From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing
Date: Mon, 7 Dec 2009 09:01:54 -0800 [thread overview]
Message-ID: <20091207090154.6bbfe8e2@nehalam> (raw)
Begin forwarded message:
Date: Sun, 6 Dec 2009 13:40:19 GMT
From: bugzilla-daemon@bugzilla.kernel.org
To: shemminger@linux-foundation.org
Subject: [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing
http://bugzilla.kernel.org/show_bug.cgi?id=14749
Summary: Kernel locks up after a few minutes of heavy surfing
Product: Networking
Version: 2.5
Kernel Version: 2.6.31.6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
AssignedTo: shemminger@linux-foundation.org
ReportedBy: rankincj@yahoo.com
Regression: Yes
Created an attachment (id=24049)
--> (http://bugzilla.kernel.org/attachment.cgi?id=24049)
Warnings found in kernel, relating to network corruption.
This bug is new as of 2.6.31.x kernels. After a short period of heavy surfing
(e.g. lots of tabs open in Firefox), the kernel will suddenly stop responding.
Nothing is written to the serial console, and the machine stops responding to
pings. My only clue so far has been a warning which I found once in my dmesg
log (attached).
I have already tried manually applying this patch from the upcoming -stable
queue:
net-fix-sk_forward_alloc-corruption.patch
to no effect.
I am currently switching back to Fedora's 2.6.31.6-145.fc12.i686 kernel to see
if it is more stable. (I cannot trust 2.6.31.6 any more.)
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
next reply other threads:[~2009-12-07 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:01 Stephen Hemminger [this message]
2009-12-07 17:05 ` [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing Stephen Hemminger
2009-12-07 22:32 ` [RFC, PATCH] net: sock_queue_err_skb() and sk_forward_alloc corruption Eric Dumazet
2009-12-26 1:29 ` David Miller
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=20091207090154.6bbfe8e2@nehalam \
--to=shemminger@vyatta.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).