Bug 720098

Summary: alloc_ioapic_entries() kmalloc's with irq's off when resuming from suspend
Product: [Fedora] Fedora Reporter: Robert Binkhorst <rbinkhor>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, markrwatts
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6a13906455d501bfd59551f810afd89d23b12a6d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-06 15:56:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Robert Binkhorst 2011-07-09 09:20:52 UTC 
abrt version: 2.0.3
architecture:   x86_64
cmdline:        ro root=/dev/mapper/vg_rbinkhorlapto-lv_root rd_LUKS_UUID=luks-2fac43f9-af72-4592-953e-a3981a83c7a9 rd_LVM_LV=vg_rbinkhorlapto/lv_root rd_LVM_LV=vg_rbinkhorlapto/lv_swap rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
comment:        I closed the lid of my X220 laptop, and opened it again. Default GNOME3 energy settings.
component:      kernel
kernel:         2.6.38.6-26.rc1.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: sleeping function called from invalid context at mm/slub.c:795
time:           Sat Jul  9 11:19:45 2011

backtrace:
:BUG: sleeping function called from invalid context at mm/slub.c:795
:in_atomic(): 0, irqs_disabled(): 1, pid: 17435, name: pm-suspend
:Pid: 17435, comm: pm-suspend Not tainted 2.6.38.6-26.rc1.fc15.x86_64 #1
:Call Trace:
: [<ffffffff81047d33>] __might_sleep+0xeb/0xf0
: [<ffffffff81111413>] __kmalloc+0x79/0x10d
: [<ffffffff81023683>] ? alloc_ioapic_entries+0x27/0x87
: [<ffffffff81023683>] alloc_ioapic_entries+0x27/0x87
: [<ffffffff81021cc0>] lapic_resume+0x3a/0x24d
: [<ffffffff81396db2>] ? cpufreq_resume+0x2d/0xac
: [<ffffffff812e49b1>] __sysdev_resume+0x22/0xc2
: [<ffffffff812e4b04>] sysdev_resume+0xb3/0xf8
: [<ffffffff81086f3b>] suspend_devices_and_enter+0x149/0x1d6
: [<ffffffff8108709f>] enter_state+0xd7/0x129
: [<ffffffff81086726>] state_store+0xaf/0xc5
: [<ffffffff8122a4d7>] kobj_attr_store+0x17/0x19
: [<ffffffff811793d1>] sysfs_write_file+0x111/0x14d
: [<ffffffff81121829>] vfs_write+0xac/0xf3
: [<ffffffff81121a18>] sys_write+0x4a/0x6e
: [<ffffffff81009bc2>] system_call_fastpath+0x16/0x1b
Comment 1 Dave Jones 2011-07-11 21:06:07 UTC 
*** Bug 699112 has been marked as a duplicate of this bug. ***
Comment 2 Josh Boyer 2012-06-06 15:56:49 UTC 
That is a rather old kernel at this point.  If you are still seeing this on F16 or F17, please open a new bug.