Subject: Re: "de0: transmit process stopped"
To: Peter Seebach <>
From: Peter A. Eisch <>
List: current-users
Date: 12/20/2000 00:07:37
> During bootup (on a normal machine with 1.5_ALPHA, not on VirtualPC,
> whatever that is), I often see something like "de0: transmitter stopped,
> cable problem?".  I don't know whether this is related...

Here is what the kernel logs:

de0 at pci0 dev 9 function 0
de0: interrupting at irq 11
de0: 21041 [10Mb/s] pass 1.1
de0: address 12:34:56:78:9a:04
de0: enabling 10baseT port

And everything is fine until the interface is brought up.   Whether if the
interface is brought up with an ifconfig command or via dhclient or

The log message comes from the tulip_printf_abnormal_interrupt which is only
called from a watchdog and from the interrupt handling.  The specific
message I get is:

de0: abnormal interrupt: transmit process stopped

Which doesn't really add much more info than what we had before.

I'm staged to where I can try stuff (I'm at 1.4.3) folks can think of,
though the compile-cycle time isn't very fast.