From: Corey Minyard <tcminyard@gmail.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: linux-kernel@vger.kernel.org, rob.herring@calxeda.com
Subject: Re: [BISECTED] ipmi_si not loading since 2.6.39
Date: Fri, 20 Apr 2012 19:34:36 -0500 [thread overview]
Message-ID: <4F92009C.9030301@acm.org> (raw)
In-Reply-To: <20120420223833.GA7855@nik-comp.lan>
On 04/20/2012 05:38 PM, Nikola Ciprich wrote:
> Hello,
>
> I was trying to find out why IPMI stopped working on new kernels. Since 2.6.39
> module loading ends with following message:
>
> ipmi_si: Interface detection failed
>
> Then ipmitool is unable to control IPMI device.
>
> Works for 2.6.38, doesn't work for 2.6.39, 3.0.28, 3.4-rc1.
>
> I got this bisected to following commit:
>
> commit a1e9c9dd3383e6a1a762464ad604b1081774dbda
> Author: Rob Herring<rob.herring@calxeda.com>
> Date: Wed Feb 23 15:37:59 2011 -0600
>
> ipmi: convert OF driver to platform driver
>
> of_bus is deprecated in favor of the plain platform bus. This patch
> merges the ipmi OF driver with the existing platform driver.
>
> CONFIG_PPC_OF occurrances are removed or replaced with CONFIG_OF.
>
> Compile tested with and without CONFIG_OF. Tested OF probe and
> default probe cases.
>
> Signed-off-by: Rob Herring<rob.herring@calxeda.com>
> Signed-off-by: Grant Likely<grant.likely@secretlab.ca>
>
> I wonder whether this is a bug, or I'm doing something wrong?
If it used to work and now it doesn't, that's probably a bug, though you
might be able to work around it with some direct settings.
What hardware is involved? 'cat /proc/ipmi/0/params' on a working
kernel would be handy. You can use that information to hot-add the BMC,
that should be documented in Documentation/IPMI.txt
-corey
next prev parent reply other threads:[~2012-04-21 0:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 22:38 [BISECTED] ipmi_si not loading since 2.6.39 Nikola Ciprich
2012-04-21 0:33 ` Rob Herring
2012-04-21 0:34 ` Corey Minyard [this message]
2012-04-21 7:20 ` Nikola Ciprich
2012-04-23 20:09 ` Rob Herring
2012-04-23 20:20 ` Nikola Ciprich
2012-04-24 13:41 ` Corey Minyard
2012-04-24 20:37 ` Nikola Ciprich
2012-04-24 20:55 ` Rob Herring
2012-04-24 21:30 ` Nikola Ciprich
2012-04-24 21:57 ` Corey Minyard
2012-04-25 4:21 ` Nikola Ciprich
2012-04-25 16:49 ` Corey Minyard
2012-04-25 17:58 ` Nikola Ciprich
2012-04-28 14:43 ` Nikola Ciprich
2012-04-29 3:34 ` Corey Minyard
2012-04-29 7:18 ` [BISECTED] SOLVED " Nikola Ciprich
2012-04-23 20:09 ` [BISECTED] " 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=4F92009C.9030301@acm.org \
--to=tcminyard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=nikola.ciprich@linuxbox.cz \
--cc=rob.herring@calxeda.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 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.