From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Drake Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems Date: Wed, 31 Aug 2005 10:56:08 +0100 Message-ID: <43157EB8.8040108@gentoo.org> References: <20050830133918.42444cae@dxpl.pdx.osdl.net> <20050830205027.59306.qmail@web53609.mail.yahoo.com> <20050830140516.316e9695@dxpl.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Steve Kieu , Jesse Brandeburg , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: To: Stephen Hemminger In-Reply-To: <20050830140516.316e9695@dxpl.pdx.osdl.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Stephen Hemminger wrote: > You have a version of the Marvell Yukon that was affected > by a fix in 2.6.13. > skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9 > > Both the skge and sk98lin driver were fixed to check for this. > Without the fix, the chip will be in the wrong power mode. > > The version of sk98lin driver from SysKonnect already had the > fix, so if your distro used that one, it would have the reset > the power mode as needed. So, am I right in saying we can't do anything in skge to work around this to allow those older buggy drivers to work on the next reboot? More reports are cropping up, e.g.: http://forums.gentoo.org/viewtopic-t-375828.html Given that it seems to be affecting the Windows drivers too, it would be great if something could be done. Thanks, Daniel