Subject: Re: [Regression] 2.6.34-rc1 sky2 mtu on second port defaults to 576

From: Michael Breuer <[email-masked]>
Date: Tue, 16 Mar 2010 12:17:20 -0400

On 3/16/2010 11:03 AM, Michael Breuer wrote:
> Haven't bisected - problem seemed to have started around 
> 2.6.34-rc1-0933 (not seen before the rc1 tag).
>
> On boot, eth1 ends up with MTU of 576 (eth0 is 1500). My f12 startup 
> scripts are not setting MTU (never have).
>
>
> Nothing of note in dmesg
> No change to .config
> No mtu change reported in log.
>
> Basically, sky2 reports eth1 up... and within the same second begins 
> reporting receive length errors. Most network functions via eth1 fail.
>
> ifconfig eth1 reveals mtu of 576, setting mtu to 1500 restores network 
> functionality.
>
> Booting back to 2.6.33-06233 (git from March 8) the problem does not 
> manifest.
>
> I'll bisect if this isn't obvious to someone.
> -- 
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to [email-masked]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
Never mind... Cablevision changed my cable modem... dhcp is setting the 
mtu option to 576 (never did before). grrrr. My one fallback test seems 
to have been a fluke.