NetBSD Problem Report #10289
Received: (qmail 20071 invoked from network); 5 Jun 2000 18:30:53 -0000
Message-Id: <200006051830.e55IUqx05533@shiner-bock.cs.stevens-tech.edu>
Date: Mon, 5 Jun 2000 14:30:52 -0400 (EDT)
From: tls@cs.stevens-tech.edu
Reply-To: tls@cs.stevens-tech.edu
To: gnats-bugs@gnats.netbsd.org
Subject: "ex" driver doesn't work with newer cards/onboard chips
X-Send-Pr-Version: 3.95
>Number: 10289
>Category: kern
>Synopsis: The first "ifconfig" operation makes "ex" permanently lose carrier with newer cards.
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jun 05 18:31:00 +0000 2000
>Closed-Date: Sun Mar 27 17:12:00 +0000 2005
>Last-Modified: Sun Mar 27 17:12:00 +0000 2005
>Originator:
>Release: 20000601
>Organization:
Stevens Institute of Technology
>Environment:
System: NetBSD shiner-bock.cs.stevens-tech.edu 1.4Z NetBSD 1.4Z (BOCK) #1: Thu Jun 1 13:18:04 EDT 2000 root@amstel.cs.stevens-tech.edu:/usr/src/sys/arch/i386/compile/BOCK i386
>Description:
On a newer "ex" (3c905) card such as a 3c905-TX-NM or the embedded
"3c905-TX" on newer Dell machines such as the Precision Workstation
410, the first "ifconfig" operation done on the card will make the
card go from "active" to "no carrier" status, evidently after a
failed attempt to negotiate media type with the switch. Explicitly
setting a media type (e.g. 100baseTX, 100baseTX-FDX, 10baseT) does not
help. Until the initial "ifconfig" is done, oddly enough, the card
appears to have correctly autonegotiated 100baseTX-FDX mode with our
Cisco 3524 switch. (you can check this with "ifconfig" if you *don't*
set anything -- setting anything at all screws it up)
I'm not sure why, but there's a substantial system pause -- a second
or so -- after the initial "ifconfig" operation that breaks things,
but not after subsequent ones. I recall there used to be some
DELAY calls in the mii or phy code; perhaps these are at fault?
I have not been able to find our sole 905-TX-NM card in some time
to reproduce this problem, but it did seem to occur there. That
card has a PHY that probes as a ukphy. Older Dell machines with
embedded "905-TX" chips have had nsphy and those don't seem to have
the problem. Our new ones have exphy and the problem exists; the
problem *still* exists if exphy's not built into the kernel and
ukphy attaches instead.
It's getting hard to buy a machine from a number of major PC
manufacturers that does *not* exhibit this problem -- anything
built in the last few months with onboard 3Com ethernet and
exphy seems to lose this way, and that describes pretty much every
machine anyone naive on this campus, at least, has bought in the
last few months.
Curiously, ukphy listed all-zeroes for the OUI and whatever the
other PHY identifier is.
>How-To-Repeat:
Find a Dell Precision 410 or other new machine with onboard "ex".
Connect to a Cisco 3524 switch (unconfirmed, but this probably
happens with other switches as well -- it does happen with two
of these machines back-to-back with an xover cable). Boot an
install disk. Try to get the interface set up so you can install
over the net. Boom.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
From: nathanw@MIT.EDU (Nathan J. Williams)
To: tls@cs.stevens-tech.edu
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10289: "ex" driver doesn't work with newer cards/onboard chips
Date: 08 Jun 2000 11:30:04 -0400
tls@cs.stevens-tech.edu writes:
> >How-To-Repeat:
> Find a Dell Precision 410 or other new machine with onboard "ex".
> Connect to a Cisco 3524 switch (unconfirmed, but this probably
> happens with other switches as well -- it does happen with two
> of these machines back-to-back with an xover cable). Boot an
> install disk. Try to get the interface set up so you can install
> over the net. Boom.
I saw very similar failures with the onboard "ex" on my Precision 410,
connected to a plain-jane 10Mbps hub.
- Nathan
State-Changed-From-To: open->feedback
State-Changed-By: chs@netbsd.org
State-Changed-When: Mon, 14 Feb 2005 01:15:51 +0000
State-Changed-Why:
the ex driver has had lots of fixes in the years since your report,
are you still seeing this problem in 2.0 or -current?
State-Changed-From-To: feedback->closed
State-Changed-By: chs@netbsd.org
State-Changed-When: Sun, 27 Mar 2005 17:12:00 +0000
State-Changed-Why:
feedback timeout, we'll assume it's not a problem anymore.
if you do see this problem again, please file a new PR.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.