Date: Tue, 29 Jul 1997 17:10:39 -0400 From: Dennis Rockwell <dennis@bbn.com> To: spork <spork@super-g.com> Cc: questions@freebsd.org, David Greenman <dg@root.com> Subject: Re: de0 problem 2.2-STABLE Message-ID: <199707292110.RAA12348@zafu.bbn.com> In-Reply-To: Message from spork <spork@super-g.com> <Pine.BSF.3.95q.970728192433.1377B-100000@super-g.inch.com> .
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Jul, spork wrote: > de0 <Digital 21140A Fast Ethernet> rev 32 int a irq 12 on pci0:10 > de0: DE500-AA 21140A [10-100Mb/s] pass 2.0 > de0: address 00:00:f8:03:66:e9 > > It seems to work fine, unless I unplug the cable. At that point it logs > the message "de0: link down: cable problem?" > > I can "ifconfig de0 up" and bring it back, but that would be inconvenient > if I weren't at the console ;) I'm also responding to later messages about the link staying down. We have a bunch of those cards, too, and it appears that the driver marks the i/f down without telling the ethernet common code about it. For instance, I get the same message, but "ifconfig de0" still shows UP. If I "ifconfig de0 down; ifconfig de0 up" the link comes back up, and all is well. I haven't checked out the FreeBSD sources, but other Unices I've worked on shortstop the ioctl at the "ether" level if the apparent state doesn't change. Give down/up a shot before you give up on these cards. I agree that it would be nice if the driver would notice that the link came back up! Does it need to probe? Dennis Rockwell dennis@bbn.com Bolt Beranek & Newman Systems & Technologies +1-617-873-5745 Cambridge, MA +1-617-873-6091 (Fax)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707292110.RAA12348>