On Mon, Jun 22, 2009 at 01:24:53PM +0400, Alexandra N. Kossovsky wrote: > Hi. > > > Does this error still occur with more recent kernel versions? > > The problem exists for me with kernel 2.6.26-2-amd64 (lenny kernel). > > 05:02.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit > Ethernet Controller (rev 14) > Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet > Controller (Asus) > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 64 (5750ns min, 7750ns max), Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 18 > Region 0: Memory at febf8000 (32-bit, non-prefetchable) [size=16K] > Region 1: I/O ports at d800 [size=256] > Expansion ROM at b0000000 [disabled] [size=128K] > Capabilities: [48] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [50] Vital Product Data <?> > Kernel driver in use: skge > Kernel modules: skge [...]
This device is handled by skge, so it is not the same device affected by this bug. Anyway, I would say this is not even the same bug as that originally reported. These log messages: > [459277.144466] sky2 eth0: rx length error: status 0x5660100 length 2758 > [459456.017982] eth0: hw csum failure. [...] show a checksum failure reported 3 minutes after the length mismatch error. Also you say: > "ifdown eth0 ; ifup eth0" helps to bring the ethernet interface back to > good state. so I assume that the interface stops passing traffic, whereas the original report said that it kept working. If you can still reproduce this problem you should make a separate bug report. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
