From: Bernd Schubert <bs@q-leap.de>
To: Nikola Ciprich <extmaillist@linuxbox.cz>,
Jesse <jesse.brandeburg@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-netdev@vger.kernel.org
Subject: Re: [regression?] e1000e breaks IPMI
Date: Wed, 18 Jun 2008 11:58:34 +0200 [thread overview]
Message-ID: <200806181158.34412.bs@q-leap.de> (raw)
> I hate working around this broken BMC (again) when others are known to
> work just fine, and CRC stripping in hardware really simplifies our
> receive path.
Due to rather bad experiences I'm always alarmed about IPMI problems (actually
so far not with supermicro, but with other vendors). So I contacted
supermicro and immediately got an answer they have a new LAP EEPROM to fix
this problem.
So the problem with supermicro is solved, lets see what the other vendor, I
also contacted, says.
--
Bernd Schubert
Q-Leap Networks GmbH
next reply other threads:[~2008-06-18 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 9:58 Bernd Schubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 21:16 [regression?] e1000e breaks IPMI Nikola Ciprich
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=200806181158.34412.bs@q-leap.de \
--to=bs@q-leap.de \
--cc=extmaillist@linuxbox.cz \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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