Fw: [Bugme-new] [Bug 4566] New: B44 Randomly driver starts sending garbage and stops receiving

Fw: [Bugme-new] [Bug 4566] New: B44 Randomly driver starts sending garbage and stops receiving

[Andrew Morton]

Begin forwarded message:

Date: Sat, 30 Apr 2005 14:04:14 -0700
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4566] New: B44 Randomly driver starts sending garbage and stops receiving


http://bugme.osdl.org/show_bug.cgi?id=4566

           Summary: B44 Randomly driver starts sending garbage and stops
                    receiving
    Kernel Version: 2.6.11
            Status: NEW
          Severity: high
             Owner: jgarzik@pobox.com
         Submitter: bonbons67@internet.lu


Distribution: Gentoo 
Hardware Environment: Acer TM66x 
    0000:02:02.0 Class 0200: 14e4:4401 (rev 01)  
        Subsystem: 1025:0035  
        Flags: bus master, fast devsel, latency 64, IRQ 10  
        Memory at e0204000 (32-bit, non-prefetchable)  
        Capabilities: [40] Power Management version 2  
    Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)  
        Subsystem: Acer Incorporated [ALI]: Unknown device 0035  
        Flags: bus master, fast devsel, latency 64, IRQ 10  
        Memory at e0204000 (32-bit, non-prefetchable)  
        Capabilities: [40] Power Management version 2  
Software Environment: GCC 3.3.5-20050130  
Problem Description:  
After some time of normal network communication, suddenly incoming traffic   
stops to be received and only outgoing traffic remains.  
Looking at the traffic sent from another machine in the network with tcpdump I   
get following output (repeating at a high rate): 
22:33:01.018523 00:40:05:43:5e:fe > 01:80:c2:00:00:01, ethertype Unknown 
(0x8808), length 60: 
    0x0000: 0001 ffff 0000 0000 0000 0000 0000 0000 
    0x0010: 0000 0000 0000 0000 0000 0000 0000 0000 
    0x0020: 0000 0000 0000 0000 0000 0000 0000 
dmesg does not produce any useful output about this. 
 
ifconfig eth0 down 
ifconfig eth0 up 
Restores the communications and stops the garbage traffic. 
 
 
Steps to reproduce: 
Happens randomly, some days very often some days not at all 
 
 
I have not yet tried to disable ACPI (as suggesed in bug #3050)

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

Re: Fw: [Bugme-new] [Bug 4566] New: B44 Randomly driver starts sending garbage and stops receiving

[Lennert Buytenhek]

On Sat, Apr 30, 2005 at 02:23:34PM -0700, Andrew Morton wrote:

> get following output (repeating at a high rate): 
> 22:33:01.018523 00:40:05:43:5e:fe > 01:80:c2:00:00:01, ethertype Unknown 
> (0x8808), length 60: 
>     0x0000: 0001 ffff 0000 0000 0000 0000 0000 0000 
>     0x0010: 0000 0000 0000 0000 0000 0000 0000 0000 
>     0x0020: 0000 0000 0000 0000 0000 0000 0000 
> dmesg does not produce any useful output about this. 

Isn't that a PAUSE frame?

Probably something in the b44 driver gets screwed so that it stops
processing RX traffic, the MAC's RX FIFO then fills up, and the
MAC (naturally) asserts flow control by periodically (in the range
of tens to hundreds of times per second) sending PAUSE frames to
its link partner as long as there's not enough space in its RX FIFO.

These PAUSE frames should not be seen by other hosts on the LAN,
though -- your switch should not autonegotiate flow control with
your b44 NIC if it doesn't support it.  (Or perhaps the b44 driver
enables flow control even though it hasn't been negotiated..)


--L

Re: [Bugme-new] [Bug 4566] New: B44 Randomly driver starts sending garbage and stops receiving

[Bruno]

On Sunday 01 May 2005 00:28, Lennert Buytenhek wrote:
> On Sat, Apr 30, 2005 at 02:23:34PM -0700, Andrew Morton wrote:
> > get following output (repeating at a high rate):
> > 22:33:01.018523 00:40:05:43:5e:fe > 01:80:c2:00:00:01, ethertype Unknown
> > (0x8808), length 60:
> >     0x0000: 0001 ffff 0000 0000 0000 0000 0000 0000
> >     0x0010: 0000 0000 0000 0000 0000 0000 0000 0000
> >     0x0020: 0000 0000 0000 0000 0000 0000 0000
> > dmesg does not produce any useful output about this.
>
> Isn't that a PAUSE frame?
>
> Probably something in the b44 driver gets screwed so that it stops
> processing RX traffic, the MAC's RX FIFO then fills up, and the
> MAC (naturally) asserts flow control by periodically (in the range
> of tens to hundreds of times per second) sending PAUSE frames to
> its link partner as long as there's not enough space in its RX FIFO.
>
> These PAUSE frames should not be seen by other hosts on the LAN,
> though -- your switch should not autonegotiate flow control with
> your b44 NIC if it doesn't support it.  (Or perhaps the b44 driver
> enables flow control even though it hasn't been negotiated..)
>
>
> --L
I don't know what kind of frame that is, but it's causing quite some trouble 
on my network:
 - network communication is broken for all other host (Windows Hosts, ADSL 
router to internet
 - My Linux Server can capture the traffic (it's from that one I executed 
tcpdump, but I don't know if Linux to Linux communication is still possible 
as I never had my desktop running when it happened)
Network works correctly again once I restart the network interface (B44) on 
the Laptop.

I don't know if it passes all the 2 switches on my LAN (first one for sure, 
second one I don't know as there is no box with sniffing-software behind it, 
but the Windows box there does not seem to loose internet connection)

In addition the recorded MAC addresses are not addresses of my hardware. So 
except thet are broadcast/multicats MAC addresses I'm wondering where they do 
come from!

If you have any suggestions on what to do for either fixing the B44 driver or 
at least making it auto-recover rapidly, this would be useful.
If there is more information that I can provide, please tell how I can find it 
out!
(But may take some time, as this problem does not happen every day)

Bruno