My laptop got stolen from my hotel room while I was in Prague, so no
further progress for now on this one...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977123
Title:
Kernel Oops - BUG: unable to
*** This bug is a duplicate of bug 922906 ***
https://bugs.launchpad.net/bugs/922906
** This bug has been marked a duplicate of bug 922906
Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
009c; EIP is at __ticket_spin_lock+0x8/0x30
--
You received this bug
FYI, trying to narrow down the kernel versions for bisect I tested with
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.39.4-oneiric/linux-
image-2.6.39-02063904-generic_2.6.39-02063904.201108040905_i386.deb on
natty and got the oops. So, it appears the regression was introduced
somewhere
Further progress: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.39-rc7-oneiric/linux-
image-2.6.39-020639rc7-generic_2.6.39-020639rc7.201105121801_i386.deb
crashes and http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.39-rc4-natty/linux-
Shock, the next step is to perform a kernel bisect from Natty to
Oneiric, in order to identify the offending commit(s). Could you please
do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?
Helpful Bug Reporting Links:
This is the oops I'm getting with the latest 'precise' kernel:
Apr 23 21:27:33 eeepc kernel: [ 111.193164] BUG: unable to handle kernel NULL
pointer dereference at (null)
Apr 23 21:27:33 eeepc kernel: [ 111.193504] IP: [c10272d8]
__ticket_spin_lock+0x8/0x30
Apr 23 21:27:33 eeepc kernel: [
This is the oops with the kernel from Andy:
Apr 23 22:02:18 eeepc kernel: [ 182.048097] BUG: unable to handle kernel NULL
pointer dereference at (null)
Apr 23 22:02:18 eeepc kernel: [ 182.048256] IP: [c10272d8]
__ticket_spin_lock+0x8/0x30
Apr 23 22:02:18 eeepc kernel: [ 182.048370] *pde =
Can you post the latest oops messages you are getting with the test
kernel from Andy?
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm still getting the kernel oops with the apw kernel from bug #922906.
I'm removing the duplicate status since it does not seem to be a
duplicate. All the patches I've seen in the apw kernel have to do with
inotify/fsnotify. I'm triggering the bug by connecting a bluetooth
mouse. The problem
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
*** This bug is a duplicate of bug 922906 ***
https://bugs.launchpad.net/bugs/922906
There is a test kernel available for this bug at:
http://people.canonical.com/~apw/lp922906-precise/
Can you test this kernel and report back in bug 922906 where or not the
test kernel resolved this bug?
Shock, thank you for reporting this bug and helping make Ubuntu better.
If you could also please test the latest upstream kernel available that
would be great. It will allow additional upstream developers to examine
the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
you've
I just tested with http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.4-rc2-precise/linux-
image-3.4.0-030400rc2-generic_3.4.0-030400rc2.201204072235_i386.deb and
while it didn't crash right after login like 3.2 used to do, I think it
didn't crash because it wasn't communicating with the mouse.
I still get the crash with http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.3-precise/linux-
image-3.3.0-030300-generic_3.3.0-030300.201203182135_i386.deb .
I'm reporting another bug for 3.3 in case the backtrace is different
(I'd assume not).
** Changed in: linux (Ubuntu)
Status:
Apport won't file a bug against 3.3 because I'm running a mainline
kernel so not filing that (likely) duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977123
Title:
Kernel Oops - BUG:
To reiterate, with up to date Natty, there's no crash and the mouse is
working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977123
Title:
Kernel Oops - BUG: unable to handle kernel NULL
*** This bug is a duplicate of bug 922906 ***
https://bugs.launchpad.net/bugs/922906
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** This bug has been marked a duplicate of bug 922906
Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at
009c; EIP
17 matches
Mail list logo
