Re: Bug#396185: sky2 freezes in 2.6.17-2-686. Maintainer confirms that it should be fixed in 2.6.19-git tree.

[Evgeniy Polyakov <johnpol@2ka.mipt.ru>]

On Sat, Nov 18, 2006 at 02:25:27PM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> On Sat, Nov 18, 2006 at 12:21:34PM +0100, maximilian attems (maks@sternwelten.at) wrote:
> > > > > > > > > Bug was filled against 2.6.17-9, but was fixed in recent git (2.6.19-rc3), probably also
> > > > > > > > > fixed in 2.6.18.1
> > > > > > > > > 
> > > > > > > > > Here is link to discussion:
> > > > > > > > > http://marc.theaimsgroup.com/?l=linux-netdev&m=116227512815783&w=2
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > can you try the linux-image 2.6.18, they are in unstable
> > > > > > > > and the etch release images.
> > > > 
> > > > 2.6.18-1-686 kernel still allows to freeze sky2.
> > > 
> > > Fix didn't go in until 2.6.18.2
> > 
> > fix is in the 2.6.18-2-686 linux image, you'd better update
> > your test box.
> 
> Just for clarification: there are at least two bugs described - one in
> the above link, and this new one. The former could only be fixed by
> reboot, the latter - by rmmod/modprobe sequence. The former had special
> info in dmesg, the latter does not.
> 
> Hopefully they both are fixed in 2.6.18-2.
> I will set it up as soon as time permits (it is my main desktop, which
> is rarely turned off) and report if problem still persists.

Bug still exists in 2.6.18-2 (package version 5).
Can be 'fixed' by rmmod/modprobe sequence though.
Is not easily reproducible.

NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 303 .. 280 report=303 done=303
sky2 hardware hung? flushing
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 280 .. 257 report=303 done=303
sky2 status report lost?
NETDEV WATCHDOG: eth0: transmit timed out
sky2 eth0: tx timeout
sky2 eth0: transmit ring 303 .. 280 report=303 done=303
sky2 hardware hung? flushing


-- 
	Evgeniy Polyakov