Chili_Man: I've been looking at the xen-netfront driver which produces the panic, and as far as I can tell this is a bug elsewhere in the networking stack and not in xen-netfront. Exactly where the problem comes from is still unknown, as the panic is disconnected from the source of the bad data.
However if true I should be able to produce similar data without using Xen. I've built a modified kernel which will hopefully detect the bad data when it is created and point to the code which created it. I'm running this right now in a kvm virtual machine with a minimal haproxy/nginx setup and downloading a large file from the VM in a tight loop. If you can provide more details about your setup I may be able to tweak my test to more closely match your use case. It would also be helpful if you could reproduce the issue while running with my modified kernel and then give me the kernel log. I've uploaded the package to the location below if you're able to try it out. You probably need only the linux-image package and not linux-image-extra, though the safest bet is to see what you already have installed and install the same thing. http://people.canonical.com/~sforshee/lp1275879/linux-3.11.0-17.31+lp1275879v201402101139/ Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275879 Title: Kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
