Re: Can't get i82557 working with 2.4.20

Donald Becker <[email protected]> Sat, 5 Apr 2003 06:56:37 -0500 (EST)
Newsgroups gmane.linux.drivers.eepro100.devel
Message-ID <[email protected]>
[[ I apologize for the delayed messages.  We switched the driver support
web pages over to a high-bandwidth external hosting service over a month
ago, but have had several getting the mailing list working properly on
the new server.   -Donald Becker ]]

On Fri, 28 Mar 2003, Francesco Vivoli wrote:
...
> eth1: OEM i82557/i82558 10/100 Ethernet, 00:20:ED:14:BA:87, IRQ 10.
> Mar 26 12:50:52 sql kernel:   Board assembly 727095-004, Physical connectors
> present: RJ45
> Mar 26 12:50:52 sql kernel:   Primary interface chip i82555 PHY #1.
...
> What I have done is:
> -downloaded netdrivers and compiled it.

Good.

> -after the reboot the interfaces are up andf running but I notice these
> messages in the log:
> _______
> eth1: OEM Intel i82559 rev 8 at 0xe0835000, 00:20:ED:14:BB:07, IRQ 26.
> Mar 28 11:33:38 mail kernel:   Board assembly 727095-004, Physical
> connectors present: RJ45
> Mar 28 11:33:38 mail kernel:   Primary interface chip i82555 PHY #1.
> Mar 28 11:33:38 mail kernel:
> Mar 28 11:33:38 mail kernel:   ** The configuration EEPROM enables Sleep
> Mode.
> Mar 28 11:33:38 mail kernel:
> Mar 28 11:33:38 mail kernel:   ** This will cause PCI bus errors!
> Mar 28 11:33:38 mail kernel:   ** Update the configuration EEPROM with the
> eepro100-diag program.
..
> Reading some post I have figured out the problem but not how to correct
> this; I have to use eepro100-diag but I don't know the parameters (being
> this a live system I can't afford-programmed EEPROM)...

Just run the eepro100-diag program and it will tell the correct options
for that release version
   eepro100-diag -e
... 
   Sleep mode is enabled.  This is not recommended.
   Under high load the card may not respond to
   PCI requests, and thus cause a master abort.
   To clear sleep mode use the '-G 0 -w -w -f' options.


> Beside this error I get messages
> IRQ 26 is physically blocked! (2050)Failing back to low-rate polling. The
> effect is a bit strange: I can ping from the box but not to the box...
> I have read that in this case disabling APIC support in the kernel should
> work, it's true? And at what cost?

That's the serious problem.
The kernel start-up messages might show a message about something going
wrong with IRQ assignment.   If so, follow that advice.
Otherwise
    - Change the BIOS setup parameters to see if there is a change
    - Try a different kernel version
    - Turn off APIC support

Disabling APIC support is not always a bad thing.  In some cases you
will see a performance increase.  We ship our distribution, intended for
high-performance clusters, with the APIC support disabled for kernels
before 2.4.18.

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993