On Mon, Dec 18, 2006 at 09:17:28AM -0800, Stephen Hemminger ([EMAIL PROTECTED])
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 <[EMAIL PROTECTED]>
--
Evgeniy Polyakov
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
