From: Chris Rankin <rankincj@yahoo.com>
To: netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, stable@kernel.org,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [Bugme-new] [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing
Date: Mon, 7 Dec 2009 16:19:35 -0800 (PST) [thread overview]
Message-ID: <138412.20552.qm@web52903.mail.re2.yahoo.com> (raw)
In-Reply-To: <20091207135342.6fb07264.akpm@linux-foundation.org>
--- On Mon, 7/12/09, Andrew Morton <akpm@linux-foundation.org> wrote:
> A regression in the latest 2.6.31 -stable tree.
>
> Are you really really sure that you applied that patch,
> recompiled, reinstalled, etc?
Yup, 'fraid so. And because you asked so nicely, I've just managed to reproduce the problem having first done "make distclean" and "make oldconfig", followed by "make" :-). (This was with F12's latest compiler gcc 4.4.2 20091027, BTW.) The symptom was the same - a complete system freeze without anything written to the serial console. So it's just a *guess* that it's network-related, but it does always seem to happen while I'm waiting for a web page to load in my browser...
I saw something interesting in 2.6.31.7 about a crash due to fragmentation:
ipv4: additional update of dev_net(dev) to struct *net in ip_fragment.c, NULL ptr OOPS
I'll try applying that patch too, to see if it makes any difference. Along with that other UDP-related thing I noticed:
udp: Fix udp_poll() and ioctl()
Cheers,
Chris
next prev parent reply other threads:[~2009-12-08 0:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14749-10286@http.bugzilla.kernel.org/>
2009-12-07 21:53 ` [Bugme-new] [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing Andrew Morton
2009-12-08 0:19 ` Chris Rankin [this message]
2009-12-08 3:03 ` Eric Dumazet
2009-12-08 9:03 ` Chris Rankin
2009-12-08 11:21 ` Eric Dumazet
2009-12-08 11:36 ` Jarek Poplawski
2009-12-08 13:35 ` Chris Rankin
2009-12-08 13:47 ` Jarek Poplawski
2009-12-15 7:54 ` Jarek Poplawski
2009-12-08 12:00 ` Neil Horman
2009-12-08 13:39 ` Chris Rankin
2009-12-08 13:41 ` Neil Horman
2009-12-08 14:39 ` Eric Dumazet
2009-12-08 9:17 ` Chris Rankin
2009-12-08 0:31 ` Chris Rankin
2009-12-08 0:44 ` Andrew Morton
2009-12-08 0:38 ` Chris Rankin
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=138412.20552.qm@web52903.mail.re2.yahoo.com \
--to=rankincj@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).