Date: Sun, 10 Dec 2000 11:41:20 +0100 From: Wilko Bulte <wkb@freebie.demon.nl> To: Bill Paul <wpaul@freebsd.org> Cc: jhb@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: cvs commit: src/sys/alpha/conf GENERIC Message-ID: <20001210114120.A9610@freebie.demon.nl> In-Reply-To: <20001209102145.C1CC137B400@hub.freebsd.org>; from wpaul@freebsd.org on Sat, Dec 09, 2000 at 02:21:45AM -0800 References: <20001209104038.A5866@freebie.demon.nl> <20001209102145.C1CC137B400@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 09, 2000 at 02:21:45AM -0800, Bill Paul wrote:
> I would have prefered it if you had put the cable in the tx0 interface
> and *then* ifconfig'ed it. Because you didn't do it this way, the
OK, I have tried this, cable connected before boot. Results below.
Look identical to me.
> results are a little ambiguous. I would also have prefered it if you
> had run tcpdump or checked netstat -in to see if you were receiving
> any packets even though you may not have been sending any.
OK, checked that as well. Tcpdump does not see anything on tx0 when
run on the Alpha. tcpdump when run on another host also does not see
anything from the Alpha on the wire (as expected)
> -Bill
>
> P.S.: I noticed that you have your dc0 interface hardcoded to 100baseTX.
> Did you set this manually or is this just the result of the NVRAM setting
It is not in rc.conf.. hmm <checks SRM setting> OK, it is hard set in SRM:
ewa0_mode Fast
Lets try:
>>>set ewa0_mode auto-negotiate
Change mode to auto negotiate
>>>
> on your particular alpha? Also, what alpha is it, and what happens if
This is a Miata 500/ MX5. Using
dc0: <Intel 21143 10/100BaseTX> port 0x9080-0x90ff mem 0x80960080-0x809600ff
irq 0 at device 3.0 on pci0
dc0: interrupting at CIA irq 0
dc0: Ethernet address: 00:00:f8:75:3c:6a
miibus0: <MII bus> on dc0
nsphy0: <DP83840 10/100 media interface> on miibus0
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> you do ifconfig dc0 media autoselect?
This gives me:
Doing initial network setup: hostname.
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.200.24 netmask 0xffffff00 broadcast 192.168.200.255
ether 00:00:f8:75:3c:6a
media: autoselect (100baseTX) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>
Works just fine on 100Mbit.
<transcript>
mx5# ifconfig tx0 192.168.200.24
mx5# tx0: can't stop Tx DMA
Dec 20 11:27:13 mx5 /kernel: tx0: can't stop Tx DMA
Dec 20 11:27:13 mx5 /kernel: tx0: can't stop Tx DMA
mx5# tx0: device timeout 1 packets, reinitialization
tx0: can't stop Tx DMA
Dec 20 11:27:21 mx5 /kernel: tx0: device timeout 1 packets, reinitialization
Dec 20 11:27:21 mx5 /kernel: tx0: device timeout 1 packets, reinitialization
Dec 20 11:27:21 mx5 /kernel: tx0: can't stop Tx DMA
Dec 20 11:27:21 mx5 /kernel: tx0: can't stop Tx DMA
mx5#
mx5# ifconfig -a
dc0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
ether 00:00:f8:75:3c:6a
media: autoselect (none) status: no carrier
supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>
tx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.200.24 netmask 0xffffff00 broadcast 192.168.200.255
ether 00:e0:29:15:b9:43
media: autoselect (100baseTX) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
mx5# ping 192.168.200.1
PING 192.168.200tx0: can't stop Tx DMA
.1 (192.168.200.1): 48 data bytes
Dec 20 11:28:29 mx5 /kernel: tx0: can't stop Tx DMA
Dec 20 11:28:29 mx5 /kernel: tx0: can't stop Tx DMA
^C
--- 192.168.200.1 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
mx5# tx0: device timeout 5 packets, reinitialization
tx0: can't stop Tx DMA
Dec 20 11:28:41 mx5 /kernel: tx0: device timeout 5 packets, reinitialization
Dec 20 11:28:41 mx5 /kernel: tx0: device timeout 5 packets, reinitialization
Dec 20 11:28:41 mx5 /kernel: tx0: can't stop Tx DMA
Dec 20 11:28:41 mx5 /kernel: tx0: can't stop Tx DMA
mx5# ping 192.168.200.1
PING 192.168.200.1 (192.168.200.1): 48 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.200.1 ping statistics ---
9 packets transmitted, 0 packets received, 100% packet loss
mx5# arp -a
? (192.168.200.1) at (incomplete) [ethernet]
mx5# tx0: device timeout 5 packets, reinitialization
tx0: can't stop Tx DMA
Dec 20 11:29:22 mx5 /kernel: tx0: device timeout 5 packets, reinitialization
Dec 20 11:29:22 mx5 /kernel: tx0: device timeout 5 packets, reinitialization
Dec 20 11:29:22 mx5 /kernel: tx0: can't stop Tx DMA
Dec 20 11:29:22 mx5 /kernel: tx0: can't stop Tx DMA
mx5#
--
Wilko Bulte Arnhem, the Netherlands
wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001210114120.A9610>