* Re: sky2 rx length errors [not found] <c5bd819b0909180641n7c353b80tc15b9c9fe02d5c95@mail.gmail.com> @ 2009-09-20 6:35 ` Andrew Morton 2009-09-20 18:05 ` Stephen Hemminger 0 siblings, 1 reply; 3+ messages in thread From: Andrew Morton @ 2009-09-20 6:35 UTC (permalink / raw) To: Grozdan; +Cc: linux-kernel, Stephen Hemminger, netdev (added cc's from the MAINTAINERS file) On Fri, 18 Sep 2009 15:41:45 +0200 Grozdan <neutrino8@gmail.com> wrote: > Hi, > > I have a Marvell onboard NIC (88E8053) and I've been noticing for a > while now a bit weird behavior with the sky2 driver. This mostly > occurs with newer kernels (2.6.30, 2.6.31) and my older distro kernel > (2.6.27.21) does not seem to have the same problem. Basically, the > sky2 driver will randomly and unpredictably spew rx length error > messages and reboot itself. I also noticed in dmesg that this mostly > occurs after "martian destination" messages. After this message, sky2 > starts spewing messages as shown below and then reboots itself. It is > not really a big problem for me, but since I'm virtually always logged > in in IRC, the client always loses connection, waits for a few minutes > to get a response from the server and then relogs me again. I do not > think it's a HW problem as the Marvell NIC otherwise works perfectly > and I've checked my cable modem too which operates without a problem. > Any ideas? > > PS: please cc me as I'm not subscribed to the mailing list > > sky2 driver version 1.23 > sky2 0000:05:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 > sky2 0000:05:00.0: setting latency timer to 64 > sky2 0000:05:00.0: PCI: Disallowing DAC for device > sky2 0000:05:00.0: Yukon-2 EC chip revision 2 > sky2 0000:05:00.0: irq 53 for MSI/MSI-X > sky2 0000:05:00.0: No interrupt generated using MSI, switching to INTx mode. > sky2 eth0: addr 00:11:d8:a1:5b:0e > sky2 eth0: enabling interface > sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx > ..... > ..... > martian destination 0.0.0.0 from 172.23.204.1, dev eth0 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x5ea0100 length 598 > sky2 eth0: rx length error: status 0x5ea0100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x5ea0100 length 598 > sky2 eth0: rx length error: status 0x5ea0100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 > sky2 eth0: rx length error: status 0x4420100 length 598 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sky2 rx length errors 2009-09-20 6:35 ` sky2 rx length errors Andrew Morton @ 2009-09-20 18:05 ` Stephen Hemminger [not found] ` <392fb48f0909201511h34c71e0au838b52c413d517e0@mail.gmail.com> 0 siblings, 1 reply; 3+ messages in thread From: Stephen Hemminger @ 2009-09-20 18:05 UTC (permalink / raw) To: Andrew Morton; +Cc: Grozdan, linux-kernel, Stephen Hemminger, netdev On Sat, 19 Sep 2009 23:35:36 -0700 Andrew Morton <akpm@linux-foundation.org> wrote: > (added cc's from the MAINTAINERS file) > > On Fri, 18 Sep 2009 15:41:45 +0200 Grozdan <neutrino8@gmail.com> wrote: > > > Hi, > > > > I have a Marvell onboard NIC (88E8053) and I've been noticing for a > > while now a bit weird behavior with the sky2 driver. This mostly > > occurs with newer kernels (2.6.30, 2.6.31) and my older distro kernel > > (2.6.27.21) does not seem to have the same problem. Basically, the > > sky2 driver will randomly and unpredictably spew rx length error > > messages and reboot itself. I also noticed in dmesg that this mostly > > occurs after "martian destination" messages. After this message, sky2 > > starts spewing messages as shown below and then reboots itself. It is > > not really a big problem for me, but since I'm virtually always logged > > in in IRC, the client always loses connection, waits for a few minutes > > to get a response from the server and then relogs me again. I do not > > think it's a HW problem as the Marvell NIC otherwise works perfectly > > and I've checked my cable modem too which operates without a problem. > > Any ideas? > > > > PS: please cc me as I'm not subscribed to the mailing list > > > > sky2 driver version 1.23 > > sky2 0000:05:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 > > sky2 0000:05:00.0: setting latency timer to 64 > > sky2 0000:05:00.0: PCI: Disallowing DAC for device > > sky2 0000:05:00.0: Yukon-2 EC chip revision 2 > > sky2 0000:05:00.0: irq 53 for MSI/MSI-X > > sky2 0000:05:00.0: No interrupt generated using MSI, switching to INTx mode. > > sky2 eth0: addr 00:11:d8:a1:5b:0e > > sky2 eth0: enabling interface > > sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx > > ..... > > ..... > > martian destination 0.0.0.0 from 172.23.204.1, dev eth0 > > sky2 eth0: rx length error: status 0x4420100 length 598 > > sky2 eth0: rx length error: status 0x5ea0100 length 598 This error status occurs if the length reported by the PHY does not match the len reported by the DMA engine. The error status is: 0x4420100 = length 1090 + broadcast packet... No idea what is on your network, but perhaps there is some MTU confusion? Since martian destination seems related, knowing more about that packet might help. ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <392fb48f0909201511h34c71e0au838b52c413d517e0@mail.gmail.com>]
* Re: sky2 rx length errors [not found] ` <392fb48f0909201511h34c71e0au838b52c413d517e0@mail.gmail.com> @ 2009-09-21 1:46 ` Stephen Hemminger 0 siblings, 0 replies; 3+ messages in thread From: Stephen Hemminger @ 2009-09-21 1:46 UTC (permalink / raw) To: Mike McCormack Cc: Andrew Morton, Grozdan, linux-kernel, Stephen Hemminger, netdev On Mon, 21 Sep 2009 07:11:21 +0900 Mike McCormack <mikem@ring3k.org> wrote: > 2009/9/21 Stephen Hemminger <shemminger@vyatta.com> > > > On Sat, 19 Sep 2009 23:35:36 -0700 > > Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > (added cc's from the MAINTAINERS file) > > > > > > On Fri, 18 Sep 2009 15:41:45 +0200 Grozdan <neutrino8@gmail.com> wrote: > > > > <snip> > > > > martian destination 0.0.0.0 from 172.23.204.1, dev eth0 > > > > sky2 eth0: rx length error: status 0x4420100 length 598 > > > > sky2 eth0: rx length error: status 0x5ea0100 length 598 > > > > This error status occurs if the length reported by the PHY does not > > match the len reported by the DMA engine. The error status is: > > 0x4420100 = length 1090 + broadcast packet... > > > > No idea what is on your network, but perhaps there is some MTU confusion? > > Since martian destination seems related, knowing more about that packet > > might help. > > > > > This appears to be the same problem reported at: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/292445 > > Mike This really looks like multiple packets are getting smashed together into one DMA, i.e a hardware timing related issue. it might be possible to work around the problem by separating them. -- ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-09-21 1:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <c5bd819b0909180641n7c353b80tc15b9c9fe02d5c95@mail.gmail.com>
2009-09-20 6:35 ` sky2 rx length errors Andrew Morton
2009-09-20 18:05 ` Stephen Hemminger
[not found] ` <392fb48f0909201511h34c71e0au838b52c413d517e0@mail.gmail.com>
2009-09-21 1:46 ` Stephen Hemminger
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).