NetBSD Problem Report #51904

From www@NetBSD.org  Sun Jan 22 09:04:28 2017
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id AB2DA7A210
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 22 Jan 2017 09:04:28 +0000 (UTC)
Message-Id: <20170122090425.E96877A2B7@mollari.NetBSD.org>
Date: Sun, 22 Jan 2017 09:04:25 +0000 (UTC)
From: wgstuken@grimme-reitenspezial.de
Reply-To: wgstuken@grimme-reitenspezial.de
To: gnats-bugs@NetBSD.org
Subject: wm driver instable on SuperMicro X8SIL server board
X-Send-Pr-Version: www-1.0

>Number:         51904
>Category:       kern
>Synopsis:       wm driver instable on SuperMicro X8SIL server board
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 22 09:05:00 +0000 2017
>Last-Modified:  Sun Mar 11 23:40:00 +0000 2018
>Originator:     Wolfgang Stukenbrock
>Release:        7.0.1
>Organization:
>Environment:
NetBSD dyn016 7.0.1 NetBSD 7.0.1 (GENERIC) #1: Sat Jan 14 22:14:24 CET 2017  wgstuken@websvr:/home.stand/wgstuken/netbsd/NetBSD-7.x/N+C-build/.OBJDIR_amd64/home.stand/wgstuken/netbsd/NetBSD-7.x/src/sys/arch/amd64/compile/GENERIC amd64

>Description:
In general the system runs fine, but after a while while dooing network traffic the interface locks up. No way found to restart the interface till now - reboot required.

In the dmesg buffer the systems starts injecting messages like the following in a never ending loop:



wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0


If you try to send some packets (with pin in this case) you will see the following sequence:


wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4095 txsfree 63 txnext 1)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4091 txsfree 59 txnext 5)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4095 txsfree 63 txnext 1)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4095 txsfree 63 txnext 1)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4093 txsfree 61 txnext 3)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4093 txsfree 61 txnext 3)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4095 txsfree 63 txnext 1)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 16
wm0: MDIC write error: phy 1 reg 0
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4093 txsfree 61 txnext 3)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4095 txsfree 63 txnext 1)
wm0: MDIC write error: phy 1 reg 4
wm0: MDIC write error: phy 1 reg 9
wm0: MDIC write error: phy 1 reg 0
wm0: device timeout (txfree 4095 txsfree 63 txnext 1)
wm0: MDIC write error: phy 1 reg 4


In this case the problem happens while running ftp mget from an other server connected via 100 MBit LAN, but it also happens while using NFS or ftp from a non-local side.

output of kernel messages during boot follows:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 7.0.1 (GENERIC) #1: Sat Jan 14 22:14:24 CET 2017
        wgstuken@websvr:/home.stand/wgstuken/netbsd/NetBSD-7.x/N+C-build/.OBJDIR_amd64/home.stand/wgstuken/netbsd/NetBSD-7.x/src/sys/arch/amd64/compile/GENERIC
total memory = 16375 MB
avail memory = 15882 MB
kern.module.path=/stand/amd64/7.0/modules
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
Supermicro X8SIL (0123456789)
mainbus0 (root)
ACPI: RSDP 0xfa280 000024 (v02 ACPIAM)
ACPI: XSDT 0xbf7a0100 000084 (v01 SMCI            20100527 MSFT 00000097)
ACPI: FACP 0xbf7a0290 0000F4 (v04 052710 FACP1450 20100527 MSFT 00000097)
ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20131218/tbfadt-634)
ACPI: DSDT 0xbf7a05f0 006C7B (v02  10605 10605000 00000000 INTL 20051117)
ACPI: FACS 0xbf7ae000 000040
ACPI: APIC 0xbf7a0390 000092 (v02 052710 APIC1450 20100527 MSFT 00000097)
ACPI: MCFG 0xbf7a0430 00003C (v01 052710 OEMMCFG  20100527 MSFT 00000097)
ACPI: OEMB 0xbf7ae040 000073 (v01 052710 OEMB1450 20100527 MSFT 00000097)
ACPI: HPET 0xbf7aa5f0 000038 (v01 052710 OEMHPET  20100527 MSFT 00000097)
ACPI: GSCI 0xbf7ae0c0 002024 (v01 052710 GMCHSCI  20100527 MSFT 00000097)
ACPI: DMAR 0xbf7b00f0 000090 (v01    AMI  OEMDMAR 00000001 MSFT 00000097)
ACPI: SSDT 0xbf7b1dc0 000363 (v01 DpgPmm    CpuPm 00000012 INTL 20051117)
ACPI: EINJ 0xbf7aa630 000130 (v01  AMIER AMI_EINJ 20100527 MSFT 00000097)
ACPI: BERT 0xbf7aa7c0 000030 (v01  AMIER AMI_BERT 20100527 MSFT 00000097)
ACPI: ERST 0xbf7aa7f0 0001B0 (v01  AMIER AMI_ERST 20100527 MSFT 00000097)
ACPI: HEST 0xbf7aa9a0 0000A8 (v01  AMIER ABC_HEST 20100527 MSFT 00000097)
ACPI: All ACPI Tables successfully acquired
ioapic0 at mainbus0 apid 8: pa 0xfec00000, version 0x20, 24 pins
cpu0 at mainbus0 apid 0: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu1 at mainbus0 apid 2: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu2 at mainbus0 apid 4: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu3 at mainbus0 apid 6: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu4 at mainbus0 apid 1: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu5 at mainbus0 apid 3: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu6 at mainbus0 apid 5: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
cpu7 at mainbus0 apid 7: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz, id 0x106e5
acpi0 at mainbus0: Intel ACPICA 20131218
acpi0: X/RSDT: OemId <SMCI  ,        ,20100527>, AslId <MSFT,00000097>
ACPI BIOS Warning (bug): Incorrect checksum in table [OEMB] - 0xA4, should be 0xA1 (20131218/tbprint-237)
ACPI: SSDT 0xbf7b0180 0015DC (v01 DpgPmm  P001Ist 00000011 INTL 20051117)
ACPI: SSDT 0x0 0015DC (v01 DpgPmm  P001Ist 00000011 INTL 20051117)
ACPI: SSDT 0xbf7b1760 000659 (v01  PmRef  P001Cst 00003001 INTL 20051117)
ACPI: SSDT 0x0 000659 (v01  PmRef  P001Cst 00003001 INTL 20051117)
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
IOH (PNP0C01) at acpi0 not configured
attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
midi0 at pcppi1: PC speaker
sysbeep0 at pcppi1
UAR1 (PNP0501) at acpi0 not configured
UAR2 (PNP0501) at acpi0 not configured
SIO2 (PNP0C02) at acpi0 not configured
SIOR (PNP0C02) at acpi0 not configured
RMSC (PNP0C02) at acpi0 not configured
OMSC (PNP0C02) at acpi0 not configured
PCIE (PNP0C02) at acpi0 not configured
RMEM (PNP0C01) at acpi0 not configured
acpibut0 at acpi0 (PWRB, PNP0C0C-170): ACPI Power Button
ACPI: Enabled 2 GPEs in block 00 to 3F
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-646)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131218/hwxface-646)
attimer1: attached to pcppi1
ipmi: bus_space_map(..., ca0, 2, 0, 0xffffffff81268be8) failed
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 0x8086 product 0xd130 (rev. 0x11)
ppb0 at pci0 dev 3 function 0: vendor 0x8086 product 0xd138 (rev. 0x11)
ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x8 @ 5.0GT/s
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
ppb1 at pci0 dev 5 function 0: vendor 0x8086 product 0xd13a (rev. 0x11)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x8 @ 5.0GT/s
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
vendor 0x8086 product 0xd155 (miscellaneous system, revision 0x11) at pci0 dev 8 function 0 not configured
vendor 0x8086 product 0xd156 (miscellaneous system, revision 0x11) at pci0 dev 8 function 1 not configured
vendor 0x8086 product 0xd157 (miscellaneous system, revision 0x11) at pci0 dev 8 function 2 not configured
vendor 0x8086 product 0xd158 (miscellaneous system, revision 0x11) at pci0 dev 8 function 3 not configured
vendor 0x8086 product 0xd150 (miscellaneous system, revision 0x11) at pci0 dev 16 function 0 not configured
vendor 0x8086 product 0xd151 (miscellaneous system, revision 0x11) at pci0 dev 16 function 1 not configured
ehci0 at pci0 dev 26 function 0: vendor 0x8086 product 0x3b3c (rev. 0x05)
ehci0: interrupting at ioapic0 pin 21
ehci0: EHCI version 1.0
usb0 at ehci0: USB revision 2.0
ppb2 at pci0 dev 28 function 0: vendor 0x8086 product 0x3b42 (rev. 0x05)
ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x4 @ 2.5GT/s
pci3 at ppb2 bus 3
pci3: i/o space, memory space enabled, rd/line, wr/inv ok
ppb3 at pci0 dev 28 function 4: vendor 0x8086 product 0x3b4a (rev. 0x05)
ppb3: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 2.5GT/s
pci4 at ppb3 bus 4
pci4: i/o space, memory space enabled, rd/line, wr/inv ok
wm0 at pci4 dev 0 function 0: Intel i82574L (rev. 0x00)
wm0: interrupting at ioapic0 pin 16
wm0: PCI-Express bus
wm0: 2048 words (8 address bits) SPI EEPROM
wm0: Ethernet address 00:25:90:61:0d:ba
makphy0 at wm0 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ppb4 at pci0 dev 28 function 5: vendor 0x8086 product 0x3b4c (rev. 0x05)
ppb4: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 2.5GT/s
pci5 at ppb4 bus 5
pci5: i/o space, memory space enabled, rd/line, wr/inv ok
wm1 at pci5 dev 0 function 0: Intel i82574L (rev. 0x00)
wm1: interrupting at ioapic0 pin 17
wm1: PCI-Express bus
wm1: 512 words (8 address bits) SPI EEPROM
wm1: Ethernet address 00:25:90:61:0d:bb
makphy1 at wm1 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ehci1 at pci0 dev 29 function 0: vendor 0x8086 product 0x3b34 (rev. 0x05)
ehci1: interrupting at ioapic0 pin 23
ehci1: EHCI version 1.0
usb1 at ehci1: USB revision 2.0
ppb5 at pci0 dev 30 function 0: vendor 0x8086 product 0x244e (rev. 0xa5)
pci6 at ppb5 bus 6
pci6: i/o space, memory space enabled
vga0 at pci6 dev 3 function 0: vendor 0x102b product 0x0532 (rev. 0x0a)
wsdisplay0 at vga0 kbdmux 1
wsmux1: connecting to wsdisplay0
drm at vga0 not configured
ichlpcib0 at pci0 dev 31 function 0: vendor 0x8086 product 0x3b14 (rev. 0x05)
timecounter: Timecounter "ichlpcib0" frequency 3579545 Hz quality 1000
ichlpcib0: 24-bit timer
ichlpcib0: TCO (watchdog) timer configured.
ahcisata0 at pci0 dev 31 function 2: vendor 0x8086 product 0x3b22 (rev. 0x05)
ahcisata0: interrupting at ioapic0 pin 19
ahcisata0: 64-bit DMA
ahcisata0: AHCI revision 1.30, 6 ports, 32 slots, CAP 0xef20ff65<SXS,EMS,PSC,SSC,PMD,ISS=0x2=Gen2,SCLO,SAL,SALP,SSS,SSNTF,SNCQ,S64A>
atabus0 at ahcisata0 channel 0
atabus1 at ahcisata0 channel 1
atabus2 at ahcisata0 channel 2
atabus3 at ahcisata0 channel 3
atabus4 at ahcisata0 channel 4
atabus5 at ahcisata0 channel 5
ichsmb0 at pci0 dev 31 function 3: vendor 0x8086 product 0x3b30 (rev. 0x05)
ichsmb0: interrupting at ioapic0 pin 18
iic0 at ichsmb0: I2C bus
isa0 at ichlpcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: FFH, lat   1 us, pow  1000 mW
acpicpu0: C2: FFH, lat  17 us, pow   500 mW
acpicpu0: C3: FFH, lat  17 us, pow   350 mW
acpicpu0: P0: FFH, lat  10 us, pow 55000 mW, 1868 MHz, turbo boost
acpicpu0: P1: FFH, lat  10 us, pow 45000 mW, 1867 MHz
acpicpu0: P2: FFH, lat  10 us, pow 35000 mW, 1733 MHz
acpicpu0: P3: FFH, lat  10 us, pow 27000 mW, 1600 MHz
acpicpu0: P4: FFH, lat  10 us, pow 21000 mW, 1467 MHz
acpicpu0: P5: FFH, lat  10 us, pow 16000 mW, 1333 MHz
acpicpu0: P6: FFH, lat  10 us, pow 11000 mW, 1200 MHz
coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=70
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=70
acpicpu2 at cpu2: ACPI CPU
coretemp2 at cpu2: thermal sensor, 1 C resolution, Tjmax=70
acpicpu3 at cpu3: ACPI CPU
coretemp3 at cpu3: thermal sensor, 1 C resolution, Tjmax=70
acpicpu4 at cpu4: ACPI CPU
acpicpu5 at cpu5: ACPI CPU
acpicpu6 at cpu6: ACPI CPU
acpicpu7 at cpu7: ACPI CPU
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "TSC" frequency 1866776320 Hz quality 3000
IPsec: Initialized Security Association Processing.
uhub0 at usb0: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub1 at usb1: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ahcisata0 port 1: device present, speed: 3.0Gb/s
ahcisata0 port 5: device present, speed: 1.5Gb/s
ahcisata0 port 0: device present, speed: 3.0Gb/s
ahcisata0 port 2: device present, speed: 3.0Gb/s
ahcisata0 port 3: device present, speed: 3.0Gb/s
wd0 at atabus0 drive 0
wd0: <Hitachi HTS723216A7A364>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd1 at atabus1 drive 0
wd1: <Hitachi HTS723216A7A364>
wd1: drive supports 16-sector PIO transfers, LBA48 addressing
wd1: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
uhub2 at uhub0 port 1: vendor 0x8087 product 0x0020, class 9/0, rev 2.00/0.00, addr 2
uhub2: single transaction translator
uhub2: 6 ports with 6 removable, self powered
uhub3 at uhub1 port 1: vendor 0x8087 product 0x0020, class 9/0, rev 2.00/0.00, addr 2
uhub3: single transaction translator
uhub3: 8 ports with 8 removable, self powered
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd2 at atabus2 drive 0
wd2: <Hitachi HTS727550A9E364>
wd2: drive supports 16-sector PIO transfers, LBA48 addressing
wd2: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors
wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd2(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd3 at atabus3 drive 0
wd3: <Hitachi HTS727550A9E364>
wd3: drive supports 16-sector PIO transfers, LBA48 addressing
wd3: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors
wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd3(ahcisata0:3:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
atapibus0 at atabus5: 1 targets
cd0 at atapibus0 drive 0: <HL-DT-ST DVDRAM GH22NS50, K3ZB34E4028, TN03> cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
cd0(ahcisata0:5:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA)
uhidev0 at uhub3 port 4 configuration 1 interface 0
uhidev0: vendor 0x046a product 0x0011, rev 2.00/1.00, addr 3, iclass 3/1
ukbd0 at uhidev0
wskbd0 at ukbd0 mux 1
wskbd0: connecting to wsdisplay0
Kernelized RAIDframe activated
pad0: outputs: 44100Hz, 16-bit, stereo
audio0 at pad0: half duplex, playback, capture
WARNING: findroot: double match for boot device (wd0, wd1)
raid0: RAID Level 1
raid0: Components: /dev/wd0a /dev/wd1a
raid0: Total Sectors: 312581632 (152627 MB)
raid1: RAID Level 1
raid1: Components: /dev/wd2e /dev/wd3e
raid1: Total Sectors: 976772992 (476939 MB)
boot device: raid0
root on raid0a dumps on raid0b
root file system type: ffs


>How-To-Repeat:
Boot system, setup wm0 (and/or wm1) interface and do some network trafic.
After a while the problem occurs.

No way found to directly trigger the problem till now.


>Fix:
not known - sorry

>Audit-Trail:
From: Wolfgang Stukenbrock <wgstuken@grimme-reitenspezial.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL server board
Date: Sun, 22 Jan 2017 10:56:12 +0100

 Hi - again

 some additional information:

 If I limit the rate in ftp to 50000 the transfer succeeds (but runs  
 over 1 hour), but at 200000 it already happens again.

 It looks like it has something to do with lots of packets arriving ...

 regards

 W. Stukenbrock

 On 22.01.2017, at 10:05, gnats-admin@netbsd.org wrote:

 > Thank you very much for your problem report.
 > It has the internal identification `kern/51904'.
 > The individual assigned to look at your
 > report is: kern-bug-people.
 >
 >> Category:       kern
 >> Responsible:    kern-bug-people
 >> Synopsis:       wm driver instable on SuperMicro X8SIL server board
 >> Arrival-Date:   Sun Jan 22 09:05:00 +0000 2017
 >

From: Masanobu SAITOH <msaitoh@execsw.org>
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
 gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
 wgstuken@grimme-reitenspezial.de
Cc: msaitoh@execsw.org
Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL server board
Date: Mon, 23 Jan 2017 14:46:51 +0900

 On 2017/01/22 20:15, Wolfgang Stukenbrock wrote:
 > The following reply was made to PR kern/51904; it has been noted by GNATS.
 >
 > From: Wolfgang Stukenbrock <wgstuken@grimme-reitenspezial.de>
 > To: gnats-bugs@NetBSD.org
 > Cc:
 > Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL server board
 > Date: Sun, 22 Jan 2017 10:56:12 +0100
 >
 >  Hi - again
 >
 >  some additional information:
 >
 >  If I limit the rate in ftp to 50000 the transfer succeeds (but runs
 >  over 1 hour), but at 200000 it already happens again.
 >
 >  It looks like it has something to do with lots of packets arriving ...
 >
 >  regards
 >
 >  W. Stukenbrock

   Long time no see :)

   You may know, a lot of fixes have merged into netbsd-7 branch but not
 to netbsd-7-0. if_wm.c rev. 1.289.2.11 include a lot of PHY related fixes,
 so I think it would worth to try netbsd-7 (or 7.1 RC1). Is it possible for
 you?


 >  On 22.01.2017, at 10:05, gnats-admin@netbsd.org wrote:
 >
 >  > Thank you very much for your problem report.
 >  > It has the internal identification `kern/51904'.
 >  > The individual assigned to look at your
 >  > report is: kern-bug-people.
 >  >
 >  >> Category:       kern
 >  >> Responsible:    kern-bug-people
 >  >> Synopsis:       wm driver instable on SuperMicro X8SIL server board
 >  >> Arrival-Date:   Sun Jan 22 09:05:00 +0000 2017
 >  >
 >
 >


 -- 
 -----------------------------------------------
                  SAITOH Masanobu (msaitoh@execsw.org
                                   msaitoh@netbsd.org)

From: Wolfgang Stukenbrock <wgstuken@grimme-reitenspezial.de>
To: Masanobu SAITOH <msaitoh@execsw.org>
Cc: gnats-bugs@NetBSD.org,
 kern-bug-people@netbsd.org,
 gnats-admin@netbsd.org,
 netbsd-bugs@netbsd.org
Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL server board
Date: Tue, 21 Feb 2017 16:37:51 +0100

 Hi - sorry for the delay.

 I've downloaded 7.1RC sources now and compiled a new kernel.

 It runs better, but still not stable.

 Getting a really large file by ftp runs for a long time without problem.
 Then I've terminated it (by ctrl-C) because I want to monitor the  
 trafic  with bmon and I've missed to remember the IP-address the  
 system got while I'm testing on console.
 Accedently I've missed to install bmon and while running 'make  
 install' make frozes at the following point:

 dyn012# setenv ftp_proxy ftp://proxy:81
 dyn012# setenv http_proxy http://proxy:81
 dyn012# ^http^https^
 setenv https_proxy http://proxy:81
 dyn012# make install
 => Bootstrap dependency digest>=20010302: found digest-20160304
 ===> Skipping vulnerability checks.
 WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
 WARNING: To fix run: `/usr/pkg/sbin/pkg_admin -K /var/db/pkg fetch- 
 pkg-vulnerabilities'.
 => Fetching bmon-3.8.tar.gz
 => Total size: 195437 bytes
 Requesting https://github.com/tgraf/bmon/releases/download/v3.8/ 
 bmon-3.8.tar.gz
    (via proxy:81)
 Redirected to https://github-cloud.s3.amazonaws.com/releases/11199684/ 
 ebdb5016-32bd-11e5-8dd9-acc875d860d5.gz?X-Amz-Algorithm=AWS4-HMAC- 
 SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20170221%2Fus-east-1% 
 2Fs3%2Faws4_request&X-Amz-Date=20170221T150453Z&X-Amz-Expires=300&X- 
 Amz- 
 Signature=ce6490880002822ae43ff8e9cf17df9a3b60b0c4761ba1cfe8eb9dd8a33508 
 3b&X-Amz-SignedHeaders=host&actor_id=0&response-content- 
 disposition=attachment%3B%20filename%3Dbmon-3.8.tar.gz&response- 
 content-type=application%2Foctet-stream
 Requesting https://github-cloud.s3.amazonaws.com/releases/11199684/ 
 ebdb5016-32bd-11e5-8dd9-acc875d860d5.gz?X-Amz-Algorithm=AWS4-HMAC- 
 SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20170221%2Fus-east-1% 
 2Fs3%2Faws4_request&X-Amz-Date=20170221T150453Z&X-Amz-Expires=300&X- 
 Amz- 
 Signature=ce6490880002822ae43ff8e9cf17df9a3b60b0c4761ba1cfe8eb9dd8a33508 
 3b&X-Amz-SignedHeaders=host&actor_id=0&response-content- 
 disposition=attachment%3B%20filename%3Dbmon-3.8.tar.gz&response- 
 content-type=application%2Foctet-stream
    (via proxy:81)
 ^C

 It got not very far ....

 ifconfig -a reports that wm0 has no carrier anymore, but the lights  
 are still on ..

 wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
          capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>

 capabilities=7ff80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx>
          capabilities=7ff80<TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6>
          enabled=0
          ec_capabilities=7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU>
          ec_enabled=0
          address: 00:25:90:61:0d:ba
          media: Ethernet autoselect
          status: no carrier
          inet 10.0.57.216 netmask 0xffffff00 broadcast 10.0.57.255
          inet6 fe80::225:90ff:fe61:dba%wm0 prefixlen 64 detached  
 scopeid 0x1


 Playing around with the cable does not help. The light went off when  
 disconnected and came back when connected.
 But still no carrier according to ifconfig

 After this, dmesg reports the following - see error messages at end:

 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,  
 2005,
      2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
      The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
      The Regents of the University of California.  All rights reserved.

 NetBSD 7.1_RC1 (GENERIC) #0: Mon Feb 20 12:18:47 CET 2017
          wgstuken@websvr:/home.stand/wgstuken/netbsd/NetBSD-7.x/N+C- 
 build/.OBJDIR_amd64/home.stand/wgstuken/netbsd/NetBSD-7.x/src/sys/ 
 arch/amd64/compile/GENERIC
 total memory = 16375 MB
 avail memory = 15882 MB
 kern.module.path=/stand/amd64/7.1/modules
 timecounter: Timecounters tick every 10.000 msec
 timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
 Supermicro X8SIL (0123456789)
 mainbus0 (root)
 ACPI: RSDP 0xfa280 000024 (v02 ACPIAM)
 ACPI: XSDT 0xbf7a0100 000084 (v01 SMCI            20100527 MSFT  
 00000097)
 ACPI: FACP 0xbf7a0290 0000F4 (v04 052710 FACP1450 20100527 MSFT  
 00000097)
 ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block:  
 128/64 (20131218/tbfadt-634)
 ACPI: DSDT 0xbf7a05f0 006C7B (v02  10605 10605000 00000000 INTL  
 20051117)
 ACPI: FACS 0xbf7ae000 000040
 ACPI: APIC 0xbf7a0390 000092 (v02 052710 APIC1450 20100527 MSFT  
 00000097)
 ACPI: MCFG 0xbf7a0430 00003C (v01 052710 OEMMCFG  20100527 MSFT  
 00000097)
 ACPI: OEMB 0xbf7ae040 000073 (v01 052710 OEMB1450 20100527 MSFT  
 00000097)
 ACPI: HPET 0xbf7aa5f0 000038 (v01 052710 OEMHPET  20100527 MSFT  
 00000097)
 ACPI: GSCI 0xbf7ae0c0 002024 (v01 052710 GMCHSCI  20100527 MSFT  
 00000097)
 ACPI: DMAR 0xbf7b00f0 000090 (v01    AMI  OEMDMAR 00000001 MSFT  
 00000097)
 ACPI: SSDT 0xbf7b1dc0 000363 (v01 DpgPmm    CpuPm 00000012 INTL  
 20051117)
 ACPI: EINJ 0xbf7aa630 000130 (v01  AMIER AMI_EINJ 20100527 MSFT  
 00000097)
 ACPI: BERT 0xbf7aa7c0 000030 (v01  AMIER AMI_BERT 20100527 MSFT  
 00000097)
 ACPI: ERST 0xbf7aa7f0 0001B0 (v01  AMIER AMI_ERST 20100527 MSFT  
 00000097)
 ACPI: HEST 0xbf7aa9a0 0000A8 (v01  AMIER ABC_HEST 20100527 MSFT  
 00000097)
 ACPI: All ACPI Tables successfully acquired
 ioapic0 at mainbus0 apid 8: pa 0xfec00000, version 0x20, 24 pins
 cpu0 at mainbus0 apid 0: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu1 at mainbus0 apid 2: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu2 at mainbus0 apid 4: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu3 at mainbus0 apid 6: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu4 at mainbus0 apid 1: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu5 at mainbus0 apid 3: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu6 at mainbus0 apid 5: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 cpu7 at mainbus0 apid 7: Intel(R) Xeon(R) CPU           L3426  @  
 1.87GHz, id 0x106e5
 acpi0 at mainbus0: Intel ACPICA 20131218
 acpi0: X/RSDT: OemId <SMCI  ,        ,20100527>, AslId <MSFT,00000097>
 ACPI BIOS Warning (bug): Incorrect checksum in table [OEMB] - 0xA4,  
 should be 0xA1 (20131218/tbprint-237)
 ACPI: SSDT 0xbf7b0180 0015DC (v01 DpgPmm  P001Ist 00000011 INTL  
 20051117)
 ACPI: SSDT 0x0 0015DC (v01 DpgPmm  P001Ist 00000011 INTL 20051117)
 ACPI: SSDT 0xbf7b1760 000659 (v01  PmRef  P001Cst 00003001 INTL  
 20051117)
 ACPI: SSDT 0x0 000659 (v01  PmRef  P001Cst 00003001 INTL 20051117)
 acpi0: SCI interrupting at int 9
 timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
 hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
 timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
 IOH (PNP0C01) at acpi0 not configured
 attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
 pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
 midi0 at pcppi1: PC speaker
 sysbeep0 at pcppi1
 UAR1 (PNP0501) at acpi0 not configured
 UAR2 (PNP0501) at acpi0 not configured
 SIO2 (PNP0C02) at acpi0 not configured
 SIOR (PNP0C02) at acpi0 not configured
 RMSC (PNP0C02) at acpi0 not configured
 OMSC (PNP0C02) at acpi0 not configured
 PCIE (PNP0C02) at acpi0 not configured
 RMEM (PNP0C01) at acpi0 not configured
 acpibut0 at acpi0 (PWRB, PNP0C0C-170): ACPI Power Button
 ACPI: Enabled 2 GPEs in block 00 to 3F
 ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_]  
 (20131218/hwxface-646)
 ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_]  
 (20131218/hwxface-646)
 attimer1: attached to pcppi1
 ipmi: bus_space_map(..., ca0, 2, 0, 0xffffffff81270be8) failed
 pci0 at mainbus0 bus 0: configuration mode 1
 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
 pchb0 at pci0 dev 0 function 0: vendor 0x8086 product 0xd130 (rev. 0x11)
 ppb0 at pci0 dev 3 function 0: vendor 0x8086 product 0xd138 (rev. 0x11)
 ppb0: PCI Express capability version 2 <Root Port of PCI-E Root  
 Complex> x8 @ 5.0GT/s
 pci1 at ppb0 bus 1
 pci1: i/o space, memory space enabled, rd/line, wr/inv ok
 ppb1 at pci0 dev 5 function 0: vendor 0x8086 product 0xd13a (rev. 0x11)
 ppb1: PCI Express capability version 2 <Root Port of PCI-E Root  
 Complex> x8 @ 5.0GT/s
 pci2 at ppb1 bus 2
 pci2: i/o space, memory space enabled, rd/line, wr/inv ok
 vendor 0x8086 product 0xd155 (miscellaneous system, revision 0x11) at  
 pci0 dev 8 function 0 not configured
 vendor 0x8086 product 0xd156 (miscellaneous system, revision 0x11) at  
 pci0 dev 8 function 1 not configured
 vendor 0x8086 product 0xd157 (miscellaneous system, revision 0x11) at  
 pci0 dev 8 function 2 not configured
 vendor 0x8086 product 0xd158 (miscellaneous system, revision 0x11) at  
 pci0 dev 8 function 3 not configured
 vendor 0x8086 product 0xd150 (miscellaneous system, revision 0x11) at  
 pci0 dev 16 function 0 not configured
 vendor 0x8086 product 0xd151 (miscellaneous system, revision 0x11) at  
 pci0 dev 16 function 1 not configured
 ehci0 at pci0 dev 26 function 0: vendor 0x8086 product 0x3b3c (rev.  
 0x05)
 ehci0: interrupting at ioapic0 pin 21
 ehci0: EHCI version 1.0
 usb0 at ehci0: USB revision 2.0
 ppb2 at pci0 dev 28 function 0: vendor 0x8086 product 0x3b42 (rev. 0x05)
 ppb2: PCI Express capability version 2 <Root Port of PCI-E Root  
 Complex> x4 @ 2.5GT/s
 pci3 at ppb2 bus 3
 pci3: i/o space, memory space enabled, rd/line, wr/inv ok
 ppb3 at pci0 dev 28 function 4: vendor 0x8086 product 0x3b4a (rev. 0x05)
 ppb3: PCI Express capability version 2 <Root Port of PCI-E Root  
 Complex> x1 @ 2.5GT/s
 pci4 at ppb3 bus 4
 pci4: i/o space, memory space enabled, rd/line, wr/inv ok
 wm0 at pci4 dev 0 function 0: Intel i82574L (rev. 0x00)
 wm0: interrupting at ioapic0 pin 16
 wm0: PCI-Express bus
 wm0: 2048 words (8 address bits) SPI EEPROM, version 1.9.0, Image  
 Unique ID 0000ffff
 wm0: Ethernet address 00:25:90:61:0d:ba
 makphy0 at wm0 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 ppb4 at pci0 dev 28 function 5: vendor 0x8086 product 0x3b4c (rev. 0x05)
 ppb4: PCI Express capability version 2 <Root Port of PCI-E Root  
 Complex> x1 @ 2.5GT/s
 pci5 at ppb4 bus 5
 pci5: i/o space, memory space enabled, rd/line, wr/inv ok
 wm1 at pci5 dev 0 function 0: Intel i82574L (rev. 0x00)
 wm1: interrupting at ioapic0 pin 17
 wm1: PCI-Express bus
 wm1: 512 words (8 address bits) SPI EEPROM, version 1.9.0, Image  
 Unique ID 0000ffff
 wm1: Ethernet address 00:25:90:61:0d:bb
 makphy1 at wm1 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
 makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 ehci1 at pci0 dev 29 function 0: vendor 0x8086 product 0x3b34 (rev.  
 0x05)
 ehci1: interrupting at ioapic0 pin 23
 ehci1: EHCI version 1.0
 usb1 at ehci1: USB revision 2.0
 ppb5 at pci0 dev 30 function 0: vendor 0x8086 product 0x244e (rev. 0xa5)
 pci6 at ppb5 bus 6
 pci6: i/o space, memory space enabled
 sip0 at pci6 dev 0 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
 sip0: interrupting at ioapic0 pin 20
 sip0: Ethernet address 00:02:e3:1d:ce:25
 nsphyter0 at sip0 phy 0: DP83815 10/100 media interface, rev. 1
 nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 vga0 at pci6 dev 3 function 0: vendor 0x102b product 0x0532 (rev. 0x0a)
 wsdisplay0 at vga0 kbdmux 1
 wsmux1: connecting to wsdisplay0
 drm at vga0 not configured
 ichlpcib0 at pci0 dev 31 function 0: vendor 0x8086 product 0x3b14  
 (rev. 0x05)
 timecounter: Timecounter "ichlpcib0" frequency 3579545 Hz quality 1000
 ichlpcib0: 24-bit timer
 ichlpcib0: TCO (watchdog) timer configured.
 ahcisata0 at pci0 dev 31 function 2: vendor 0x8086 product 0x3b22  
 (rev. 0x05)
 ahcisata0: interrupting at ioapic0 pin 19
 ahcisata0: 64-bit DMA
 ahcisata0: AHCI revision 1.30, 6 ports, 32 slots, CAP  
 0xef20ff65<SXS,EMS,PSC,SSC,PMD,ISS=0x2=Gen2,SCLO,SAL,SALP,SSS,SSNTF,SNCQ 
 ,S64A>
 atabus0 at ahcisata0 channel 0
 atabus1 at ahcisata0 channel 1
 atabus2 at ahcisata0 channel 2
 atabus3 at ahcisata0 channel 3
 atabus4 at ahcisata0 channel 4
 atabus5 at ahcisata0 channel 5
 ichsmb0 at pci0 dev 31 function 3: vendor 0x8086 product 0x3b30 (rev.  
 0x05)
 ichsmb0: interrupting at ioapic0 pin 18
 iic0 at ichsmb0: I2C bus
 isa0 at ichlpcib0
 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 com0: console
 com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
 pckbc0 at isa0 port 0x60-0x64
 acpicpu0 at cpu0: ACPI CPU
 acpicpu0: C1: FFH, lat   1 us, pow  1000 mW
 acpicpu0: C2: FFH, lat  17 us, pow   500 mW
 acpicpu0: C3: FFH, lat  17 us, pow   350 mW
 acpicpu0: P0: FFH, lat  10 us, pow 55000 mW, 1868 MHz, turbo boost
 acpicpu0: P1: FFH, lat  10 us, pow 45000 mW, 1867 MHz
 acpicpu0: P2: FFH, lat  10 us, pow 35000 mW, 1733 MHz
 acpicpu0: P3: FFH, lat  10 us, pow 27000 mW, 1600 MHz
 acpicpu0: P4: FFH, lat  10 us, pow 21000 mW, 1467 MHz
 acpicpu0: P5: FFH, lat  10 us, pow 16000 mW, 1333 MHz
 acpicpu0: P6: FFH, lat  10 us, pow 11000 mW, 1200 MHz
 coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=70
 acpicpu1 at cpu1: ACPI CPU
 coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=70
 acpicpu2 at cpu2: ACPI CPU
 coretemp2 at cpu2: thermal sensor, 1 C resolution, Tjmax=70
 acpicpu3 at cpu3: ACPI CPU
 coretemp3 at cpu3: thermal sensor, 1 C resolution, Tjmax=70
 acpicpu4 at cpu4: ACPI CPU
 acpicpu5 at cpu5: ACPI CPU
 acpicpu6 at cpu6: ACPI CPU
 acpicpu7 at cpu7: ACPI CPU
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 timecounter: Timecounter "TSC" frequency 1866801640 Hz quality 3000
 IPsec: Initialized Security Association Processing.
 uhub0 at usb0: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00,  
 addr 1
 uhub0: 2 ports with 2 removable, self powered
 uhub1 at usb1: vendor 0x8086 EHCI root hub, class 9/0, rev 2.00/1.00,  
 addr 1
 uhub1: 2 ports with 2 removable, self powered
 ahcisata0 port 1: device present, speed: 3.0Gb/s
 ahcisata0 port 0: device present, speed: 3.0Gb/s
 ahcisata0 port 2: device present, speed: 3.0Gb/s
 ahcisata0 port 3: device present, speed: 3.0Gb/s
 ahcisata0 port 5: device present, speed: 1.5Gb/s
 wd0 at atabus0 drive 0
 wd0: <Hitachi HTS723216A7A364>
 wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 wd0: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808  
 sectors
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6  
 (Ultra/133) (using DMA)
 wd1 at atabus1 drive 0
 wd1: <Hitachi HTS723216A7A364>
 wd1: drive supports 16-sector PIO transfers, LBA48 addressing
 wd1: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808  
 sectors
 wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6  
 (Ultra/133) (using DMA)
 wd2 at atabus2 drive 0
 wd2: <Hitachi HTS727550A9E364>
 wd2: drive supports 16-sector PIO transfers, LBA48 addressing
 wd2: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168  
 sectors
 wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd2(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6  
 (Ultra/133) (using DMA)
 wd3 at atabus3 drive 0uhub2 at uhub0 port 1
 : vendor 0x8087 product 0x0020, class 9/0, rev 2.00/0.00, addr 2
 wd3: <Hitachi HTS727550A9E364>
 wd3: drive supports 16-sector PIO transfers, LBA48 addressing
 wd3: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168  
 sectors
 uhub2: single transaction translator
 uhub2: 6 ports with 6 removable, self powered
 uhub3 at uhub1 port 1: vendor 0x8087 product 0x0020, class 9/0, rev  
 2.00/0.00, addr 2
 uhub3: single transaction translator
 uhub3: 8 ports with 8 removable, self powered
 wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd3(ahcisata0:3:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6  
 (Ultra/133) (using DMA)
 atapibus0 at atabus5: 1 targets
 cd0 at atapibus0 drive 0: <HL-DT-ST DVDRAM GH22NS50, K3ZB34E4028,  
 TN03> cdrom removable
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 cd0(ahcisata0:5:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5  
 (Ultra/100) (using DMA)
 umass0 at uhub3 port 2 configuration 1 interface 0
 umass0: PHILIPS ED16DVDS, rev 2.00/0.01, addr 3
 umass0: using SCSI over Bulk-Only
 scsibus0 at umass0: 2 targets, 1 lun per target
 cd1 at scsibus0 target 0 lun 0: <PHILIPS, ED16DVDS, J5S7> cdrom  
 removable
 uhidev0 at uhub3 port 4 configuration 1 interface 0
 uhidev0: vendor 0x046a product 0x0011, rev 2.00/1.00, addr 4, iclass 3/1
 ukbd0 at uhidev0
 wskbd0 at ukbd0 mux 1
 wskbd0: connecting to wsdisplay0
 Kernelized RAIDframe activated
 pad0: outputs: 44100Hz, 16-bit, stereo
 audio0 at pad0: half duplex, playback, capture
 WARNING: findroot: double match for boot device (wd0, wd1)
 raid0: RAID Level 1
 raid0: Components: /dev/wd0a /dev/wd1a
 raid0: Total Sectors: 312581632 (152627 MB)
 raid1: RAID Level 1
 raid1: Components: /dev/wd2e /dev/wd3e
 raid1: Total Sectors: 976772992 (476939 MB)
 boot device: raid0
 root on raid0a dumps on raid0b
 root file system type: ffs
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 16
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4084 txsfree 60 txnext 1675)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4093 txsfree 63 txnext 3)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 16
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4092 txsfree 62 txnext 4)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4094 txsfree 62 txnext 2)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4094 txsfree 62 txnext 2)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4094 txsfree 62 txnext 2)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 16
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 16
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4092 txsfree 62 txnext 4)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4094 txsfree 62 txnext 2)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4094 txsfree 62 txnext 2)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: device timeout (txfree 4094 txsfree 62 txnext 2)
 wm0: MDIC write error: phy 1 reg 4
 wm0: MDIC write error: phy 1 reg 9
 wm0: MDIC write error: phy 1 reg 0
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 22
 wm0: MDIC write error: phy 1 reg 16
 ...

 Sorry, but 7.1RC does not solve this problem.

 remark: wm0 is connected to a 100 MBit switch - just in case that  
 this may be relevant.
 Accedently I've no 1G Bit Port available to test the behavior there.

 regards

 W. Stukenbrock

 On 23.01.2017, at 06:46, Masanobu SAITOH wrote:

 > On 2017/01/22 20:15, Wolfgang Stukenbrock wrote:
 >> The following reply was made to PR kern/51904; it has been noted  
 >> by GNATS.
 >>
 >> From: Wolfgang Stukenbrock <wgstuken@grimme-reitenspezial.de>
 >> To: gnats-bugs@NetBSD.org
 >> Cc:
 >> Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL  
 >> server board
 >> Date: Sun, 22 Jan 2017 10:56:12 +0100
 >>
 >>  Hi - again
 >>
 >>  some additional information:
 >>
 >>  If I limit the rate in ftp to 50000 the transfer succeeds (but runs
 >>  over 1 hour), but at 200000 it already happens again.
 >>
 >>  It looks like it has something to do with lots of packets  
 >> arriving ...
 >>
 >>  regards
 >>
 >>  W. Stukenbrock
 >
 >  Long time no see :)
 >
 >  You may know, a lot of fixes have merged into netbsd-7 branch but not
 > to netbsd-7-0. if_wm.c rev. 1.289.2.11 include a lot of PHY related  
 > fixes,
 > so I think it would worth to try netbsd-7 (or 7.1 RC1). Is it  
 > possible for
 > you?
 >
 >
 >>  On 22.01.2017, at 10:05, gnats-admin@netbsd.org wrote:
 >>
 >>  > Thank you very much for your problem report.
 >>  > It has the internal identification `kern/51904'.
 >>  > The individual assigned to look at your
 >>  > report is: kern-bug-people.
 >>  >
 >>  >> Category:       kern
 >>  >> Responsible:    kern-bug-people
 >>  >> Synopsis:       wm driver instable on SuperMicro X8SIL server  
 >> board
 >>  >> Arrival-Date:   Sun Jan 22 09:05:00 +0000 2017
 >>  >
 >>
 >>
 >
 >
 > -- 
 > -----------------------------------------------
 >                 SAITOH Masanobu (msaitoh@execsw.org
 >                                  msaitoh@netbsd.org)

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL server board
Date: Sun, 11 Mar 2018 23:37:32 +0000

 This is from a while back but got sent to the wrong address.

    ------

 From: Jarom?r Dole?ek <jaromir.dolecek@gmail.com>
 Cc: gnats-admin@netbsd.org
 Subject: Re: kern/51904: wm driver instable on SuperMicro X8SIL server board
 Date: Sun, 22 Jan 2017 13:25:16 +0100

 I see this happens for you with 7.0.1 kernel. Could you please try
 with -current kernel? The driver got lot of attention recently, it
 might have been fixed as part of the changes.

 Jaromir

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.