From owner-freebsd-alpha Sun Dec 10 2:41:44 2000 From owner-freebsd-alpha@FreeBSD.ORG Sun Dec 10 02:41:40 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 791A737B400; Sun, 10 Dec 2000 02:41:39 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 1453vF-000Pd9-00; Sun, 10 Dec 2000 10:41:37 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eBAAfK909696; Sun, 10 Dec 2000 11:41:20 +0100 (CET) (envelope-from wkb) Date: Sun, 10 Dec 2000 11:41:20 +0100 From: Wilko Bulte To: Bill Paul Cc: jhb@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: cvs commit: src/sys/alpha/conf GENERIC Message-ID: <20001210114120.A9610@freebie.demon.nl> References: <20001209104038.A5866@freebie.demon.nl> <20001209102145.C1CC137B400@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001209102145.C1CC137B400@hub.freebsd.org>; from wpaul@freebsd.org on Sat, Dec 09, 2000 at 02:21:45AM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 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: 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: on dc0 nsphy0: 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 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 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX Works just fine on 100Mbit. 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 mtu 1500 ether 00:00:f8:75:3c:6a media: autoselect (none) status: no carrier supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX tx0: flags=8843 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 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX lo0: flags=8049 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