From: Jarek Poplawski <jarkao2@o2.pl>
To: David Johnson <dj@david-web.co.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hardware bug or kernel bug?
Date: Fri, 13 Oct 2006 15:06:48 +0200 [thread overview]
Message-ID: <20061013130648.GC1690@ff.dom.local> (raw)
In-Reply-To: <200610131256.54546.dj@david-web.co.uk>
On Fri, Oct 13, 2006 at 12:56:53PM +0100, David Johnson wrote:
> On Friday 13 October 2006 11:58, Jarek Poplawski wrote:
> >
> > PS: I hope you tested it also under internal stress (heavy
> > copying plus computing).
>
> Yes, I did. No individual factor triggers the bug (high CPU load, lots of disk
> activity, high network load, etc.) nor does any other combination of factors
> other than what I mentioned before (high network load, some disk activity,
> some CPU load).
>
> Both scp and rsync trigger it reliably, but FTP does not trigger it at all. So
> CPU load (which scp and rsync generates but FTP does not) must be a key part
> of the equation...
Probably - but only with networking. So I'd try with this debugging
like in my first reply plus maybe 2.6.19-rc1 (e1000 - btw. I hope
this other tested card was different model - and locking improved)
and resend conclusions to netdev@vger.kernel.org.
Cheers,
Jarek P.
next prev parent reply other threads:[~2006-10-13 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 16:53 Hardware bug or kernel bug? David Johnson
2006-10-12 17:20 ` Arjan van de Ven
2006-10-12 19:13 ` Linus Torvalds
2006-10-13 9:20 ` David Johnson
2006-10-13 8:56 ` Jarek Poplawski
2006-10-13 9:20 ` David Johnson
2006-10-13 10:58 ` Jarek Poplawski
2006-10-13 11:56 ` David Johnson
2006-10-13 13:06 ` Jarek Poplawski [this message]
2006-10-13 16:24 ` David Johnson
2006-10-13 17:11 ` Alan Cox
2006-10-16 10:25 ` Jarek Poplawski
2006-10-16 14:32 ` David Johnson
2006-10-17 7:10 ` Jarek Poplawski
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=20061013130648.GC1690@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=dj@david-web.co.uk \
--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