From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org
Cc: e1000-devel@lists.sf.net
Subject: Fw: [Bug 43277] New: net/e1000e set mtu larger than 1500 fails
Date: Tue, 22 May 2012 11:19:50 -0700 [thread overview]
Message-ID: <20120522111950.4548747c@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Tue, 22 May 2012 18:13:21 +0000 (UTC)
From: bugzilla-daemon@bugzilla.kernel.org
To: shemminger@linux-foundation.org
Subject: [Bug 43277] New: net/e1000e set mtu larger than 1500 fails
https://bugzilla.kernel.org/show_bug.cgi?id=43277
Summary: net/e1000e set mtu larger than 1500 fails
Product: Networking
Version: 2.5
Kernel Version: 3.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
AssignedTo: shemminger@linux-foundation.org
ReportedBy: che@chrekh.se
Regression: Yes
In kernel 3.4 I can no longer use jumbo-frames with my e1000e network
interface.
$ sudo ip link set eth1 mtu 9000
RTNETLINK answers: Invalid argument
Card-info (from kernel-log)
e1000e 0000:05:00.1: eth1: (PCI Express:2.5GT/s:Width x4) 00:1b:78:59:84:25
e1000e 0000:05:00.1: eth1: Intel(R) PRO/1000 Network Connection
e1000e 0000:05:00.1: eth1: MAC: 0, PHY: 4, PBA No: D51930-003
I have bisected and found:
70495a500d787c0c90a136acf454cb7d0eecd82e is the first bad commit
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-05-22 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 18:19 Stephen Hemminger [this message]
2012-05-22 18:25 ` [Bug 43277] New: net/e1000e set mtu larger than 1500 fails Stephen Hemminger
2012-05-22 18:28 ` Allan, Bruce W
2012-05-22 18:39 ` Christer Ekholm
2012-05-22 18:59 ` Ben Hutchings
2012-05-22 21:29 ` 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=20120522111950.4548747c@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=e1000-devel@lists.sf.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.