Subject: kern/33429: wm (intel gigabit ethernet) loses carrier/never gets carrier
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <perry@piermont.com>
List: netbsd-bugs
Date: 05/06/2006 17:30:00
>Number:         33429
>Category:       kern
>Synopsis:       wm (intel gigabit ethernet) loses carrier/never gets carrier
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 06 17:30:00 +0000 2006
>Originator:     Perry E. Metzger
>Release:        NetBSD 3.99.18
>Organization:
Perry E. Metzger		perry@piermont.com
--
"Ask not what your country can force other people to do for you..."
>Environment:
	
	
System: NetBSD hackworth 3.99.18 NetBSD 3.99.18 (HACKWORTH) #0: Thu Apr 27 15:04:36 EDT 2006 perry@hackworth:/usr/src/sys/arch/i386/compile/HACKWORTH i386
Architecture: i386
Machine: i386
>Description:
	My wm device frequently loses carrier and will not regain it
or fails to get carrier at all.

The device is:

wm0 at pci2 dev 1 function 0: Intel i82540EP 1000BASE-T Ethernet, rev. 3
wm0: interrupting at irq 11
wm0: 32-bit 33MHz PCI bus
wm0: 64 word (6 address bits) MicroWire EEPROM
wm0: Ethernet address 00:0d:60:77:41:d2
makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 4

It is the built in ethernet in an IBM T41 laptop.

I am sorry that I can't give more details, but it pretty much is as
simple as that. Sometimes it works just fine, sometimes it refuses to
work at all, and I can't predict why or when. As you might imagine it
is a big problem when one needs the network and it doesn't operate.

>How-To-Repeat:

Other than by trying a wm in an IBM T41, I don't know. :)
The behavior seems pretty consistent. It *may* depend on the
particular kind of switch I'm connected to but I can't really tell.

>Fix:
	

>Unformatted: