Markus Meusel, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/comments/48 : >"Christopher, please read Tim's post #39."
I re-reviewed comment #39 and saw no mention of how either of you tested this issue in a Raring environment, whose Ubuntu kernel is linux 3.7.0-0.5 as per https://launchpad.net/ubuntu/raring/+source/linux . As per #39 Tim tested mainline http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.7-rc5-raring/ . Correct? As is known, the Ubuntu kernel and mainline upstream kernel are not the same. Hence, a bug expressed in a Ubuntu kernel, may not necessarily exist in a mainline kernel of a similar looking, but distinctly different version scheme, and vice versa. "He is testing the platform with me. We are working on the issue together." I'll keep this in mind. "So the bug is indeed fixed for Raring." Did either Tim or you test for this problem in a Raring environment and was unable to reproduce the problem? Thank you for your understanding. -- 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/bumblebee/+bug/1070690/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
