more wm(4) fun

[Jeff Rizzo <riz%tastylime.net@localhost>]

Running a relatively recent (~1wk) -current, on the wm(4) cards I bought
because the motherboard ethernet isn't yet supported, I see this
periodically:

wm0: device timeout (txfree 3927 txsfree 0 txnext 57)
wm0: device timeout (txfree 3902 txsfree 0 txnext 2003)
wm0: device timeout (txfree 3929 txsfree 0 txnext 2776)
wm0: device timeout (txfree 3957 txsfree 0 txnext 278)
wm1: device timeout (txfree 3926 txsfree 0 txnext 423)
wm0: device timeout (txfree 3885 txsfree 0 txnext 211)


... that's over the span of 20 hours - so not a HUGE deal, but kind of
annoying, as it's long enough to make the webserver appear down to the
load balancer.

Here's the chipset-specific info from dmesg:

wm0 at pci4 dev 0 function 0: Intel PRO/1000 PT (82571EB), rev. 6
wm0: interrupting at ioapic0 pin 16
wm0: PCI-Express bus
wm0: 65536 word (16 address bits) SPI EEPROM
wm0: Ethernet address 00:15:17:7d:e9:68
igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX
, auto
wm1 at pci4 dev 0 function 1: Intel PRO/1000 PT (82571EB), rev. 6
wm1: interrupting at ioapic0 pin 17
wm1: PCI-Express bus
wm1: 65536 word (16 address bits) SPI EEPROM
wm1: Ethernet address 00:15:17:7d:e9:69
igphy1 at wm1 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
igphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX
, auto


... is anyone familiar with this issue?  Should I use 'ukphy' instead of
'igphy'?

+j