In addition to opening an upstream bug, 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.
Can you test the following kernels and report back? We are looking for the first kernel version that doesn't have 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-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc4-quantal/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Tags added: performing-bisect ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Raring) Importance: Medium Status: Incomplete ** Changed in: linux (Ubuntu Quantal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Quantal) Status: New => Incomplete ** Changed in: linux (Ubuntu Raring) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070690 Title: BUG: unable to handle kernel NULL pointer dereference at (null); RIP: 0010:[<ffffffff8167f93a>] [<ffffffff8167f93a>] __mutex_lock_slowpath+0xaa/0x150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
