From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, stable@kernel.org,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [Bugme-new] [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing
Date: Tue, 08 Dec 2009 12:21:12 +0100 [thread overview]
Message-ID: <4B1E36A8.5040106@gmail.com> (raw)
In-Reply-To: <335647.4861.qm@web52906.mail.re2.yahoo.com>
Chris Rankin a écrit :
> --- On Tue, 8/12/09, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> Its all two years old UDP bugs (I spot another one some
>> hours ago), and very rare.
>
>> I am quite suprised it could happen on your machine on
>> demand.
>
> Who said anything about "on demand"? It took about 30 minutes to freeze last time;
> I was starting to think that a complete recompile had fixed it!
>
30 minutes is pretty fast, this is why I said 'on demand'...
> For the record: I've only seen that dmesg warning I've reported *once*, and that didn't kill the machine immediately (hence I was able to report it in the first place).
>
>> 1) Do you have another NIC adapter to try ? It might be a
>> buggy driver. (Neil Horman found an error on Intel drivers some
>> hours ago, that can corrupt skbs)
>
> I can test any patches for a e1000 that apply to 2.6.31.x. But the e1000 is an on-board device and I don't have another. But Fedora's 2.6.31.x kernels seem OK.
>
>> 2) Could you add following debugging aid ?
>
> Not a problem; I do have a serial console attached.
>
>> 3) Any chance you can do a git bisect ?
>
> How do you git-bisect a bug that you can't reproduce on demand? A negative is easy to spot, but a positive would be not experiencing a random freeze. As I said, I *almost* thought that I'd resolved the issue by recompiling last night.
>
Please fold your lines length to < 70
If Fedora kernel works, either its just pure luck, or they found
a bug and they didnt sent the fix to mainline (unlikely)
next prev parent reply other threads:[~2009-12-08 11:21 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 [this message]
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=4B1E36A8.5040106@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 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).