From: Jarek Poplawski <jarkao2@o2.pl>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: dj@david-web.co.uk
Subject: Re: Hardware bug or kernel bug?
Date: Fri, 13 Oct 2006 10:56:05 +0200 [thread overview]
Message-ID: <20061013085605.GA1690@ff.dom.local> (raw)
In-Reply-To: <200610121753.23220.dj@david-web.co.uk>
On 12-10-2006 18:53, David Johnson wrote:
> Hi,
>
> I'm having a major problem on a system that I've been unable to track down.
> When using scp to transfer a large file (a few gig) over the network
> (@100Mbit/s) the system will reboot after about 5-10 minutes of transfer. No
> errors, just a reboot. I have another identical system which exhibits the
> same behaviour.
...
> I've tested with Centos' 2.6.9 kernel and with a vanilla 2.6.17.13 kernel and
> the results are the same with both.
...
> Any suggestions for more ways to debug this would be greatfully received.
I'd try with this:
- minimal workable config with a lot of debugging turned on (e.g. no:
smp, floppy, parport, mouse, ipv6, video, clock modulation, apm, acpi
buttons, thermal etc. - only base acpi or no if possible),
- 2.4 kernel,
- other distro e.g. live-cd knoppix,
- other transfer method like ftp (all superfluous services turned off).
Jarek P.
next prev parent reply other threads:[~2006-10-13 8:51 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 [this message]
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
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=20061013085605.GA1690@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 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.