Date: Sat, 25 Jan 2014 21:50:50 +0200 From: Vitaly Magerya <vmagerya@gmail.com> To: curtis@ipv6.occnc.com Cc: Yonghyeon PYUN <pyunyh@gmail.com>, freebsd-stable@freebsd.org Subject: Re: Any news about "msk0 watchdog timeout" regression in 10-RELEASE? Message-ID: <52E4159A.4020007@gmail.com> In-Reply-To: <201401251935.s0PJZAwH048013@maildrop2.v6ds.occnc.com> References: <201401251935.s0PJZAwH048013@maildrop2.v6ds.occnc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/25/14 21:35, Curtis Villamizar wrote: > When I'm no longer quite so swamped I'll look at this again. It seems > we are the only two reporting this problem. To everyone reading this list: if you have an msk(4) NIC that doesn't work on 10-RELEASE, now is the time to speak up. > Please send lines of these form from dmesg: > > mskc0: <Marvell Yukon 88E8057 Gigabit Ethernet> port 0xe800-0xe8ff > mem 0xfebfc000-0xfebfffff irq 19 at deviceD 0.0 on pci2 > > msk0: <Marvell Technology Group Ltd. Yukon Ultra 2 Id 0xba Rev 0x00> > on mskc0 > > That may indicate we have very similar chips. If not, this msk > problem may be more widespread. Mine goes like this: mskc0: <Marvell Yukon 88E8040 Fast Ethernet> port 0x2000-0x20ff mem 0xf0200000-0xf0203fff irq 18 at device 0.0 on pci9 msk0: <Marvell Technology Group Ltd. Yukon FE+ Id 0xb8 Rev 0x00> on mskc0 Pretty different chips it seems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E4159A.4020007>