From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Locked up 2.4.10-pre11 on Tyan 815t motherboard.
Date: Tue, 18 Sep 2001 23:51:52 -0700 [thread overview]
Message-ID: <3BA84088.27698798@candelatech.com> (raw)
I was running a network stress test (sending lots of 64 byte packets
on the DLINK 4-port NIC and two EEPRO-100 NICs. This ran for 5 minutes,
and all was good (about 12Mbps of 64byte packets)..
Then, I re-started the test with 128 byte packets. As soon as traffic
started, the whole machine locked up. Couldn't even ping it from another
machine. I had to hold down the power-switch for about 5 seconds before
it reset (ie it wasn't even listening to the power-down??)
I'm using the eepro100 driver that is included in the kernel, btw. This
used to have a lockup problem, but I thought it was fixed...
I'm going to see if I can re-produce this. If so, can someone suggest
a way to get more/better debugging information??
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next reply other threads:[~2001-09-19 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 6:51 Ben Greear [this message]
2001-09-19 7:10 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard Ben Greear
[not found] ` <3BA8CCF1.CA2933B3@zip.com.au>
[not found] ` <3BA8D351.F57BE70D@candelatech.com>
[not found] ` <3BA8D619.9A607219@zip.com.au>
2001-09-19 18:09 ` Ben Greear
2001-09-24 15:14 ` bill davidsen
2001-09-24 18:18 ` Ben Greear
2001-09-19 18:38 ` Bruce Harada
2001-09-19 19:15 ` Alan Cox
2001-09-19 19:53 ` Ben Greear
2001-09-19 20:03 ` Jeff Garzik
2001-09-19 20:05 ` Alan Cox
2001-09-19 20:40 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard. [EEPRO-100 bugs] Ben Greear
2001-09-19 21:57 ` Alan Cox
2001-09-20 19:28 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard Martin Josefsson
2001-09-19 19:46 ` Ben Greear
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=3BA84088.27698798@candelatech.com \
--to=greearb@candelatech.com \
--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;
as well as URLs for NNTP newsgroup(s).