[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.WNT.2.00.1007260936160.4488@jbrandeb-desk1.amr.corp.intel.com>
Date: Mon, 26 Jul 2010 09:45:06 -0700 (Pacific Daylight Time)
From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To: Andrey Panin <pazke@...trinvest.ru>
cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
"Ronciak, John" <john.ronciak@...el.com>
Subject: Re: Problem with e1000e, 802.1Q VLAN's and IPMI
On Mon, 26 Jul 2010, Andrey Panin wrote:
> I have a problem using IPMI on Super Micro X7SBL motherboard (AOC-IPMI20-E BMC).
> BMC shares ethernet port with onboard e1000e. It works when IPMI traffic is
> untagged (CrcStripping=0 module option used), but if I try to use 802.1Q vlan
> for IPMI traffic BMC stops responding right after "ifup eth0".
We've heard of this issue (or similar) before. I believe for the other
guys they had to run IPMI traffic untagged, if your main network is
running untagged. The problem in this case is that the tags are being
stripped in hardware even for the SMBUS packets, at which point the BMC
that is stupid and doesn't understand offloading hardware gets confused
that the traffic it is receiving doesn't have a vlan tag.
> I tested 2.6.26 (debian stable kernel) and 2.6.35-rc6.
> Looks like there is some problem with 802.1Q tags stripping/inserting.
Thanks for testing the latest kernel.
> There was no such problem with e1000 driver from 2.6.18.
Hm, that is an interesting statement. The major changes to the driver
include stripping tags all the time when not in promisc mode, and there
have been some fixes and attempts to fix the ipmi issues some
(particularly supermicro) BMCs have. I'm quite surprised it worked for
you at all (there have been quite a few issues in this area)
> Unfortunately I can't provide additional info right now, but I can provide
> it slightly later and I'm ready to test patches.
I can send you a patch to disable vlan stripping in hardware which will
probably get you working, but I don't think it is production worthy.
Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists