All of lore.kernel.org
 help / color / mirror / Atom feed
* e1000 vlan functionality broken in 3.1
@ 2011-11-21 19:28 Josh Boyer
  2011-11-21 22:05 ` Jiri Pirko
  0 siblings, 1 reply; 2+ messages in thread
From: Josh Boyer @ 2011-11-21 19:28 UTC (permalink / raw)
  To: Jesse Brandeburg, Jeff Kirsher, Jiri Pirko
  Cc: netdev, linux-kernel, kernel-team

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: e1000 vlan functionality broken in 3.1
  2011-11-21 19:28 e1000 vlan functionality broken in 3.1 Josh Boyer
@ 2011-11-21 22:05 ` Jiri Pirko
  0 siblings, 0 replies; 2+ messages in thread
From: Jiri Pirko @ 2011-11-21 22:05 UTC (permalink / raw)
  To: Josh Boyer
  Cc: Jesse Brandeburg, Jeff Kirsher, netdev, linux-kernel, kernel-team

Mon, Nov 21, 2011 at 08:28:39PM CET, jwboyer@redhat.com wrote:
>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?


Looking at the patch again, I do not see anything suspicious. Plus the
bugzilla is talking about carrupting tx packets which is really odd. One
thing I can think of is if maybe VLAN tag inserting/striping and enable
VLAN receive filtering might be needed to be enabled/disabled together.
Intel guys should be able to tell.

Thanks.

Jirka

>
>josh

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-11-21 22:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-21 19:28 e1000 vlan functionality broken in 3.1 Josh Boyer
2011-11-21 22:05 ` Jiri Pirko

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.