mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steffen Grunewald <Steffen.Grunewald@aei.mpg.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: htejun@gmail.com, tj@kernel.org,
	Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Subject: Need assistance fixing a tg3 driver side-effect on IPMI
Date: Wed, 7 Nov 2012 09:28:20 +0100	[thread overview]
Message-ID: <20121107082820.GP30936@casco.aei.mpg.de> (raw)

Hi everyone,

I've been running into a problem while installing Debian Wheezy on a bunch
of 6-year old machines which have been running Squeeze happily for years.

They are SuperMicro-based (H8SSL opteron board), with two BCM95704A6 (Tigon3) 
interfaces, and a BMC/IPMI card (SuperMicro 1U) which shares eth0.

With a 2.6.32 kernel (and the 3.102 version of the tg3 driver) everything is fine.

With Debian's 3.2 (and tg3 3.121) I lose access to the IPMI LAN (or LANplus)
interface as soon as the tg3 module has been loaded. Even shutting down doesn't
give the interface back - I've got to pull the power plug.

Trying to git bisect the corresponding changes to the tg3 driver, I'm running
against a wall at the point where the source code has been moved to another
subtree back in 2011 (still a long time past Squeeze). I appear to be unable
to go back beyond that.

Can you advise how to find out when IPMI access got lost, and how to re-enable
it? Any suggestion is appreciated.
I suppose it wouldn't be as easy as "get the old source from 2.6.32, and plug
it into drivers/net/ethernet/broadcom, then rebuild the kernel" -?

Please keep me on CC, thanks.

Regards,
 Steffen

             reply	other threads:[~2012-11-07  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  8:28 Steffen Grunewald [this message]
2012-11-07  9:40 ` 王金浦
2012-11-12 15:29   ` Steffen Grunewald

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=20121107082820.GP30936@casco.aei.mpg.de \
    --to=steffen.grunewald@aei.mpg.de \
    --cc=carsten.aulbert@aei.mpg.de \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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

all inboxes | Powered by JetHome®