sky2 rx length error

[David Ehrlich]

After upgrade from Hardy to Intrepid, network throughput has decreased considerably. I verified the limited bandwidth using http://reviews.cnet.com/internet-speed-test/ from both Intrepid and non-Intrepid based machines.

dmesg is continuously reporting the following:
[ 266.436193] sky2 eth0: rx length error: status 0x45a0100 length 598
[ 266.463250] sky2 eth0: rx length error: status 0x45a0100 length 598
[ 266.776521] sky2 eth0: rx length error: status 0x45a0100 length 598
[ 321.473543] __ratelimit: 9 callbacks suppressed

Attached is a tar file containing the four log files as requested by the Kernel Team Bug Policies page: https://wiki.ubuntu.com/KernelTeamBugPolicies.

This issue did not impact Hardy to my knowledge. I did not see a similar report in bugzilla.kernel.org.

[minisori (minisori)]

I can confirm this too.

[israel vainsencher (israel-mat)]

same with me, on a vaio vgn-tz170n, using a router.
the problem doesn't seem to occur with direct wired connection, nor with wireless.

[madbam (bennyalm)]

I have this problem to, do anyone have some more info what it is, and if there is a workaround?

[Mihai Tanasescu (mihai-duras)]

Let me also join the club:)
I have the same bug.

[madbam (bennyalm)]

Well. I do not have the same problem any more. I changed MTU to 1492, and it
has moved smooth since then.
Cheers,
/Ben

On Fri, Apr 3, 2009 at 9:25 PM, Mihai Tanasescu <email address hidden> wrote:

> Let me also join the club:)
> I have the same bug.
>
> --
> sky2 rx length error
> https://bugs.launchpad.net/bugs/292445
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: New
>
> Bug description:
> After upgrade from Hardy to Intrepid, network throughput has decreased
> considerably. I verified the limited bandwidth using
> http://reviews.cnet.com/internet-speed-test/ from both Intrepid and
> non-Intrepid based machines.
>
> dmesg is continuously reporting the following:
> [ 266.436193] sky2 eth0: rx length error: status 0x45a0100 length 598
> [ 266.463250] sky2 eth0: rx length error: status 0x45a0100 length 598
> [ 266.776521] sky2 eth0: rx length error: status 0x45a0100 length 598
> [ 321.473543] __ratelimit: 9 callbacks suppressed
>
> Attached is a tar file containing the four log files as requested by the
> Kernel Team Bug Policies page:
> https://wiki.ubuntu.com/KernelTeamBugPolicies.
>
> This issue did not impact Hardy to my knowledge. I did not see a similar
> report in bugzilla.kernel.org.
>

[Mihai Tanasescu (mihai-duras)]

I did the MTU thing with ifconfig and so far (2h now) I got no such error in the logs.

If your fix proves to be lasting..then I guess the beer's on me:)

Thanks madbam.

[kernel-janitor (kernel-janitor)]

Hi David,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 292445

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[David Ehrlich (david-ehrlich)]

When I encountered the problem, I was connecting a gigabit network card to 100Mb switch. When I upgraded to a gigabit switch, the problem disappeared.

[Leann Ogasawara (leannogasawara)]

Thanks for the update. I'll go ahead and close this bug for now. If anyone else is able to confirm the issue remains with the latest Karmic release and using the original configuration David noted, feel free to reopen. Thanks.