Thanks for getting those logs. Unfortunately I'm still not able to reproduce the problem.
The logs show that the data which triggers the panic is read from a pipe, but the problem happens on the other side, before or when the data enters the pipe. I've been looking at code and haven't identified the cause so far, though there's still more code to investigate. While I'm doing that it would be helpful if you could reproduce the problem again with the test kernel below. This should tell us where the problematic data comes from. I also added some printouts to provide additional information at the point where the panic occurs. Hopefully this gets us to the root cause and not to another layer of indirection. http://people.canonical.com/~sforshee/lp1275879/linux-3.11.0-17.31+lp1275879v201402141025/ -- 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
