[eepro100] Second eepro100 recognized "Receiver Lock-Up bug",
but nothing gets done about it....
Tue, 13 Mar 2001 11:17:03 -0500
Thanks for your reply Donald.
I am sorry to report that passing "noapic" as an append statement or at the
terminal, has no affect to the behavior.
So, what you are saying, that there is no problems directly with drivers and
Thanks for your help Donald!
Red Hat Linux Certified Engineer (R.H.C.E.)
Systems Engineer | Engineering Department
(678) 365-2849 | firstname.lastname@example.org
Interland, Inc. | www.interland.com
From: Donald Becker [mailto:email@example.com]
Sent: Tuesday, March 13, 2001 10:45 AM
To: Graham Wooden
Cc: 'firstname.lastname@example.org'; Eric Van Wieren
Subject: Re: [eepro100] Second eepro100 recognized "Receiver Lock-Up
bug", but nothing ge ts done about it....
On Tue, 13 Mar 2001, Graham Wooden wrote:
> I have a HP LT6000 with an on-board Intel Pro 100 NIC and a PCI Intel
> EtherExpress NIC.
> I am having a problem with the PCI one, eth1.
> According to dmesg, for eth0, it's found the receiver bug, and the work
> around gets activated.
> And for eth1, its say it does exist, and stats enabling work around, but
The receive lock-up work-around is pretty rare, and likely unrelated to
> Eth1 goes to sleep about 3-4 minutes after I disconnect from the machine.
> The only way I can get Eth1 to respond is to have activity on eth0.
This sounds like an IRQ mapping problem.
Try passing the kernel option 'noapic' on the boot line.
Donald Becker email@example.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993