From: Michael Breuer <mbreuer@majjas.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [Regression] 2.6.34-rc1 sky2 mtu on second port defaults to 576
Date: Tue, 16 Mar 2010 14:46:49 -0400 [thread overview]
Message-ID: <4B9FD219.4050209@majjas.com> (raw)
In-Reply-To: <4B9FAF10.8000707@majjas.com>
On 3/16/2010 12:17 PM, Michael Breuer wrote:
> 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 majordomo@vger.kernel.org
>> 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.
And one last update... turns out not Cablevision either. There was an
F12 update to dhcp client over the weekend to enable request (and set)
of interface.mtu by default. Previously, dhcp client was not requesting
or setting the mtu.
prev parent reply other threads:[~2010-03-16 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 15:03 [Regression] 2.6.34-rc1 sky2 mtu on second port defaults to 576 Michael Breuer
2010-03-16 16:17 ` Michael Breuer
2010-03-16 18:46 ` Michael Breuer [this message]
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=4B9FD219.4050209@majjas.com \
--to=mbreuer@majjas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).