From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Chris Rankin <rankincj@yahoo.com>,
netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, stable@kernel.org
Subject: Re: [Bugme-new] [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing
Date: Tue, 08 Dec 2009 15:39:35 +0100 [thread overview]
Message-ID: <4B1E6527.4020605@gmail.com> (raw)
In-Reply-To: <20091208134157.GB24223@hmsreliant.think-freely.org>
Neil Horman a écrit :
> On Tue, Dec 08, 2009 at 05:39:28AM -0800, Chris Rankin wrote:
>> --- On Tue, 8/12/09, Neil Horman <nhorman@tuxdriver.com> wrote:
>>> 30 minutes isn't too long to wait for an error to appear, I think.
>> Except it's a very "busy" waiting process with me actively surfing the web. I can't automate that. I'm still not entirely sure what the trigger condition is.
>>
> Sure you can, generate a list of sites that you visited and access them all with
> a curl or wget script. I would imagine thats a reasonable test to trigger the
> reproducer.
Yes, but I suspect a multi threading bug, or vm , or X11, or something.
Andi posted a futex patch that is worth to try, if machine is swaping a bit.
Chris, please provide as much information as you can
# cat /proc/cpuinfo
# cat /proc/meminfo
# ps aux
# scripts/ver_linux
next prev parent reply other threads:[~2009-12-08 14:40 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
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 [this message]
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=4B1E6527.4020605@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rankincj@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.