Re: Linux 2.6.0-test8

From: Daniele Venzano
Date: Sat Oct 18 2003 - 11:50:26 EST


On Fri, Oct 17, 2003 at 03:31:00PM -0700, Linus Torvalds wrote:
>
> More changes than I would have liked, but most of them are fairly small.
> The most noticeable changes:
>

I get these two sleeping functions etc. etc. on boot with 2.6.0-test8:

Kernel command line: root=/dev/hda3
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Debug: sleeping function called from invalid context at include/linux/rwsem.h:66
in_atomic():1, irqs_disabled():1
Call Trace:
[<c011d1d0>] __might_sleep+0xa0/0xd0
[<c02796f0>] cpufreq_register_notifier+0x30/0xa0
[<c0105000>] rest_init+0x0/0x60
[<c03b330b>] init_tsc+0x4b/0x170
[<c03b683b>] init_timers+0x3b/0x40
[<c0105000>] rest_init+0x0/0x60
[<c011467d>] select_timer+0x2d/0x50
[<c03afa8e>] time_init+0x3e/0x70
[<c03ac675>] start_kernel+0xb5/0x160
[<c03ac480>] unknown_bootoption+0x0/0x100

Detected 1674.442 MHz processor.
Console: colour VGA+ 80x25
Memory: 482692k/491432k available (1930k kernel code, 7948k reserved, 789k data, 144k init, 0k highmem)
Calibrating delay loop... 3309.56 BogoMIPS
Debug: sleeping function called from invalid context at mm/page_alloc.c:548
in_atomic():1, irqs_disabled():0
Call Trace:
[<c0105000>] rest_init+0x0/0x60
[<c011d1d0>] __might_sleep+0xa0/0xd0
[<c013db75>] __alloc_pages+0x335/0x340
[<c011fdbc>] printk+0x12c/0x180
[<c0105000>] rest_init+0x0/0x60
[<c013dbf0>] get_zeroed_page+0x20/0x60
[<c03b6a7c>] pidmap_init+0xc/0x40
[<c03ac69d>] start_kernel+0xdd/0x160
[<c03ac480>] unknown_bootoption+0x0/0x100

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[...]

Apart from that, everything work well (of what has been tested 8) ).

--
----------------------------------------
Daniele Venzano
Web: http://digilander.iol.it/webvenza/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/