All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Ronciak, John" <john.ronciak@intel.com>,
	Henning Fehrmann <henning.fehrmann@aei.mpg.de>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Allan, Bruce W" <bruce.w.allan@intel.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Subject: Re: loosing IPMI-card by loading netconsole
Date: Fri, 14 May 2010 12:37:33 -0500	[thread overview]
Message-ID: <1273858653.15067.1335.camel@calx> (raw)
In-Reply-To: <4BED79EB.1000204@kernel.org>

On Fri, 2010-05-14 at 18:27 +0200, Tejun Heo wrote:
> Hello, John.
> 
> As Henning seems offline, I'll try to fill in.
> 
> On 05/14/2010 04:51 PM, Ronciak, John wrote:
> > Sorry to hear about the problem you are having Henning.  What do you
> > mean when you say "it disappears"?
> 
> It stops responding to IPMI requests.
> 
> > Can both eth0 and eth1 ping (or be pinged)?  Do all the networking
> > devices still show up in the system when you do an 'lspci'?
> 
> Yeah, everything other than IPMI works just fine.
> 
> > What happens if you down and then up the interface you are having
> > problems with?  Does 'rmmod' do the same thing as your removal
> > method?
> 
> Haven't tried these but well I think rmmoding should achieve about the
> same thing.
> 
> > Is there anything in the system logs saying anything about the
> > interfaces?
> 
> Nope.
> 
> > We have not had reports of this so this is a bit unusual.  Please let us know.
> > 
> > Does this happen on other systems as well or just one particular system?
> 
> Yeah, it happens on at least several hundred machines, so not an
> isolated hardware issue at all.
> 
> To sum up.
> 
> On 2.6.27.39, netconsole + IPMI works fine.  On 2.6.32.7, as soon as
> netconsole is loaded, IPMI stops working.  Unloading netconsole
> doesn't revive IPMI but detaching the driver from the controller does.
> In both cases, usual networking works fine.

Looks like a job for bisect.

-- 
Mathematics is the supreme nostalgia of our time.



  parent reply	other threads:[~2010-05-14 17:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 13:45 loosing IPMI-card by loading netconsole Henning Fehrmann
2010-05-14 14:51 ` Ronciak, John
2010-05-14 16:27   ` Tejun Heo
2010-05-14 16:39     ` Ronciak, John
2010-05-14 17:20     ` "Brandeburg, Jesse"
2010-05-14 22:18       ` Tejun Heo
2010-05-15  8:26       ` Carsten Aulbert
2010-05-15  9:10         ` Tejun Heo
2010-05-15  9:36           ` Carsten Aulbert
2010-05-14 17:37     ` Matt Mackall [this message]
2010-05-14 22:11       ` Tejun Heo
2010-05-14 22:16         ` Matt Mackall
2010-05-14 22:24           ` Tejun Heo
2010-05-18 13:12             ` Henning Fehrmann
2010-05-20 10:16               ` Henning Fehrmann
2010-05-20 15:01                 ` Allan, Bruce W

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=1273858653.15067.1335.camel@calx \
    --to=mpm@selenic.com \
    --cc=bruce.w.allan@intel.com \
    --cc=carsten.aulbert@aei.mpg.de \
    --cc=henning.fehrmann@aei.mpg.de \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --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 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.