I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug: v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/ v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ v3.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/ v3.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/ v3.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251946 Title: Network related kernel panic on Atom 64bit system using saucy backport stack on precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251946/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
