NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/50150: wm(4) failure

>Number:         50150
>Category:       kern
>Synopsis:       wm(4) failure
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 17 13:45:00 +0000 2015
>Originator:     Hauke Fath
>Release:        NetBSD 7.0_RC2
Technische Universitaet Darmstadt
System: NetBSD Vertatscha 7.0_RC2 NetBSD 7.0_RC2 (FIFI-$Revision: 1.85 $) #0: Fri Aug 7 16:16:59 CEST 2015 hf@Hochstuhl:/var/obj/netbsd-builds/7/amd64/sys/arch/amd64/compile/FIFI amd64
Architecture: x86_64
Machine: amd64

	On a router running netbsd-7, one wm(4) interface

wm5 at pci8 dev 0 function 0: Intel i82574L (rev. 0x00)
wm5: interrupting at ioapic0 pin 19
wm5: Ethernet address 00:25:90:af:ed:cf
makphy1 at wm5 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto

	has failed three times so far over a course of two months.
	The wm5 interface is one of two onboard NICs. It has five
	vlans configured on it. The other onboard NIC, wm4, has one
	vlan, but sees considerably more traffic, and performs

	In addition, there is a four-port NIC pci-e card of type
	82571EB, whose interfaces wm0 ... wm3 also perform flawlessly.

	During the failure, the kernel logs a lot of

wm5: device timeout (txfree 4089 txsfree 57 txnext 7)

	style messages. At this point, the interface is down, reporting
	"no carrier":

        address: 00:25:90:af:ed:cf
        media: Ethernet autoselect (none)
        status: no carrier
        inet6 fe80::225:90ff:feaf:edcf%wm5 prefixlen 64 detached scopeid 0x6

	Since the router had to come back up as quick as possible, we
	did not take the time to check whether an 'ifconfig wm5 down ;
	ifconfig wm5 up' could have brought the NIC back in line.


	Configure a handful of vlans on an Intel i82574L wm(4) NIC,
	run traffic, and wait, I guess?
	None known.


Home | Main Index | Thread Index | Old Index