Bug 61881 - Fatal exception in interrupt (IPv6, virtio-net)
Summary: Fatal exception in interrupt (IPv6, virtio-net)
Status: RESOLVED DUPLICATE of bug 63331
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV6 (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Hideaki YOSHIFUJI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-22 13:16 UTC by Roman Mamedov
Modified: 2013-11-20 04:49 UTC (History)
1 user (show)

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

Attachments
screenshot of the crash backtrace (44.72 KB, image/png)
2013-09-22 13:16 UTC, Roman Mamedov 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Roman Mamedov 2013-09-22 13:16:20 UTC 
Created attachment 109231 [details]
screenshot of the crash backtrace

Hello,

I have a KVM virtual machine that started crashing with increasing frequency, two crashes within 12 hours, then one more within 10 minutes, and one more even just 50 seconds after boot-up.

Also tried 3.10.11, result is the same.

This VM is a router (IPv6 too) between several VLANs and tunnel interfaces. The backtrace mentions IPv6 and virtio-net (screenshot attached).

Hope someone can help figure out what is happening here.

Thanks
Comment 1 hannes 2013-09-22 15:59:38 UTC 
Could you log the splat via (virtual) serial console? I would be helpful to have a complete and copy&pastable one.
Comment 2 Roman Mamedov 2013-11-04 23:41:21 UTC 
Hello,

Back then I have switched KVM/QEMU from virtio-net to Intel 82540EM emulation, and have not had this problem ever since. Unfortunately I was not in a position to investigate this any further.

However today I ran across this report: http://www.spinics.net/lists/netdev/msg255605.html
and the backtrace in it looks very similar to what I had. Maybe it is the same problem.

Thanks
Comment 3 hannes 2013-11-20 04:25:49 UTC 
Duplicate of 63331 which is fixed.
Comment 4 Roman Mamedov 2013-11-20 04:49:15 UTC 

*** This bug has been marked as a duplicate of bug 63331 ***
Note You need to log in before you can comment on or make changes to this bug.