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

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

[Stephen Hemminger]

On Thu, 16 Nov 2006 20:35:32 +0300
Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:

> On Tue, Oct 31, 2006 at 12:44:25PM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) 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

> There is nothing in dmesg and card just stops transmitting and
> receiving.
> rmmod/modproble helps in this situation though, so it is probably 
> not 100% the same bug as described in above link.
> 
> It looks like it happens when device is in promiscuous mode some traffic
> is started, at least I did not see such freezes when device operates in 
> usual mode, but it can be unrelated though.
> 
> I would say it is 100% reproducible, but only in current state - I do
> not know what will happen when I reboot. With tcpdump -n host 224.0.0.123
> and scp of the big file from sky2 to via_rhine 100mbit I'm able to
> reproduce that bug 100%, without tcpdump it seems to work correct.
> 
> Here is rmmod/modprobe dmesg:
> 
> ACPI: PCI interrupt for device 0000:05:00.0 disabled
> PCI: Enabling device 0000:05:00.0 (0000 -> 0003)
> ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNKD] -> GSI 17 (level,low) -> IRQ 106
> PCI: Setting latency timer of device 0000:05:00.0 to 64
> sky2 v1.5 addr 0xfbefc000 irq 106 Yukon-EC (0xb6) rev 2
> sky2 eth0: addr 00:17:31:9a:e5:be
> sky2 eth0: enabling interface
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> eth0: no IPv6 routers present
> 
> Here is line from /proc/interrupts when device was frozen again:
> 114:    3257078          0         PCI-MSI  sky2
> 
> Above number does not change when card is frozen and starts increasing
> after rmmod/modprobe.
> 
> Attached statistic and register dumps for working and frozen states.
> 

Please retest with 2.76.18.2 or 2.6.19-rc6, there were some fixes
already there.

-- 
Stephen Hemminger <shemminger@osdl.org>

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]

On Thu, Nov 16, 2006 at 09:38:21AM -0800, Stephen Hemminger (shemminger@osdl.org) wrote:
> Please retest with 2.76.18.2 or 2.6.19-rc6, there were some fixes
> already there.

I will install that kernel, but I can not test it right now.
If there will be any problem I will report it.
Thank you.

> -- 
> Stephen Hemminger <shemminger@osdl.org>

-- 
	Evgeniy Polyakov

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

[maximilian attems]

On Thu, 16 Nov 2006, Stephen Hemminger wrote:

> On Thu, 16 Nov 2006 20:35:32 +0300
> Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> 
> > On Tue, Oct 31, 2006 at 12:44:25PM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) 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.

thanks
 
-- 
maks

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]

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.

> thanks
>  
> -- 
> maks

-- 
	Evgeniy Polyakov

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]

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

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]

On Wed, Nov 29, 2006 at 08:29:48AM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> > > > > > > > > > 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.

Bug with freeze also exists in 2.6.18-3 (package version 2.6.18-7) - no
messages in dmesg, no interrupts.
It is dual lan board with only one port being used.
rmmod/modprobe sequence brings NIC back to working mode.

-- 
	Evgeniy Polyakov

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

[Stephen Hemminger]

On Sun, 17 Dec 2006 17:15:47 +0300
Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:

> On Wed, Nov 29, 2006 at 08:29:48AM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> > > > > > > > > > > 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.
> 
> Bug with freeze also exists in 2.6.18-3 (package version 2.6.18-7) - no
> messages in dmesg, no interrupts.
> It is dual lan board with only one port being used.
> rmmod/modprobe sequence brings NIC back to working mode.
> 

What are the statistics (ethtool -S eth0) after the hang.
One user reported a single pause frame being sent. I have can't reproduce
a hang with similar hardware, so am beginning to wonder if the problem is
pause negotiation, and interoperability problems??  Maybe the receiver gets
overloaded and sends one pause frame, but the switch can't really do flow
control and gets stuck.  I do stress tests with either a direct connect cable,
or with a switch that does flow control and lots of packets and see the driver/hardware
successfully doing flow control.




-- 
Stephen Hemminger <shemminger@osdl.org>

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]

On Mon, Dec 18, 2006 at 09:17:28AM -0800, Stephen Hemminger (shemminger@osdl.org) wrote:
> > Bug with freeze also exists in 2.6.18-3 (package version 2.6.18-7) - no
> > messages in dmesg, no interrupts.
> > It is dual lan board with only one port being used.
> > rmmod/modprobe sequence brings NIC back to working mode.
> > 
> 
> What are the statistics (ethtool -S eth0) after the hang.
> One user reported a single pause frame being sent. I have can't reproduce
> a hang with similar hardware, so am beginning to wonder if the problem is
> pause negotiation, and interoperability problems??  Maybe the receiver gets
> overloaded and sends one pause frame, but the switch can't really do flow
> control and gets stuck.  I do stress tests with either a direct connect cable,
> or with a switch that does flow control and lots of packets and see the driver/hardware
> successfully doing flow control.
 
Load was quite small - no huge transfers, just usual couple of ssh
sessions to read mails, web. Switch is dlink dgs-1216t gigabit one which
supports flow control (according to dlink spec).

I will dump statistic and registers next time it happens - I do not know
how to reproduce it on demand.
 
> -- 
> Stephen Hemminger <shemminger@osdl.org>

-- 
	Evgeniy Polyakov