lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 20 Apr 2012 19:34:36 -0500
From:	Corey Minyard <tcminyard@...il.com>
To:	Nikola Ciprich <nikola.ciprich@...uxbox.cz>
CC:	linux-kernel@...r.kernel.org, rob.herring@...xeda.com
Subject: Re: [BISECTED] ipmi_si not loading since 2.6.39

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@...xeda.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@...xeda.com>
>      Signed-off-by: Grant Likely<grant.likely@...retlab.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ