So I got bold and enabled CONFIG_PREEMPT in 2.5.39, and got the
following message at boot time:
Sleeping function called from illegal context at slab.c:1374
c12a5ea8 c0117a26 c0296260 c0298202 0000055e c1283060 c013ab4f c0298202
0000055e c03b668c 00000002 00000003 c01ff5ec c03b668c 00000042 c12838e0
c12838e0 c12838e0 00000246 cfdee214 c0207830 04000000 c03b65f0 c0109be2
Call Trace:
[<c0117a26>]__might_sleep+0x56/0x5d
[<c013ab4f>]kmalloc+0x4f/0x330
[<c01ff5ec>]piix_tune_chipset+0x33c/0x350
[<c0207830>]ide_intr+0x0/0x320
[<c0109be2>]request_irq+0x52/0xa0
[<c0200a33>]init_irq+0x263/0x400
[<c0207830>]ide_intr+0x0/0x320
[<c0200edc>]hwif_init+0x10c/0x260
[<c02006ad>]probe_hwif_init+0x1d/0x70
[<c02121d1>]ide_setup_pci_device+0x41/0x70
[<c01ff7a5>]piix_init_one+0x35/0x40
[<c010511b>]init+0x8b/0x250
[<c0105090>]init+0x0/0x250
[<c01055f9>]kernel_thread_helper+0x5/0xc
kksymoops is very nice :)
The system still seems to be running ok, but I think I'll turn off
CONFIG_PREEMPT just to be sure.
This is a SMP kernel running on a UP box. Other configuration options
available if needed.
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 30 2002 - 22:00:33 EST