I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue. If it's confirmed this bug still exists in the mainline kernel after testing per comment #25, then it would be good to test some of the 3.7 kernels to see where the bug was introduced..
Can you test the following kernels and report back? We are looking for the earliest kernel version that exhibits this bug: v3.7-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc4-raring/ If v3.7-rc4 does not exhibit the bug then test v3.7-rc6: v3.7-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc6-raring/ If v3.7-rc4 does exhibit the bug then test v3.7-rc2: v3.7-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc2-raring/ You don't have to test every kernel, just up until the kernel that first has this bug. One thing to note, you will need to install both the linux-image and linux-image-extra .deb packages. Thanks in advance! ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173581 Title: Ubuntu 13.04 full system crash/kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
