msk(4) stops working.
ianf at clue.co.za
Wed Dec 24 05:42:18 UTC 2008
Pyun YongHyeon wrote:
> On Tue, Dec 23, 2008 at 03:33:40PM +0200, Ian Freislich wrote:
> > Hi
> > My msk0 (Marvell Yukon 88E8053 Gigabit Ethernet) will stop working
> > and never recover after a burst in activity. It produces the
> > following messages:
> > Dec 23 15:24:16 apple kernel: msk0: watchdog timeout
> > Dec 23 15:24:16 apple kernel: msk0: link state changed to DOWN
> > Dec 23 15:24:19 apple kernel: msk0: link state changed to UP
> > Dec 23 15:24:29 apple kernel: msk0: watchdog timeout (missed Tx interrupts
) -- recovering
> > pciconf -lvc:
> > mskc0 at pci0:2:0:0: class=0x020000 card=0x532111ab chip=0x436211ab rev
> > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
> > device = '88E8053 Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Con
> > class = network
> > subclass = ethernet
> > cap 01 = powerspec 2 supports D0 D1 D2 D3 current D0
> > cap 03 = VPD
> > cap 05[5c] = MSI supports 2 messages, 64 bit enabled with 2 messages
> > cap 10[e0] = PCI-Express 1 legacy endpoint
> About 2-3 months ago I committed workaround for Yukon silicon bug.
> Do you use latest CURRENT?
Yes, this is on yesterday's sources. It was better for a month or
so, but over the last month it's been really bad. Now I can provoke
this condition in under 1 minute of uptime.
More information about the freebsd-current