From: William Montgomery <william@opinicus.com>
To: linux-kernel@vger.kernel.org
Subject: e100 driver hard lockups with AEI-P430C 4 port card
Date: Wed, 11 Jul 2007 16:49:55 -0400 [thread overview]
Message-ID: <46954273.9090207@opinicus.com> (raw)
Hello,
The AEI-P430C PCI 10/100 Quad Fast Ethernet card causes two computers to
lockup
hard but runs OK on a third computer. I have spent several days trying to
determine the cause. I have used the following OS/driver combos:
Slackware 10.1 Linux kernel 2.6.17 / eepro100 / e100
Slackware 10.1 Linux kernel 2.6.13 / eepro100 / e100
Slackware 9.1 Linux kernel 2.4.22 / e100
The following computer hardware configurations were used:
PC_1: Rackmount Industrial PC (Advantech 4U chassis)
12 slot PCI backplane (Advantech)
Pentium 4 2.80GHz, 512M Ram PCMIG (Advantech)
PC_2: Rackmount Industrial PC (Axiomtek 4U chassis)
12 slot PCI backplane (Axiomtek)
Pentium 4 3.00GHz, 512M Ram PCMIG (Axiomtek)
PC_3: Desktop (ShuttleX)
1 AGP, 1 PCI slot motherboard with Pentium 4 2.80GHz, 512M Ram
The hard lockups occur on PC_1 and PC_2 but not on PC_3. I have used
all three
OS/driver combos on PC_1 and PC_2 to try to eliminate the OS/driver as the
problem; in each case the lockup is repeatable within a few minutes of heavy
traffic. The test script uses the "iperf" utility which measures
bandwidth on
an ethernet port by moving as much data as possible in 10 seconds then
computing bandwidth. The script runs iperf on 3 ports simultaneously and
repeats until killed. I have tested the AEI card by connecting to 3
separate
Intel PRO/100 S cards and (in trying a different configuration) by
connecting
it to a Routerboard RB44 (4 port card).
I have tried the obvious methods to get an oops but no success so far.
I have
enabled the Magic SysRq key and enabled the NMI watchdog. The lockup is so
hard that none of these works. The only thing that brings the CPU out
of the
lockup is the i810 watchdog but that causes a reset/reboot and no oops so I
cant see any backtrace info. Any suggestions would be welcome.
Regards,
William Montgomery
reply other threads:[~2007-07-11 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46954273.9090207@opinicus.com \
--to=william@opinicus.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