Upon resuming from suspend to disk, I got a kernel panic like it can be seen in the attached picture. I'm using 3.0 for less than a week and this is the first time this happens (after several successful suspend+resume-s).
Created attachment 67322 [details] kernel panic camera shot
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Mon, 1 Aug 2011 20:51:43 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=40422 > > Summary: 3.0: kernel panic - not syncing: fatal exception in > interrupt > Product: Memory Management > Version: 2.5 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Other > AssignedTo: akpm@linux-foundation.org > ReportedBy: mihai.dontu@gmail.com > Regression: No > > > Upon resuming from suspend to disk, I got a kernel panic like it can be seen > in > the attached picture. I'm using 3.0 for less than a week and this is the > first > time this happens (after several successful suspend+resume-s). > --- Comment #1 from Mihai Don#u <mihai.dontu@gmail.com> 2011-08-01 20:55:23 --- Created an attachment (id=67322) --> (https://bugzilla.kernel.org/attachment.cgi?id=67322) kernel panic camera shot drat, the first part of that crash scrolled off the screen or wasn't in the photo. I don't suppose it's possible to get that information? Still, the oops is in netfilter code - a bad pointer dereference under devinet_ioctl->masq_device_event.
On Mon, 1 Aug 2011 14:04:18 -0700 Andrew Morton wrote: > (switched to email. Please respond via emailed reply-to-all, not via > the bugzilla web interface). > > On Mon, 1 Aug 2011 20:51:43 GMT > bugzilla-daemon@bugzilla.kernel.org wrote: > > > https://bugzilla.kernel.org/show_bug.cgi?id=40422 > > > > Summary: 3.0: kernel panic - not syncing: fatal > > exception in interrupt > > Product: Memory Management > > Version: 2.5 > > Platform: All > > OS/Version: Linux > > Tree: Mainline > > Status: NEW > > Severity: normal > > Priority: P1 > > Component: Other > > AssignedTo: akpm@linux-foundation.org > > ReportedBy: mihai.dontu@gmail.com > > Regression: No > > > > > > Upon resuming from suspend to disk, I got a kernel panic like it > > can be seen in the attached picture. I'm using 3.0 for less than a > > week and this is the first time this happens (after several > > successful suspend+resume-s). > > > > --- Comment #1 from Mihai Don#u <mihai.dontu@gmail.com> 2011-08-01 > 20:55:23 --- Created an attachment (id=67322) > --> (https://bugzilla.kernel.org/attachment.cgi?id=67322) > kernel panic camera shot > > drat, the first part of that crash scrolled off the screen or wasn't > in the photo. I don't suppose it's possible to get that information? No, I'm afraid not. I'll disable the framebuffer decorations for the future. Should get me 4 or 5 more lines of backtrace when the crash reappears. > Still, the oops is in netfilter code - a bad pointer dereference under > devinet_ioctl->masq_device_event.
Reply-To: mdontu@bitdefender.com On Tuesday 02 August 2011 00:45:58 Mihai Donțu wrote: > > drat, the first part of that crash scrolled off the screen or wasn't > > in the photo. I don't suppose it's possible to get that > > information? > > No, I'm afraid not. I'll disable the framebuffer decorations for the > future. Should get me 4 or 5 more lines of backtrace when the crash > reappears. > > > Still, the oops is in netfilter code - a bad pointer dereference > > under devinet_ioctl->masq_device_event. I got another kernel panic, but it's in a different place and I've somehow managed to take a crappy snapshot (missing some of the right side info). Anyway, at the rate these tend to happen, I'm likely to be able to submit a correct one pretty soon. Is there any option you'll like me to turn on? -- Mihai DONȚU Linux Software Developer BitDefender ------------------------------ Email: mdontu@bitdefender.com Phone: +40 212 063 470 ------------------------------ www.bitdefender.com unices.bitdefender.com