Processed: Re: Bug#492853: problem exists
Processing commands for cont...@bugs.debian.org: tags 492853 moreinfo Bug #492853 [linux-2.6] [linux-image-2.6.25-2-amd64] sky2 eth0: rx length error: status 0x4660100 length 598 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 492853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127522337331159.transcr...@bugs.debian.org
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 b000 [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 [803ba65e] netdev_rx_csum_fault+0x29/0x31 [459456.018013] [803b70fe] __skb_checksum_complete_head+0x43/0x56 [459456.018017] [803b711d] __skb_checksum_complete+0xc/0x11 [459456.018021] [8024ac5a] getnstimeofday+0x39/0x98 [459456.018024] [803f3e4b] tcp_v4_rcv+0x132/0x6e3 [459456.018029] [803d95c8] ip_rcv_finish+0x0/0x352 [459456.018034] [803d9a3a] ip_local_deliver_finish+0x120/0x1dd [459456.018038] [803d98f7] ip_rcv_finish+0x32f/0x352 [459456.018042] [803d9e14] ip_rcv+0x22e/0x273 [459456.018051] [a00921a9] :sky2:sky2_poll+0x8d6/0xbfe [459456.018057] [803f0cb5] tcp_write_timer+0x633/0x762 [459456.018061] [8024ac5a] getnstimeofday+0x39/0x98 [459456.018066] [803bc4ee] net_rx_action+0xab/0x1da [459456.018072] [802393fb] __do_softirq+0x5c/0xd1 [459456.018077] [8020d2cc] call_softirq+0x1c/0x28 [459456.018081] [8020f3d0] do_softirq+0x3c/0x81 [459456.018084] [8023935b] irq_exit+0x3f/0x83 [459456.018087] [8020f630] do_IRQ+0xb9/0xd9 [459456.018090] [8020c46d] ret_from_intr+0x0/0x19 [459456.018092] EOI [a000c269] :processor:acpi_idle_enter_bm+0x2b3/0x327 [459456.018111] [803a9cbf] cpuidle_idle_call+0x7a/0xaf [459456.018113] [803a9c45] cpuidle_idle_call+0x0/0xaf [459456.018116] [8020ac79] 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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100530124243.go2...@galadriel.inutil.org
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 b000 [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
Bug#492853: problem exists
On Wed, Aug 19, 2009 at 07:14:54PM +0200, Moritz Muehlenhoff wrote: Alexandra N. Kossovsky wrote: On Sat, Aug 15, 2009 at 07:41:56PM +0200, Moritz Muehlenhoff wrote: Sorry for the late followup. Are these messages appearing for any traffic or just specific patterns? As far as I've seen it, the problem is VLAN-related. It occurs if I enable some VLANs on the interface. These VLANs are used by test boxes (a lot of embedded linuxes with various software onboard), so it is hard to predict what do they send to the net because of software and hardware errors. Currently, I've disabled VLANs (they are not really necessary on that computer), and there are no problems... Do some of your embedded devices use big endian byte order? It suspect your issue is fixed by the following commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b9389796fa4c87fbdff33816e317cdae5f36dd0b I'm afraid I do not understand your idea. Some embedded devices are big endian, but the device with sky2 driver is little-endian (amd64, Intel Core Duo, just usual desktop). As far as I can see from the comments to the commit above, the patch fixes sky2 driver when it works with big endian host, which is not the case. -- Alexandra N. Kossovsky OKTET Labs (http://www.oktetlabs.ru/) Phones: +7(921)956-42-86(mobile) +7(812)783-21-91(office) e-mail: sa...@oktetlabs.ru -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#492853: problem exists
On Thu, Aug 20, 2009 at 01:45:07PM +0400, Alexandra N. Kossovsky wrote: On Wed, Aug 19, 2009 at 07:14:54PM +0200, Moritz Muehlenhoff wrote: Alexandra N. Kossovsky wrote: On Sat, Aug 15, 2009 at 07:41:56PM +0200, Moritz Muehlenhoff wrote: Sorry for the late followup. Are these messages appearing for any traffic or just specific patterns? As far as I've seen it, the problem is VLAN-related. It occurs if I enable some VLANs on the interface. These VLANs are used by test boxes (a lot of embedded linuxes with various software onboard), so it is hard to predict what do they send to the net because of software and hardware errors. Currently, I've disabled VLANs (they are not really necessary on that computer), and there are no problems... Do some of your embedded devices use big endian byte order? It suspect your issue is fixed by the following commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b9389796fa4c87fbdff33816e317cdae5f36dd0b I'm afraid I do not understand your idea. Some embedded devices are big endian, but the device with sky2 driver is little-endian (amd64, Intel Core Duo, just usual desktop). As far as I can see from the comments to the commit above, the patch fixes sky2 driver when it works with big endian host, which is not the case. I misunderstodd. I thought your embedded devices were running Debian kernels as well and the error was seen across several systems. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#492853: problem exists
Alexandra N. Kossovsky wrote: On Sat, Aug 15, 2009 at 07:41:56PM +0200, Moritz Muehlenhoff wrote: Sorry for the late followup. Are these messages appearing for any traffic or just specific patterns? As far as I've seen it, the problem is VLAN-related. It occurs if I enable some VLANs on the interface. These VLANs are used by test boxes (a lot of embedded linuxes with various software onboard), so it is hard to predict what do they send to the net because of software and hardware errors. Currently, I've disabled VLANs (they are not really necessary on that computer), and there are no problems... Do some of your embedded devices use big endian byte order? It suspect your issue is fixed by the following commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b9389796fa4c87fbdff33816e317cdae5f36dd0b Could you please test, whether the problem is fixed if running one of he trunk kernels based on 2.6.31-rcX (which already include the patch)? http://wiki.debian.org/DebianKernel If it fixes the problem, we can add the patch to a kernel update in a stable point update. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#492853: problem exists
On Sat, Aug 15, 2009 at 07:41:56PM +0200, Moritz Muehlenhoff wrote: Sorry for the late followup. Are these messages appearing for any traffic or just specific patterns? As far as I've seen it, the problem is VLAN-related. It occurs if I enable some VLANs on the interface. These VLANs are used by test boxes (a lot of embedded linuxes with various software onboard), so it is hard to predict what do they send to the net because of software and hardware errors. Currently, I've disabled VLANs (they are not really necessary on that computer), and there are no problems... -- Alexandra N. Kossovsky OKTET Labs (http://www.oktetlabs.ru/) Phones: +7(921)956-42-86(mobile) +7(812)783-21-91(office) e-mail: sa...@oktetlabs.ru -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 b000 [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 [803ba65e] netdev_rx_csum_fault+0x29/0x31 [459456.018013] [803b70fe] __skb_checksum_complete_head+0x43/0x56 [459456.018017] [803b711d] __skb_checksum_complete+0xc/0x11 [459456.018021] [8024ac5a] getnstimeofday+0x39/0x98 [459456.018024] [803f3e4b] tcp_v4_rcv+0x132/0x6e3 [459456.018029] [803d95c8] ip_rcv_finish+0x0/0x352 [459456.018034] [803d9a3a] ip_local_deliver_finish+0x120/0x1dd [459456.018038] [803d98f7] ip_rcv_finish+0x32f/0x352 [459456.018042] [803d9e14] ip_rcv+0x22e/0x273 [459456.018051] [a00921a9] :sky2:sky2_poll+0x8d6/0xbfe [459456.018057] [803f0cb5] tcp_write_timer+0x633/0x762 [459456.018061] [8024ac5a] getnstimeofday+0x39/0x98 [459456.018066] [803bc4ee] net_rx_action+0xab/0x1da [459456.018072] [802393fb] __do_softirq+0x5c/0xd1 [459456.018077] [8020d2cc] call_softirq+0x1c/0x28 [459456.018081] [8020f3d0] do_softirq+0x3c/0x81 [459456.018084] [8023935b] irq_exit+0x3f/0x83 [459456.018087] [8020f630] do_IRQ+0xb9/0xd9 [459456.018090] [8020c46d] ret_from_intr+0x0/0x19 [459456.018092] EOI [a000c269] :processor:acpi_idle_enter_bm+0x2b3/0x327 [459456.018111] [803a9cbf] cpuidle_idle_call+0x7a/0xaf [459456.018113] [803a9c45] cpuidle_idle_call+0x0/0xaf [459456.018116] [8020ac79] 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). Sorry for the late followup. Are these messages appearing for any traffic or just specific patterns? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#492853: problem exists
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 b000 [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 [803ba65e] netdev_rx_csum_fault+0x29/0x31 [459456.018013] [803b70fe] __skb_checksum_complete_head+0x43/0x56 [459456.018017] [803b711d] __skb_checksum_complete+0xc/0x11 [459456.018021] [8024ac5a] getnstimeofday+0x39/0x98 [459456.018024] [803f3e4b] tcp_v4_rcv+0x132/0x6e3 [459456.018029] [803d95c8] ip_rcv_finish+0x0/0x352 [459456.018034] [803d9a3a] ip_local_deliver_finish+0x120/0x1dd [459456.018038] [803d98f7] ip_rcv_finish+0x32f/0x352 [459456.018042] [803d9e14] ip_rcv+0x22e/0x273 [459456.018051] [a00921a9] :sky2:sky2_poll+0x8d6/0xbfe [459456.018057] [803f0cb5] tcp_write_timer+0x633/0x762 [459456.018061] [8024ac5a] getnstimeofday+0x39/0x98 [459456.018066] [803bc4ee] net_rx_action+0xab/0x1da [459456.018072] [802393fb] __do_softirq+0x5c/0xd1 [459456.018077] [8020d2cc] call_softirq+0x1c/0x28 [459456.018081] [8020f3d0] do_softirq+0x3c/0x81 [459456.018084] [8023935b] irq_exit+0x3f/0x83 [459456.018087] [8020f630] do_IRQ+0xb9/0xd9 [459456.018090] [8020c46d] ret_from_intr+0x0/0x19 [459456.018092] EOI [a000c269] :processor:acpi_idle_enter_bm+0x2b3/0x327 [459456.018111] [803a9cbf] cpuidle_idle_call+0x7a/0xaf [459456.018113] [803a9c45] cpuidle_idle_call+0x0/0xaf [459456.018116] [8020ac79] 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). Regards, Alexandra. -- Alexandra N. Kossovsky OKTET Labs (http://www.oktetlabs.ru/) Phones: +7(921)956-42-86(mobile) +7(812)783-21-91(office) e-mail: sa...@oktetlabs.ru -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
