Re: Command 80 was not immediately accepted, 10001 ticks!

Donald Becker <[email protected]> wrote:

> > Nov 29 13:10:37 kernel: eth0: Command 80 was not immediately accepted, 10001 ticks!
> > Nov 29 13:10:44 kernel: eth0: Transmit timed out: status 0050  0080 at 39064/39066 commands 000c0000 400c0000 000ca000.
> 
> This is the driver trying to restart the chip, but the chip firmware is
> now confused.  There might be some useful information from the very
> first problem message.

Thanks for the quick response.

The quoted extract from the logs was in fact the first problem message.
It occurred many hours after the previous log entry (someone logging out).

There was probably more info generated that wasn't logged and the 'dmesg'
buffer would long since have wrapped before I got to it.

> The usual cause of this problem is an incorrect motherboard chipset
> configuration.  The solution is a BIOS update.

Do you mean that that is the cause of the original problem or that it
is the cause of the failure to recover?

There is a BIOS update available for the machine in question but no
details regarding its revision history.  I can try it, I guess.

Is the problem described likely to be related to the earlier problem I
was having (wait_for_cmd_done timeout! errors)?

I'm still curious as to why the problem suddenly appeared after some 18
months of problem-free operation.  Any ideas?

Cheers,

Mark

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm