Date: Fri, 21 Feb 2003 08:27:26 -0800 From: "Kevin Oberman" <oberman@es.net> Cc: current@freebsd.org Subject: Re: Ethernet (xl) will not transmit or receive Message-ID: <20030221162727.F1A615D04@ptavv.es.net> In-Reply-To: Your message of "Thu, 20 Feb 2003 08:19:05 PST." <20030220161905.BBA6D5D04@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Thu, 20 Feb 2003 08:19:05 -0800 > From: "Kevin Oberman" <oberman@es.net> > Sender: owner-freebsd-current@FreeBSD.ORG > > I updated my 5.0 system built in late January to RELENG_5_0 on Sunday > and the Ethernet was not working. I tried again last night with no > change in behavior. > > The system is an AMD K6-2 on an ASUS P5A mobo. I have a 3Com 3c905B > Ethernet which had been working fine on a kernel built in late > January. > > The dmesg is not too meaningful, but the system shows no errors. It > simply never receives a packet. ARPs are all incomplete and no packets > are transmitted although netstat -in indicates that they are. The > packets never actually reach the wire, though. > > I can't believe that no one else has this card, but I didn't find > anything in the archives on it. > > Any idea what needs to be rolled back and how far? I'm suspicious that > it might be an mii problem. Maybe even an interrupt issue. I an > suspicious of the second, empty xlphy0: line in the dmesg, but the > reported MAC is right and my old kernel that works seems to generate a > similar empty line. To follow up with more information: Several folks suggested ifconfiging the interface down and up (or down and up with media and mediaopt specified). This did not help at all. ifconfig shows the interface as up but in hardware loopback at 100BaseTX. I see no link on the line and the status line in the ifconfig output is blank. I tried to force it to 10BaseT/UTP and half-duplex, but this did not work. When the system boots I see link until the device probes. After about 1-2 seconds, link is restored. This is identical to what I see with the January kernel. Then, when the network is started, the link goes out and stays out. I have not had time to try instrumenting the network startup to see exactly which command does this, but may get a chance this weekend. The system in question is at home and it's a bit hard to deal with remotely since I lose connectivity if the system boots the new V5 kernel. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030221162727.F1A615D04>