From: David Johnson <dj@david-web.co.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Hardware bug or kernel bug?
Date: Thu, 12 Oct 2006 17:53:22 +0100 [thread overview]
Message-ID: <200610121753.23220.dj@david-web.co.uk> (raw)
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.
The system is a Supermicro P4SCT+ with a hyperthreading P4. I've posted the
dmesg here:
http://www.david-web.co.uk/download/dmesg
I initially tried a different NIC in case that was at fault, but the results
were the same.
Changing the interrupt timer frequency in the kernel makes a difference:
100Hz - system reboots instantly when transfer is started
250Hz - reboots after a few seconds
1000Hz - reboots after 5-10 minutes
As the problem appears to be interrupt-related, I disabled the I/O APIC in the
BIOS (after first having to disable hyperthreading) which resulted in the
system lasting a bit longer before it reboots. I then tried disabling the
Local APIC as well but this made no difference.
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.
Does anyone have any idea whether this is likely to be a hardware problem or a
kernel problem?
Any suggestions for more ways to debug this would be greatfully received.
Thanks,
David.
next reply other threads:[~2006-10-12 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 16:53 David Johnson [this message]
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
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=200610121753.23220.dj@david-web.co.uk \
--to=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
Powered by JetHome