Bug 71781
| Summary: | Kernel panic - not syncing: Fatal exception in interrupt | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Antonio (asilva) |
| Component: | IPV4 | Assignee: | Stephen Hemminger (stephen) |
| Status: | RESOLVED INVALID | ||
| Severity: | blocking | CC: | eric.dumazet |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 3.10.32 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | full boot sequence log | ||
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. Reproduce problem without known buggy out of tree module (IMQ). IMQ was rejected upstream because it was racy. Thanks, I didn't notice the IMQ messages, removing IMQ from loading on boot the kernel starts ok. Thanks, |
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..