FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 05-30-2010, 12:42 PM
Moritz Muehlenhoff
 
Default Bug#492853: problem exists

tags 492853 moreinfo
thanks

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
>
> [459277.144466] sky2 eth0: rx length error: status 0x5660100 length 2758
> [459456.017982] eth0: hw csum failure.
> [459456.017988] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1
> [459456.017990]
> [459456.017991] Call Trace:
> [459456.017992] <IRQ> [<ffffffff803ba65e>] netdev_rx_csum_fault+0x29/0x31
> [459456.018013] [<ffffffff803b70fe>] __skb_checksum_complete_head+0x43/0x56
> [459456.018017] [<ffffffff803b711d>] __skb_checksum_complete+0xc/0x11
> [459456.018021] [<ffffffff8024ac5a>] getnstimeofday+0x39/0x98
> [459456.018024] [<ffffffff803f3e4b>] tcp_v4_rcv+0x132/0x6e3
> [459456.018029] [<ffffffff803d95c8>] ip_rcv_finish+0x0/0x352
> [459456.018034] [<ffffffff803d9a3a>] ip_local_deliver_finish+0x120/0x1dd
> [459456.018038] [<ffffffff803d98f7>] ip_rcv_finish+0x32f/0x352
> [459456.018042] [<ffffffff803d9e14>] ip_rcv+0x22e/0x273
> [459456.018051] [<ffffffffa00921a9>] :sky2:sky2_poll+0x8d6/0xbfe
> [459456.018057] [<ffffffff803f0cb5>] tcp_write_timer+0x633/0x762
> [459456.018061] [<ffffffff8024ac5a>] getnstimeofday+0x39/0x98
> [459456.018066] [<ffffffff803bc4ee>] net_rx_action+0xab/0x1da
> [459456.018072] [<ffffffff802393fb>] __do_softirq+0x5c/0xd1
> [459456.018077] [<ffffffff8020d2cc>] call_softirq+0x1c/0x28
> [459456.018081] [<ffffffff8020f3d0>] do_softirq+0x3c/0x81
> [459456.018084] [<ffffffff8023935b>] irq_exit+0x3f/0x83
> [459456.018087] [<ffffffff8020f630>] do_IRQ+0xb9/0xd9
> [459456.018090] [<ffffffff8020c46d>] ret_from_intr+0x0/0x19
> [459456.018092] <EOI> [<ffffffffa000c269>] rocessor:acpi_idle_enter_bm+0x2b3/0x327
> [459456.018111] [<ffffffff803a9cbf>] cpuidle_idle_call+0x7a/0xaf
> [459456.018113] [<ffffffff803a9c45>] cpuidle_idle_call+0x0/0xaf
> [459456.018116] [<ffffffff8020ac79>] cpu_idle+0x89/0xb3
> [459456.018126]
>
> "ifdown eth0 ; ifup eth0" helps to bring the ethernet interface back to
> good state.
>
> If you need more info about my hardware (or anything else), please, tell me.
>
> Any propositions are welcome (such as "try newer kernel version" or
> "try that patch").

Hi,
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
us whether the problem persists. If so, we should report it upstream
to the kernel.org developers.

The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.

Thanks,
Moritz




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100530124243.GO2398@galadriel.inutil.org">http://lists.debian.org/20100530124243.GO2398@galadriel.inutil.org
 
Old 05-30-2010, 10:26 PM
Ben Hutchings
 
Default Bug#492853: problem exists

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.
 

Thread Tools




All times are GMT. The time now is 07:56 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org