Bug 71781 - Kernel panic - not syncing: Fatal exception in interrupt
Summary: Kernel panic - not syncing: Fatal exception in interrupt
Status: RESOLVED INVALID
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV4 (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-10 12:51 UTC by Antonio
Modified: 2014-03-11 08:10 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.10.32
Subsystem:
Regression: No
Bisected commit-id:

Attachments
full boot sequence log (46.81 KB, text/x-log)
2014-03-10 12:51 UTC, Antonio 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Antonio 2014-03-10 12:51:36 UTC 
Created attachment 128811 [details]
full boot sequence log

The servers just panic on boot time:

[   18.647435] BUG: unable to handle kernel NULL pointer dereference at 0000000000000080
[   18.656468] IP: [<ffffffff810f4c8d>] ____cache_alloc+0x1f/0x290
[   18.663269] PGD 0 
[   18.665581] Oops: 0000 [#1] SMP 

.... (see attach log for the full message)

[   19.200202] ---[ end trace 85fce9ca9a98a944 ]---
[   19.207209] Kernel panic - not syncing: Fatal exception in interrupt
[   19.216142] Rebooting in 1 seconds..
Comment 1 Eric Dumazet 2014-03-11 05:31:50 UTC 
Yes, and the interesting part in the clipped message is :

[   16.431685]  Hooking IMQ after NAT on PREROUTING.
[   16.436985]  Hooking IMQ before NAT on POSTROUTING.

Sorry, we do not support IMQ in upstream kernel.
Comment 2 Stephen Hemminger 2014-03-11 05:46:46 UTC 
Reproduce problem without known buggy out of tree module (IMQ).
IMQ was rejected upstream because it was racy.
Comment 3 Antonio 2014-03-11 08:10:36 UTC 
Thanks,

I didn't notice the IMQ messages, removing IMQ from loading on boot the kernel starts ok.


Thanks,
Note You need to log in before you can comment on or make changes to this bug.