From: Bob Tracy <rct@gherkin.frus.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG] 3.12.0-rcX IPv6 panic
Date: Mon, 21 Oct 2013 08:18:46 -0500 [thread overview]
Message-ID: <20131021131846.GA5769@gherkin.frus.com> (raw)
Actually, a regression: the 3.11 kernel is rock-solid stable on my
Alpha.
Beginning with 3.12.0-rc1, I can reliably trigger a kernel panic by
executing the gogo6.net "gw6c" IPv6 client program. If the networking
layer is active, an "Oops" will eventually (within a day) occur regardless
of whether I attempt to run "gw6c". 3.12.0-rcX is stable as long as I
leave networking completely disabled. The error has persisted up through
-rc6. Apologies for not mentioning this earlier, but the state of my
PWS-433au has been questionable, and I wanted to make sure I had a
legitimate bug sighting.
I'll have to transcribe the panic backtrace by hand: nothing makes it
into any of the system logs :-(. I *can* recall that every backtrace
I've seen thus far has included one of the skb_copy() variants near the
top of the list (first or second function).
--Bob
next reply other threads:[~2013-10-21 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 13:18 Bob Tracy [this message]
2013-10-21 15:52 ` Hannes Frederic Sowa
2013-10-21 23:40 ` Bob Tracy
2013-10-29 4:00 ` Bob Tracy
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=20131021131846.GA5769@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®