From: "Mihai Donțu" <mihai.dontu@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [Bug 40422] New: 3.0: kernel panic - not syncing: fatal exception in interrupt
Date: Mon, 23 Jan 2012 16:53:58 +0200 [thread overview]
Message-ID: <20120123165358.60b1ba11@mdontu-l.dsd.ro> (raw)
In-Reply-To: <20110803045916.363b35fb@mdontu-dell>
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 netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-01-23 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40422-27@https.bugzilla.kernel.org/>
2011-08-01 21:04 ` [Bug 40422] New: 3.0: kernel panic - not syncing: fatal exception in interrupt Andrew Morton
2011-08-01 21:45 ` Mihai Donțu
[not found] ` <20110803045916.363b35fb@mdontu-dell>
2012-01-23 14:53 ` Mihai Donțu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120123165358.60b1ba11@mdontu-l.dsd.ro \
--to=mihai.dontu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox