Red Hat Bugzilla – Bug 140553
Invalid sleep context in resuming from suspend-to-mem
Last modified: 2015-01-04 17:12:56 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 Description of problem: I got an debug message resuming from suspend-to-mem. I am using ACPI, and my event setup is such that when the lid closes I do "echo mem > /sys/power/state". Suspending is fine, but on resume I got the following oops: Debug: sleeping function called from invalid context at mm/slab.c:2063 in_atomic():0[expected: 0], irqs_disabled():1 [<0211cbcb>] __might_sleep+0x7d/0x8a [<0214bf9f>] __kmalloc+0x42/0x7d [<021f48e9>] acpi_os_allocate+0xa/0xb [<0220878a>] acpi_ut_allocate+0x2e/0x52 [<02208721>] acpi_ut_initialize_buffer+0x41/0x7c [<02205474>] acpi_rs_create_byte_stream+0x23/0x3b [<02206976>] acpi_rs_set_srs_method_data+0x1b/0x9d [<0211b101>] recalc_task_prio+0x128/0x133 [<0220e15c>] acpi_pci_link_set+0xfe/0x176 [<0220e4e0>] irqrouter_resume+0x1c/0x24 [<0224366a>] sysdev_resume+0x3e/0xa5 [<02246564>] device_power_up+0x5/0xa [<0213db9a>] suspend_enter+0x25/0x2d [<0213dc08>] enter_state+0x3f/0x5e [<0213dd07>] state_store+0x83/0x91 [<0213dc84>] state_store+0x0/0x91 [<021ab44b>] subsys_attr_store+0x19/0x21 [<021ab5be>] flush_write_buffer+0x1d/0x22 [<021ab5e5>] sysfs_write_file+0x22/0x35 [<02165c82>] vfs_write+0xb6/0xe2 [<02165d4c>] sys_write+0x3c/0x62 ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 9 (level, low) -> IRQ 9 ACPI: PCI interrupt 0000:00:0f.0[A]: no GSI ACPI: PCI interrupt 0000:00:13.0[A] -> GSI 9 (level, low) -> IRQ 9 hub 1-0:1.0: reactivate --> -22 Restarting tasks... done Resume completes, but my mouse didn't work at all; restarting X didn't work, I had to reboot. Version-Release number of selected component (if applicable): kernel-2.6.9-1.681_FC3 How reproducible: Always Steps to Reproduce: 1. Close lid 2. Open lid 3. dmesg Additional info:
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you.