[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#321403: 8139too network driver won't work with my card (it did with 2.6.8)



Package: kernel-source-2.6.11
Version: 2.6.11-7
Severity: important

Hi there!

When I tried to upgrade my kernel from 2.6.8 to 2.6.11, 
I was shocked to see that my Ethernet card stopped working.

I am using the standard Debian kernel sources to build my own kernels.

I tested kernel-source-2.6.10, and (because kernel-source-2.6.9 is no longer
in Debian) the vanilla linux-2.6.9 from kernel.org, and neither of them worked.

So it seems the thing broke from 2.6.8 to 2.6.9.

  * * *
  
My card is: (lspci output on 2.6.8)

0000:00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

The 2.6.8 kernel says this, then loading the driver:

8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xe281c000, 00:20:18:8d:3d:40, IRQ 10
eth0:  Identified 8139 chip type 'RTL-8139B'

With, 2.6.11, at first it seems to be OK, too:

eth0: RealTek RTL8139 at 0xe2a38000, 00:20:18:8d:3d:40, IRQ 10
eth0:  Identified 8139 chip type 'RTL-8139B'
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1

...but when I try to send out data, it says:

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0c 0005 c07f media 00.
eth0: Tx queue start entry 4  dirty entry 0.
eth0:  Tx descriptor 0 is 0008a156. (queue head)
eth0:  Tx descriptor 1 is 0008a156.
eth0:  Tx descriptor 2 is 0008a156.
eth0:  Tx descriptor 3 is 0008a156.
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1

   * * *
   
Since until this is resolved, I am stucked to 2.6.8, I am very eager to help you
debugging this. Please tell me how can I help you to fix this.


    Kristof Csillag
    



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2)

Versions of packages kernel-source-2.6.11 depends on:
(irrelevant)

-- no debconf information



Reply to: