Subject: Re: vr0 transmit aborted on arm32/1.4.2_ALPHA
To: Todd Whitesel <firstname.lastname@example.org>
From: Greg Oster <email@example.com>
Date: 01/27/2000 10:50:04
Todd Whitesel writes:
> I have two very similar arm32/i386 systems here running 1.4.2_ALPHA.
> They can be similar because the arm32 is a CATS ATX board. The i386 has
> the same ALi SuperIO on it, and both machines have very similar peripherals.
> However, the i386 has been happily using vr0 (D-Link DFE 530TX) for months,
> and I finally got around to upgrading the CATS from ne0 to vr0 last night.
> It works, but I get these messages on the console when FTP'ing large files:
> vr0: transmit aborted
> what to do about this? the i386 never gets it.
Under 1.4.1 on i386 with the same D-Link DFE 530TX card:
vr0 at pci0 dev 10 function 0: VIA VT3043 (Rhine) 10/100 Ethernet Ethernet
vr0: interrupting at irq 5
vr0: Ethernet address: 00:80:c8:xx:xx:xx
OUI 0x006040 model 0x0000 rev 0 at vr0 phy 8 not configured
I see that error lots:
Jan 19 16:28:57 aladdin /netbsd: vr0: transmit aborted
Jan 19 16:38:16 aladdin last message repeated 31 times
> Should I ask the CATS people if there are DMA oddities or something?
I'm seeing the above on two similarly configured machines, both of which have
ASUS P2B motherboards. I'm not sure what causes that message to be displayed,
and it hasn't seemed to be causing any major problems, so I havn't been too
worried about it... (although maybe I should be??)