BUG: scheduling while atomic in acpi_ipmi

Issue

• System crashes with a log similar to the below. Note: this alone is not sufficient to identify this specific bug, please check the diagnostic steps below.

BUG: scheduling while atomic: swapper/0/0x10000100
Modules linked in: iptable_filter ip_tables bridge bonding 8021q garp stp llc ipv6 sg enic power_meter microcode i2c_i801 i2c_core iTCO_wdt iTCO_vendor_support ioatdma dca i7core_edac edac_core shpchp ext4 mbcache jbd2 dm_round_robin sd_mod crc_t10dif fnic libfcoe libfc scsi_transport_fc scsi_tgt mptsas mptscsih mptbase scsi_transport_sas dm_multipath dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
CPU 10

Pid: 0, comm: swapper Not tainted 2.6.32-358.11.1.el6.x86_64 #1 Cisco Systems Inc N20-B6625-1/N20-B6625-1
RIP: 0010:[<ffffffff812d39fe>]  [<ffffffff812d39fe>] intel_idle+0xde/0x170
RSP: 0018:ffff880864779e68  EFLAGS: 00000206
RAX: 0000000000000000 RBX: ffff880864779ed8 RCX: 0000000000000000
RDX: 00000000000003c0 RSI: 0000000000000000 RDI: 00000000000ea857
RBP: ffffffff8100bb8e R08: ffffffff81a975c0 R09: 00000000000000c8
R10: 0000000000000002 R11: 0000000000000000 R12: 0000000052b66c23
R13: 13420ded0f619e00 R14: 0000000225c17d03 R15: 00000000000ea857
FS:  0000000000000000(0000) GS:ffff8800282a0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00000030c344b180 CR3: 00000008609ec000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process swapper (pid: 0, threadinfo ffff880864778000, task ffff88106440cae0)
Stack:
000000000000000a 0000000000000002 0000000000000000 00000000000003c0
0000000000000000 00000000000003c0 0000000000000000 0000000a000d36f5
0000000000000000 ffff8800282bdf00 ffff8800282be030 0000000000000000
Call Trace:
[<ffffffff814152d7>] ? cpuidle_idle_call+0xa7/0x140
[<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110
[<ffffffff8150704c>] ? start_secondary+0x2ac/0x2ef
Code: da dc ff 4c 29 e8 48 89 c7 e8 3f 1d da ff 49 89 c4 49 89 d5 48 89 45 a0 48 89 55 a8 48 89 45 b0 48 89 55 b8 fb 66 0f 1f 44 00 00 <85> 1d 9c 1a 82 00 75 0e 48 8d 75 cc bf 05 00 00 00 e8 5c 28 dd
Call Trace:
[<ffffffff812d39e1>] ? intel_idle+0xc1/0x170
[<ffffffff814152d7>] ? cpuidle_idle_call+0xa7/0x140
[<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110
[<ffffffff8150704c>] ? start_secondary+0x2ac/0x2ef

• Another call trace that can be seen in the system log, especially on Cisco servers is:

BUG: scheduling while atomic: kipmi0/235/0x10000100
Pid: 235, comm: kipmi0 Tainted: G W --------------- 2.6.32-358.0.1.el6.x86_64 #1 Cisco Systems Inc N20-B6625-1/N20-B6625-1
RIP: 0010:[<ffffffff815100f7>] [<ffffffff815100f7>] _spin_unlock_irqrestore+0x17/0x20
RSP: 0018:ffff880861e49e70 EFLAGS: 00000246
RAX: 0000000000000004 RBX: ffff880861e49e70 RCX: 00000000ffffd0c6
RDX: ffff880861e9ae24 RSI: 0000000000000246 RDI: 0000000000000246
RBP: ffffffff8100bb8e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff880861e9ae00
R13: ffffffff812d9789 R14: ffff880861e49df0 R15: ffffffff812dc01f
FS: 0000000000000000(0000) GS:ffff88088c420000(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00000000027fef48 CR3: 00000008602ac000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kipmi0 (pid: 235, threadinfo ffff880861e48000, task ffff880861e4d540)
Stack:
ffff880861e49ee0 ffffffff812da280 ffff880864789500 ffff880800000004
<d> 0000000000000286 ffff881064e61c18 ffff880861e9ae00 ffffffffffffffff
<d> ffff880861e49ee0 ffff881064e61c00 ffff880861e49ef8 ffffffff812da210
Call Trace:
[<ffffffff812da280>] ? ipmi_thread+0x70/0x1c0
[<ffffffff812da210>] ? ipmi_thread+0x0/0x1c0
[<ffffffff81096936>] ? kthread+0x96/0xa0
[<ffffffff8100c0ca>] ? child_rip+0xa/0x20
[<ffffffff810968a0>] ? kthread+0x0/0xa0