Bugzilla – Bug 148294
kernel traceback returning from sleep
Last modified: 2006-04-27 12:09:52 UTC
kernel 2.6.16_rc1_git3 This kernel also has usb-storage problems when going to sleep. Feb 5 14:10:03 frank kernel: Back to C! Feb 5 14:10:03 frank kernel: Debug: sleeping function called from invalid context at mm/slab.c:2515 Feb 5 14:10:03 frank kernel: in_atomic():0, irqs_disabled():1 Feb 5 14:10:03 frank kernel: [<c014cc5a>] kmem_cache_alloc+0x1b/0x79 Feb 5 14:10:03 frank kernel: [<c01cdff3>] acpi_os_acquire_object+0xb/0x36 Feb 5 14:10:03 frank kernel: [<c01e4d88>] acpi_ut_allocate_object_desc_dbg+0x13/0x49 Feb 5 14:10:03 frank kernel: [<c01e4dd3>] acpi_ut_create_internal_object_dbg+0x15/0x68 Feb 5 14:10:03 frank kernel: [<c01e0fc1>] acpi_rs_set_srs_method_data+0x3d/0xb7 Feb 5 14:10:03 frank kernel: [<c014bcce>] cache_alloc_debugcheck_after+0xb8/0xea Feb 5 14:10:03 frank kernel: [<c01e8563>] acpi_pci_link_set+0x40/0x1c0 Feb 5 14:10:03 frank kernel: [<c01e8629>] acpi_pci_link_set+0x106/0x1c0 Feb 5 14:10:03 frank kernel: [<c01e8738>] irqrouter_resume+0x55/0x73 Feb 5 14:10:03 frank kernel: [<c020ad3f>] __sysdev_resume+0x11/0x53 Feb 5 14:10:03 frank kernel: [<c020ae7f>] sysdev_resume+0x16/0x47 Feb 5 14:10:03 frank kernel: [<c020edaa>] device_power_up+0x5/0xa Feb 5 14:10:03 frank kernel: [<c012e55d>] enter_state+0x10d/0x160 Feb 5 14:10:03 frank kernel: [<c012e638>] state_store+0x88/0x95 Feb 5 14:10:03 frank kernel: [<c012e5b0>] state_store+0x0/0x95 Feb 5 14:10:03 frank kernel: [<c018260e>] subsys_attr_store+0x1e/0x22 Feb 5 14:10:03 frank kernel: [<c018270f>] sysfs_write_file+0x9b/0xc1 Feb 5 14:10:03 frank kernel: [<c0182674>] sysfs_write_file+0x0/0xc1 Feb 5 14:10:03 frank kernel: [<c014f7fe>] vfs_write+0xa1/0x146 Feb 5 14:10:03 frank kernel: [<c014fd14>] sys_write+0x3c/0x63 Feb 5 14:10:04 frank kernel: [<c0102a3b>] sysenter_past_esp+0x54/0x79
There has been no activity for quite a while. I'm closing this bug as WONTFIX. If you feel this is inappropriate and the bug should remain open, or you have new information which may lead to an actual resolution, please reopen the bug and add the new status.