[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20090920184606.5a75aba6@nehalam>
Date: Sun, 20 Sep 2009 18:46:06 -0700
From: Stephen Hemminger <shemminger@...tta.com>
To: Mike McCormack <mikem@...g3k.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Grozdan <neutrino8@...il.com>, linux-kernel@...r.kernel.org,
Stephen Hemminger <shemminger@...ux-foundation.org>,
netdev@...r.kernel.org
Subject: Re: sky2 rx length errors
On Mon, 21 Sep 2009 07:11:21 +0900
Mike McCormack <mikem@...g3k.org> wrote:
> 2009/9/21 Stephen Hemminger <shemminger@...tta.com>
>
> > On Sat, 19 Sep 2009 23:35:36 -0700
> > Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > > (added cc's from the MAINTAINERS file)
> > >
> > > On Fri, 18 Sep 2009 15:41:45 +0200 Grozdan <neutrino8@...il.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.
--
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists