Subject: Re: "de0: transmit process stopped"
To: None <current-users@netbsd.org>
From: Peter Seebach <seebs@plethora.net>
List: current-users
Date: 12/19/2000 10:57:16
In message <m148Q1K-000Fz0C@shanghai.realtime.bc.ca>, David Querbach writes:
>> Is this our fault or theirs?  The fact that my intermediate kernel doesn't
>> get it makes it look like a change in our code - also, other systems run
>> on VPC4 just fine.  On the other hand, it didn't happen with VPC3.
>
>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...

I don't think that's the same thing.  The weird thing is that both 1.4.3
and 1.5 seem to have this problem, but 1.5_ALPHA doesn't with de0.  (It
does with tlp0).

I've sent in a report to Connectix, but part of the problem is that I
really don't know what this *means*.  Is this an interrupt we can just
ignore?  Should this interrupt be happening at all?

-s