[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bok3oww6.fsf@spindle.srvr.nix>
Date: Fri, 29 Jun 2012 00:10:49 +0100
From: Nix <nix@...eri.org.uk>
To: Francois Romieu <romieu@...zoreil.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 3.4.x regression: rtl8169: frequent resets
On 28 Jun 2012, Francois Romieu stated:
> Nix <nix@...eri.org.uk> :
>> Francois Romieu <romieu@...zoreil.com> :
>> > Can you try and revert 036dafa28da1e2565a8529de2ae663c37b7a0060 ?
>>
>> I can try, but there's been a *lot* of code motion since then, 'git
>> revert' fails hilariously (trying to patch obviously the wrong places):
>> I'll have to do it by hand.
>
> There is a single line reject in rtl8169_start_xmit. Other than that it
> should patch -p1 -R fine.
... and indeed it does. Weird, why does git revert fail so badly when
patch and git apply are both happy?!
I'll reboot into this kernel tomorrow, and report back in a few days (or
sooner if it goes wrong).
>> [ 1.341389] r8169 0000:06:00.0: eth0: jumbo features [frames: 6128 bytes, tx checksumming: ko]
>
> This chipset is not supposed to be pushed beyond 6128 bytes.
Interesting. It's always worked flawlessly at 7200 for me before, until,
uh, last year when it stopped working and I never noticed (in fact
a 7200-byte MTU was how the machine was shipped to me :) ).
I guess I'll knock it down to 6128 then, less than 1000 bytes isn't
going to ruin performance by any means...
... aand that works. thanks! (Let's see if the link stuttering continues. I
expect it will, though it's been three hours since the last stutter...)
--
NULL && (void)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists