"transmit timed out" with 3c509 on 2.0.38 and 2.2.13

• Next message: Bruce Stephens: "Re: Best Notebook(s)"
• Previous message: Kendall Lister: "Re: Req. reg. ipv4 addr. hashing"
• In reply to: Thomas Schenk: "eth0: transmit timed out Tx_status 00 status 2000 FIFO room 4092"
• Next in thread: Bruce Stephens: "Re: "transmit timed out" with 3c509 on 2.0.38 and 2.2.13"
• Reply: Bruce Stephens: "Re: "transmit timed out" with 3c509 on 2.0.38 and 2.2.13"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Jan 06, 2000 at 12:46:01PM -0600, Thomas Schenk wrote:

> Ever since upgrading a number of our servers to kernel 2.2.13, we have been
> receiving this error message in syslog regularly. Reverting back to 2.0.37
> eliminates this message. The card that is reporting the error is a 3C509.
> Has anyone seen this and is there a fix.

Just a heads up to say that I saw this the other day on one of my boxes
using kernel 2.0.38 (and a 3c509, obviously <g>). I've not done any
investigation into it as yet. I note you stepped back to 2.0.37 -- if you
can normally reproduce the problem easily, could try with 2.0.38? If so it
might implicate a driver change that went into 2.0.38 and 2.2.13.

I've changed the subject line in the hope it might grab someone's attention :-)

-- 
%DCL-MEM-BAD, bad memory
VMS-F-PDGERS, pudding between the ears
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu

• Next message: Bruce Stephens: "Re: Best Notebook(s)"
• Previous message: Kendall Lister: "Re: Req. reg. ipv4 addr. hashing"
• In reply to: Thomas Schenk: "eth0: transmit timed out Tx_status 00 status 2000 FIFO room 4092"
• Next in thread: Bruce Stephens: "Re: "transmit timed out" with 3c509 on 2.0.38 and 2.2.13"
• Reply: Bruce Stephens: "Re: "transmit timed out" with 3c509 on 2.0.38 and 2.2.13"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Jan 07 2000 - 21:00:13 EST