netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henning Fehrmann <henning.fehrmann@aei.mpg.de>
To: Tejun Heo <tj@kernel.org>
Cc: "Ronciak, John" <john.ronciak@intel.com>,
	"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: Thu, 20 May 2010 10:16:01 +0000	[thread overview]
Message-ID: <20100520101601.GA26235@localhost> (raw)
In-Reply-To: <20100518131216.GA24750@localhost>



Hello,
> 
> 
> Let me re-describe the symptoms.
> I am not loading any ipmi related modules and not the netconsole
> module.
> When booting out current 2.6.32 kernel we can not access the IPMI
> remotely.
> 
> We had one case where the IPMI card was accessible while using this
> kernel but probably due to the fact that eth0 was removed. We do not
> consider this case anymore. 
> 
> This problem does not occur when using an older kernel. 
> 
> It has likely nothing to do with netconsole.
> 
> Here is the bisecting result:
> 
> The sha1 sum of the first bad commit is: 
> 6e50912a442947d5fafd296ca6fdcbeb36b163ff
> 
> Hence, the last good commit has:
> b2f8f7525c8aa1fdd8ad8c72c832dfb571d5f768

I 'reverse patched' the changes: 

diff --git a/drivers/net/e1000e/param.c b/drivers/net/e1000e/param.c
index e909f96..1342e0b 100644
--- a/drivers/net/e1000e/param.c
+++ b/drivers/net/e1000e/param.c
@@ -427,6 +427,8 @@ void __devinit e1000e_check_options(struct e1000_adapter *adapter)
                        e1000_validate_option(&crc_stripping, &opt, adapter);
                        if (crc_stripping == OPTION_ENABLED)
                                adapter->flags2 |= FLAG2_CRC_STRIPPING;
+               } else {
+                       adapter->flags2 |= FLAG2_CRC_STRIPPING;
                }
        }
        { /* Kumeran Lock Loss Workaround */


and compiled the kernel. This kernel works and the IPMI card is remotely accessible. 

Can we savely remove this two lines or are we running into other problems?

Cheers,
Henning

  reply	other threads:[~2010-05-20 10:16 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
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 [this message]
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=20100520101601.GA26235@localhost \
    --to=henning.fehrmann@aei.mpg.de \
    --cc=bruce.w.allan@intel.com \
    --cc=carsten.aulbert@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).