New: 3.0: kernel panic - not syncing: fatal exception in interrupt
Subsystems (3)
A message that is not in the archive (sent off-list or not yet received): [email protected]/
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).
Quoted 18 lines · On Mon, 1 Aug 2011 20:51:43 GMT [email protected] 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: [email protected]
ReportedBy: [email protected]
Regression: No
Quoted 4 lines
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 <[email protected]> 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.
Quoted 30 lines · 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).
Quoted 18 lines · On Mon, 1 Aug 2011 20:51:43 GMT [email protected] 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: [email protected]
ReportedBy: [email protected]
Regression: NoQuoted 5 lines
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).
Quoted 7 lines
--- Comment #1 from Mihai Don#u <[email protected]> 2011-08-01 20:55:23 --- Created an attachment (id=67322)
--> (https://bugzilla.kernel.org/attachment.cgi?id=67322)
kernel panic camera shotdrat, 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.
Quoted 2 lines
Still, the oops is in netfilter code - a bad pointer dereference under
devinet_ioctl->masq_device_event.
Signature · 1 line
Mihai Donțu
A message that is not in the archive (sent off-list or not yet received): 20110803045916.363b35fb@mdontu-dell
Quoted 12 lines · On Wed, 3 Aug 2011 04:59:16 +0300 Mihai Donțu wrote:
Quoted 10 lines · On Tuesday 02 August 2011 00:45:58 Mihai Donțu wrote:
Quoted 3 lines
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.
Quoted 2 lines
Still, the oops is in netfilter code - a bad pointer dereference under
devinet_ioctl->masq_device_event.
Quoted 7 lines
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?
This issue has not reproduced for me in quite some time, also I have updated my hardware a month ago, so I'm likely unable to test any fixes in this area.
The strange thing however is that for a while I suffered from a "desynchronization" between "hard locked" and "soft locked" (as displayed by rfkill) and I had to manually run rfkill to enable WiFi. After that last kernel panic, things got back to normal. :-) But I assume that was a hardware issue ...
You can probably close this bug.
Thanks,
Signature · 5 lines
Mihai Donțu -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html