From: "Andrey Panin" <pazke@centrinvest.ru>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: Problem with e1000e, 802.1Q VLAN's and IPMI
Date: Fri, 30 Jul 2010 11:00:11 +0400 [thread overview]
Message-ID: <20100730070011.GA29453@centrinvest.ru> (raw)
In-Reply-To: <20100727120552.GA31741@centrinvest.ru>
On 208, 07 27, 2010 at 04:05:52 +0400, Andrey Panin wrote:
> On 207, 07 26, 2010 at 09:45:06AM -0700, Brandeburg, Jesse wrote:
> >
> > 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 suspected something like that. Unfortunately Super Micro isn't interested
> in fixing their BMC, at least latest firmware doesn't fix the issue.
>
> > > 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)
>
> After some sleep I'm not so sure that it was really working :(
> I'll retest it more thoroughly this evening.
After retest I can confirm that tagged IPMI works with 2.6.18 e1000 driver.
prev parent reply other threads:[~2010-07-30 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 7:39 Andrey Panin
2010-07-26 16:45 ` Brandeburg, Jesse
2010-07-27 12:05 ` Andrey Panin
2010-07-30 7:00 ` Andrey Panin [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=20100730070011.GA29453@centrinvest.ru \
--to=pazke@centrinvest.ru \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/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
Powered by JetHome