Distribution:RHEL4.0 Hardware Environment: Kernel-2.6.12 on RHEL4-u1-rc3 distro: sleeping function called from invalid context at mm/slab.c:2093 Software Environment: Linux DISTRO:RHEL4.0 Problem Description: During the kernel boot the following error is logged in the /var/log/messages: Debug: sleeping function called from invalid context at mm/slab.c:2093 THIS PROBLEM WAS SEEN ON kernel-2.6.12 also. Steps to reproduce: Install RHEL4.0-U1-rc3. Reboot Download kernel-2.6.12.1 from kernel.org Build the kernel and reboot. This message will appear in the /var/log/messages file.
Dump from the /var/log/messages file: Jun 23 16:50:03 kernel: target0:0:8: Beginning Domain Validation Jun 23 16:50:03 kernel: Debug: sleeping function called from invalid context at mm/slab.c:2093 Jun 23 16:50:03 kernel: in_atomic():0, irqs_disabled():1 Jun 23 16:50:03 kernel: Call Trace: Jun 23 16:50:03 kernel: [c00000000406a930] [c00000000004e398] .__might_sleep+0xf4/0x104 (unreliable) Jun 23 16:50:03 kernel: [c00000000406a9c0] [c000000000091c78] .__kmalloc+0xe4/0xfc Jun 23 16:50:03 kernel: [c00000000406aa50] [c000000000093664] .kcalloc+0x48/0x7c Jun 23 16:50:03 kernel: [c00000000406aad0] [d0000000000a471c] .sym_get_ccb+0x268/0x43c [sym53c8xx] Jun 23 16:50:03 kernel: [c00000000406aba0] [d00000000009d4ec] .sym53c8xx_queue_command+0x110/0x1d8 [sym53c8xx] Jun 23 16:50:03 kernel: [c00000000406ac30] [d000000000067f4c] .scsi_dispatch_cmd+0x224/0x3a4 [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406ace0] [d0000000000700b8] .scsi_request_fn+0x2e4/0x5b0 [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406ada0] [c0000000001d7880] .blk_insert_request+0x11c/0x15c Jun 23 16:50:03 kernel: [c00000000406ae40] [d00000000006e7e0] .scsi_insert_special_req+0x4c/0x64 [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406aec0] [d00000000006ea68] .scsi_wait_req+0x7c/0xec [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406af70] [d00000000001f164] .spi_wait_req+0x60/0xcc [scsi_transport_spi] Jun 23 16:50:03 kernel: [c00000000406b020] [d00000000002141c] .spi_dv_device_compare_inquiry+0xd0/0x190 [scsi_transport_spi] Jun 23 16:50:03 kernel: [c00000000406b0f0] [d000000000021a9c] .spi_dv_device+0x310/0x65c [scsi_transport_spi] Jun 23 16:50:03 kernel: [c00000000406b1e0] [d00000000009df38] .sym53c8xx_slave_configure+0x228/0x2d0 [sym53c8xx] Jun 23 16:50:03 kernel: [c00000000406b2c0] [d0000000000722dc] .scsi_probe_and_add_lun+0xae4/0xba0 [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406b400] [d0000000000729c0] .scsi_scan_target+0x17c/0x5e0 [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406b560] [d000000000072ed0] .scsi_scan_channel+0xac/0xe8 [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406b610] [d000000000073034] .scsi_scan_host_selected+0x128/0x1fc [scsi_mod] Jun 23 16:50:03 kernel: [c00000000406b6c0] [d00000000009f5fc] .sym2_probe+0x88c/0xa10 [sym53c8xx] Jun 23 16:50:03 kernel: [c00000000406b960] [c0000000001637d4] .pci_device_probe+0xe8/0x238 Jun 23 16:50:03 kernel: [c00000000406ba90] [c0000000001cbc5c] .driver_attach+0xa0/0xf8 Jun 23 16:50:03 kernel: [c00000000406bb20] [c0000000001cc23c] .bus_add_driver+0x110/0x204 Jun 23 16:50:03 kernel: [c00000000406bbd0] [c0000000001cca8c] .driver_register+0x38/0x4c Jun 23 16:50:03 kernel: [c00000000406bc50] [c000000000163318] .pci_register_driver+0x84/0xec Jun 23 16:50:03 kernel: [c00000000406bce0] [d0000000000aa444] .sym2_init+0xd8/0x15c [sym53c8xx] Jun 23 16:50:03 kernel: [c00000000406bd80] [c00000000007d748] .sys_init_module+0x338/0x530 Jun 23 16:50:03 kernel: [c00000000406be30] [c00000000000d480] syscall_exit+0x0/0x18 Jun 23 16:50:03 kernel: target0:0:8: asynchronous.
This was a bug in the sym2 driver, wasn't it? Is this still happening in 2.6.13-rc4?
I will check with 2.6.13-rc4 and let you know. I remember that this was seen with 2.6.13-rc2 also. -- Ananda
Andrew, Checked with kernel-2.6.13-rc4 and the bug is not seen. Logs look clean. So I am closing the bug.