public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Johnson <dj@david-web.co.uk>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hardware bug or kernel bug?
Date: Fri, 13 Oct 2006 12:56:53 +0100	[thread overview]
Message-ID: <200610131256.54546.dj@david-web.co.uk> (raw)
In-Reply-To: <20061013105807.GB1690@ff.dom.local>

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...

Regards,
David.

  reply	other threads:[~2006-10-13 11:56 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 [this message]
2006-10-13 13:06         ` Jarek Poplawski
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=200610131256.54546.dj@david-web.co.uk \
    --to=dj@david-web.co.uk \
    --cc=jarkao2@o2.pl \
    --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