Re: tulip driver problem

From: Lech Szychowski (lech.szychowski@pse.pl)
Date: Tue Aug 07 2001 - 05:44:13 EST

Next message: Andrzej Krzysztofowicz: "Re: How does "alias ethX drivername" in modules.conf work?"
Previous message: Jochen Striepe: "Re: Linux-2.4.8pre5 does not build"
In reply to: Albert D. Cahalan: "Re: tulip driver problem"
Next in thread: Colonel: "Re: tulip driver problem"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> eth0: Setting half-duplex based on MII#1 link partner capability of 0021.
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out
> NETDEV WATCHDOG: eth0: transmit timed out

Does eth0 share IRQ with any other card? I got the very same messages
when one of my 4-way Adaptec (tulip based) ports got assigned the same
IRQ as my SCSI card (53c810a). BTW, that forced me to swich to using
de4x5 driver...

-- Leszek.

-- lech7@pse.pl 2:480/33.7 -- REAL programmers use INTEGERS -- -- speaking just for myself... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Andrzej Krzysztofowicz: "Re: How does "alias ethX drivername" in modules.conf work?"
Previous message: Jochen Striepe: "Re: Linux-2.4.8pre5 does not build"
In reply to: Albert D. Cahalan: "Re: tulip driver problem"
Next in thread: Colonel: "Re: tulip driver problem"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Aug 07 2001 - 21:00:44 EST