From: Josh Boyer <jwboyer@redhat.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jiri Pirko <jpirko@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fedoraproject.org
Subject: e1000 vlan functionality broken in 3.1
Date: Mon, 21 Nov 2011 14:28:39 -0500 [thread overview]
Message-ID: <20111121192839.GA2585@zod.bos.redhat.com> (raw)
Hi All,
We've had a couple of reports of the e1000 driver no longer working with
tagged VLANs in the 3.1 kernel. The bug report has much more detail
here:
https://bugzilla.redhat.com/show_bug.cgi?id=754589
The summary is, if you turn of rxvlan and tx offloading, the driver
seems to work fine with 3.1 again whereas this wasn't needed on 3.0.
(Fedora calls 3.0 2.6.40 on Fedora 15, but that is strictly a naming
thing.)
Looking through the commit logs, 5622e4044a91 seems to be the most
relevant commit between those versions. Does anyone have any ideas?
josh
next reply other threads:[~2011-11-21 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 19:28 Josh Boyer [this message]
2011-11-21 22:05 ` e1000 vlan functionality broken in 3.1 Jiri Pirko
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=20111121192839.GA2585@zod.bos.redhat.com \
--to=jwboyer@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jpirko@redhat.com \
--cc=kernel-team@fedoraproject.org \
--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).