Bug 186971 - Kernel Panic: unable to handle kernel paging request in neigh_resolve_output with RIP eth_header
Summary: Kernel Panic: unable to handle kernel paging request in neigh_resolve_output ...
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV6 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Hideaki YOSHIFUJI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-04 21:19 UTC by Martin Weinelt
Modified: 2016-11-13 18:58 UTC (History)
1 user (show)

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


Attachments
kernel 4.6 (kvm guest) (5.16 KB, application/octet-stream)
2016-11-04 21:19 UTC, Martin Weinelt
Details
kernel 4.6 (xen guest) (5.03 KB, application/octet-stream)
2016-11-04 21:19 UTC, Martin Weinelt
Details
kernel 4.7 (xen guest) (4.53 KB, application/octet-stream)
2016-11-04 21:20 UTC, Martin Weinelt
Details
kernel 4.5 (xen guest) (4.63 KB, application/octet-stream)
2016-11-13 18:58 UTC, Martin Weinelt
Details

Description Martin Weinelt 2016-11-04 21:19:11 UTC
Created attachment 243651 [details]
kernel 4.6 (kvm guest)

At least several times a day three of our virtualized hosts, serving as IPv4 and IPv6 Gateways for a batman-adv mesh network, are experiencing this kernel panic.

Both the guest and hostsystems are running Debian Jessie (with the 4.7.8 backports Kernel) and the virtualization happens with both Xen and KVM, so I'll attach both backtraces.

We have first experienced this issue in the beginning of august 2016 when we were using Kernel version 4.6.1-1~bpo8+1 or 4.6.3-1~bpo8+1.

We are running a more recent out-of-tree release of batman-adv (2016.2, 2016.3 and now 2016.4).
Comment 1 Martin Weinelt 2016-11-04 21:19:46 UTC
Created attachment 243661 [details]
kernel 4.6 (xen guest)
Comment 2 Martin Weinelt 2016-11-04 21:20:03 UTC
Created attachment 243671 [details]
kernel 4.7 (xen guest)
Comment 3 Martin Weinelt 2016-11-13 18:58:55 UTC
Created attachment 244331 [details]
kernel 4.5 (xen guest)

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