[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-12-04 Thread Rick Lavoie
I saw that 3.11.0-15 included a couple of backported fixes for shm races, including one (8380e1f50d3640498a3fec272ce32199de788a2d) that described my bug nearly exactly. I've been testing this kernel for the last couple of days, and have been unable to reproduce the kernel oops, so I think we can ca

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-12-01 Thread Rick Lavoie
The 3.11.5-031105.201311251400_amd64 (6b8fe6d417f93fa628779b1afd9e7717bbcb0572) kernel is bad, I was able to trigger the oops. However, the oops was only triggered after several days of usage, making me uneasy that the cause of the oops might be present in earlier kernels and I simply failed to tri

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-24 Thread Rick Lavoie
The 3.11.5-031105.201311211301_amd64 (1104f1b038765d0e31262eecdea6010907194226) kernel seems to be good, no oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249719 Title: Kernel oops - BUG: unab

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-20 Thread Rick Lavoie
http://kernel.ubuntu.com/~jsalisbury/lp1249719 seems to be empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-20 Thread Rick Lavoie
Will do, though the new specified commit (8bacb5ad41da1fde1c05165515c50e2911f16899) is actually before the previous commit (dbb563ec7b143323dd31520ab08c08394bc13381), which usually happens if "bad" is reported to the bisection, whereas all the results to date have been "good". -- You received thi

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-18 Thread Rick Lavoie
The 3.11.5-031105.201311181306_amd64 (dbb563ec7b143323dd31520ab08c08394bc13381) kernel is good, no oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249719 Title: Kernel oops - BUG: unable to han

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-16 Thread Rick Lavoie
The 3.11.5-031105.201311151139_amd64 (b340404549c872099aec7554439a1821c0708878) kernel is good, no oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249719 Title: Kernel oops - BUG: unable to han

[Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-14 Thread Rick Lavoie
Hello, I tested the three specified kernels, and v3.11.6 was the first one in which I could trigger the oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249719 Title: Kernel oops - BUG: unable

[Bug 1249719] [NEW] Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140

2013-11-09 Thread Rick Lavoie
Public bug reported: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain pro