Date: Wed, 30 Dec 2009 14:24:03 -0800 From: Pyun YongHyeon <pyunyh@gmail.com> To: "Lhunath (Maarten B.)" <lhunath@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: mskc0: Tx descriptor error Message-ID: <20091230222403.GO1166@michelle.cdnetworks.com> In-Reply-To: <5D9DCA13-95CC-4848-AAFF-04900CE841B2@gmail.com> References: <C7B75D6E-7FA4-4EB2-B242-BABF0E1877DF@gmail.com> <20091224194214.GE8146@michelle.cdnetworks.com> <5D9DCA13-95CC-4848-AAFF-04900CE841B2@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 24, 2009 at 10:25:46PM +0100, Lhunath (Maarten B.) wrote: > >> e1000phy0: <Marvell 88E1149 Gigabit PHY> PHY 0 on miibus0 > >> e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > > > I guess you hit known msk(4) issue for 88E8056/88E1149 PHY. Some > > users have no problems but others seem to suffer from the issue. > > There is also a PR about this but it seems it's hard to fix that > > mainly because I don't have access to the hardware. > > Perhaps if you can provide patches against the 8.0-REL msk(1) to make it extremely verbose, I could provide the output and we might learn more about the cause of this issue. The fact that it's so easily reproduced must play in favor. > A kind user gave me remote access to a 7.2-RELEASE system that has this controller. After applying latest msk(4)/mii(4) in HEAD I was not able to reproduce the issue on Yukon Ultra controller. So would you try latest msk(4)/mii(4) in HEAD? Just copying the related files in HEAD(msk(4) files in /usr/src/sys/dev/msk directory and mii(4) files in /usr/src/sys/dev/mii directory) and rebuild your kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091230222403.GO1166>