Am Thu, 8 Nov 2007 08:52:56 +0100
schrieb Hans-Jürgen Koch <[email protected]>:
> Am Wed, 07 Nov 2007 11:07:07 -0500
> schrieb Mark Lord <[email protected]>:
>
> > My ASUS board has one of these:
> >
> > 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
> > Subsystem: ASUSTeK Computer Inc. Unknown device 81aa Control: I/O+
> > Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
> > SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to
> > >IRQ 16 Region 0: I/O ports at 9800 [size=256]
> > Region 2: Memory at ff3ff000 (64-bit, non-prefetchable)
> > [size=4K] Expansion ROM at ff3c0000 [disabled] [size=128K]
> > Capabilities: [40] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> > PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0
> > DScale=0 PME- Capabilities: [48] Vital Product Data
> > Capabilities: [50] Message Signalled Interrupts: Mask-
> > 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000
> > Capabilities: [60] Express Endpoint IRQ 0
> > Device: Supported: MaxPayload 1024 bytes, PhantFunc
> > 0, ExtTag+ Device: Latency L0s <1us, L1 unlimited
> > Device: AtnBtn+ AtnInd+ PwrInd+
> > Device: Errors: Correctable- Non-Fatal- Fatal-
> > Unsupported- Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> > Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
> > Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s,
> > Port 0 Link: Latency L0s unlimited, L1 unlimited
> > Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
> > Link: Speed 2.5Gb/s, Width x1
> > Capabilities: [84] Vendor Specific Information
> >
> > It works perfectly in 2.6.23.
> > It does not work in 2.6.24-rc2. Dunno about -rc1 or earlier -git*.
> >
> > Without CONFIG_PCI_MSI, it works slightly, enough to ping it a
> > couple of times, but it then dies when used for anything real:
> >
> > r8169 Gigabit Ethernet driver 2.2LK loaded
> > r8169 0000:01:00.0: no MSI. Back to INTx.
> > ...
> > eth0: RTL8168b/8111b at 0xf884a000, 00:17:31:64:e0:bc, XID
> > 30000000 IRQ 16 ...
> > r8169: eth0: link up
> > ...
> > kernel: NETDEV WATCHDOG: eth0: transmit timed out
> > r8169: eth0: link up
> > ...
> > Not usable from this point on.
>
> Same problem here with a MSI K9AGM2 board. The problem appeared in
> 2.6.24-rc1 (http://bugzilla.kernel.org/show_bug.cgi?id=9257).
>
> It seems to be better in -rc2, at least the chip is detected again. I
> can assign an IP to that interface and bring it up, but no data
> traffic is possible. After some tests in both directions, ifconfig
> reports 157.6 KiB RX bytes, but TX bytes is 0, so sent packets seem
> to disappear quite early.
The patch just submitted by Francois Romieu fixes the problem.
Thanks,
Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
