mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grozdan <neutrino8@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sky2 rx length errors
Date: Sun, 20 Sep 2009 20:16:02 +0200	[thread overview]
Message-ID: <c5bd819b0909201116u5a84c426tdd0f298d7019505d@mail.gmail.com> (raw)
In-Reply-To: <20090920110527.39fd7af5@s6510>

2009/9/20 Stephen Hemminger <shemminger@vyatta.com>:

>
> 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.
>

Hi,

Thanks for the reply. There's nothing on my home network here. It is
just a direct connection from my PC to my cable modem and there's
nothing in between. I've googled a bit and it seems others also
encounter this problem. I've read a few posts on the Ubuntu bugzilla
where people change the MTU from 1500 to 1492 and this fixes the
problem. However, even with this, some report that the problem is
still there. I did the same and it didn't change anything for me. So I
disabled my onboard NIC and added a 3Com one which has been working
perfectly so far and I think I'll just keep using it instead of the
Marvell one.

  reply	other threads:[~2009-09-20 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 13:41 Grozdan
2009-09-20  6:35 ` Andrew Morton
2009-09-20 18:05   ` Stephen Hemminger
2009-09-20 18:16     ` Grozdan [this message]
2009-09-20 18:34       ` Willy Tarreau
2009-09-20 18:46         ` Grozdan
2009-09-20 18:54           ` Willy Tarreau
     [not found]     ` <392fb48f0909201511h34c71e0au838b52c413d517e0@mail.gmail.com>
2009-09-21  1:46       ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c5bd819b0909201116u5a84c426tdd0f298d7019505d@mail.gmail.com \
    --to=neutrino8@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®