netdev - Re: [Bug 40422] New: 3.0: kernel panic - not syncing: fatal exception in interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 23 Jan 2012 16:53:58 +0200
From:	Mihai Donțu <mihai.dontu@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	bugzilla-daemon@...zilla.kernel.org, netdev@...r.kernel.org,
	netfilter-devel@...r.kernel.org
Subject: Re: [Bug 40422] New: 3.0: kernel panic - not syncing: fatal
 exception in interrupt

On Wed, 3 Aug 2011 04:59:16 +0300 Mihai Donțu wrote:
> 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?
> 

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,

-- 
Mihai Donțu
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html