Bug 186971
| Summary: | Kernel Panic: unable to handle kernel paging request in neigh_resolve_output with RIP eth_header | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Martin Weinelt (martin) |
| Component: | IPV6 | Assignee: | Hideaki YOSHIFUJI (yoshfuji) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | szg00000 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.7.8 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
kernel 4.6 (kvm guest)
kernel 4.6 (xen guest) kernel 4.7 (xen guest) kernel 4.5 (xen guest) |
||
Created attachment 243661 [details]
kernel 4.6 (xen guest)
Created attachment 243671 [details]
kernel 4.7 (xen guest)
Created attachment 244331 [details]
kernel 4.5 (xen guest)
|
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).