Date: Wed, 24 Dec 2008 07:42:08 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: pyunyh@gmail.com Cc: current@freebsd.org Subject: Re: msk(4) stops working. Message-ID: <E1LFMVU-0001fB-Mz@clue.co.za> In-Reply-To: <20081224021016.GF95088@cdnetworks.co.kr> References: <20081224021016.GF95088@cdnetworks.co.kr> <E1LF7Oc-000Djt-C1@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
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@pci0:2:0:0: class=0x020000 card=0x532111ab chip=0x436211ab rev =0x22 hdr=0x00 > > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > > device = '88E8053 Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Con troller' > > class = network > > subclass = ethernet > > cap 01[48] = powerspec 2 supports D0 D1 D2 D3 current D0 > > cap 03[50] = 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. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1LFMVU-0001fB-Mz>