| 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
| ||
|
Message-ID: <20120429071848.GA2064@nik-comp.lan>
Date: Sun, 29 Apr 2012 09:18:48 +0200
From: Nikola Ciprich <nikola.ciprich@...uxbox.cz>
To: minyard@....org
Cc: Rob Herring <rob.herring@...xeda.com>,
linux-kernel@...r.kernel.org, tcminyard@...il.com
Subject: Re: [BISECTED] SOLVED ipmi_si not loading since 2.6.39
Hi guys,
thanks for all Your help. Problem solved, I have to be very sorry about that :(
There was a boot script I wasn't aware of which we're using for setting IPMI and this
tried to load the module using
modprobe ipmi_si type=kcs ports=0xca8 regspacings=4
THIS seems to have stopped working, but I think it was just wrong all the time, and is
now not needed at all. Just loading ipmi_si now works, so the system was maybe just
getting confused when trying to load module with wrong params (I was unloading module
first, but seems like that wasn't enough).
So I'll just have this script fixed (or better removed).
I'm once again sorry for the fuss, I don't know much about how IPMI works and apparently
haven't gathered all the needed info.
Cheers!
nik
On Sat, Apr 28, 2012 at 10:34:14PM -0500, Corey Minyard wrote:
> On 04/28/2012 09:43 AM, Nikola Ciprich wrote:
>>> nothing on this address (with 3.4 kernel).
>>>
>>> on 2.6.32 I see:
>>> 0a30-0a3f : pnp 00:07
>>> 0b00-0b7f : pnp 00:0c
>>> 0ca2-0ca2 : ipmi_si
>>> 0ca3-0ca3 : ipmi_si
>>> 0cf8-0cff : PCI conf1
>>> 1180-119f : 0000:00:1f.3
>>> 1180-119f : pnp 00:0e
>>> d000-dfff : PCI Bus 0000:06
>>> d000-d01f : 0000:06:00.0
>>>
>>> on 3.4-rc4:
>>> 0a30-0a3f : pnp 00:07
>>> 0b00-0b7f : pnp 00:0c
>>> 0cf8-0cff : PCI conf1
>>> 0d00-ffff : PCI Bus 0000:00
>>> 1180-119f : 0000:00:1f.3
>>> 1180-119f : pnp 00:0e
>>> c000-cfff : PCI Bus 0000:06
>>> c000-c01f : 0000:06:00.0
>>>
>> well, I wasn't able to figure out anything special :(
>> do You guys have any idea on what more I could check?
>> I'd be very grateful for any hints..
>> thanks a lot in advance
>> nik
>
> I do not know. I just tried 3.2 and the head of the kernel tree and
> they both worked fine on my system, which is an old Intel server.
>
> I have a Supermicro system with IPMI, but it will take me a bit to get a
> working kernel there.
>
> Could you try with the module param "kcs_debug=7"? That will give me
> some idea what the state machine is doing.
>
> At this point, if I can't reproduce, I can't do much. I also don't see
> how that patch would make any difference if you hand-specify the
> parameters.
>
> -corey
>
>>
>>> I'll try comparing both kernels' dmesg output in more detail to see
>>> if there's some difference that might be important..
>>>
>>> n.
>>>
>>>
>>>
>>>
>>>> -corey
>>>>
>>>>> cheers!
>>>>> n.
>>>>>
>>>>>
>>>>>> -corey
>>>>>>
>>>>>>
>>>>>>> n.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Apr 24, 2012 at 03:55:54PM -0500, Rob Herring wrote:
>>>>>>>> On 04/24/2012 03:37 PM, Nikola Ciprich wrote:
>>>>>>>>> Hi Corey,
>>>>>>>>>
>>>>>>>>> I have this problem with 3.4-rc4 as well and it already contains
>>>>>>>>> b1608d69cb804e414d0887140ba08a9398e4e638, so this doesn't fix this problem..
>>>>>>>>>
>>>>>>>> Can you send the kernel log for the failing case.
>>>>>>>>
>>>>>>>> Rob
>>>>>>>>
>>>>>>>>> BR
>>>>>>>>>
>>>>>>>>> nik
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Apr 24, 2012 at 08:41:32AM -0500, Corey Minyard wrote:
>>>>>>>>>> Looks like you might need change b1608d69cb804e414d0887140ba08a9398e4e638
>>>>>>>>>>
>>>>>>>>>> -corey
>>>>>>>>>>
>>>>>>>>>> On 04/23/2012 03:09 PM, Rob Herring wrote:
>>>>>>>>>>> On 04/21/2012 02:20 AM, Nikola Ciprich wrote:
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> here's further information Rob and Corey requested:
>>>>>>>>>>>>
>>>>>>>>>>>> on working system:
>>>>>>>>>>>>
>>>>>>>>>>>> [root@...x4 ~]# cat /proc/ipmi/0/params
>>>>>>>>>>>> kcs,i/o,0xca2,rsp=1,rsi=1,rsh=0,irq=0,ipmb=0
>>>>>>>>>>>>
>>>>>>>>>>>> dmesg snippet:
>>>>>>>>>>>>
>>>>>>>>>>>> [ 41.759319] ipmi message handler version 39.2
>>>>>>>>>>>> [ 41.760690] ipmi device interface
>>>>>>>>>>>> [ 42.765334] IPMI System Interface driver.
>>>>>>>>>>>> [ 42.765336] ipmi_si: probing via hardcoded address
>>>>>>>>>>>> [ 42.765337] ipmi_si: Adding hardcoded-specified kcs state machine
>>>>>>>>>>>> [ 42.765340] ipmi_si: Trying hardcoded-specified kcs state machine at i/o address 0xca8, slave address 0x0, irq 0
>>>>>>>>>>>> [ 42.765344] ipmi_si: Interface detection failed
>>>>>>>>>>>> [ 42.770823] ipmi_si: probing via SMBIOS
>>>>>>>>>>>> [ 42.770834] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
>>>>>>>>>>>> [ 42.770836] ipmi_si: Adding SMBIOS-specified kcs state machine
>>>>>>>>>>>> [ 42.770838] ipmi_si: probing via SPMI
>>>>>>>>>>>> [ 42.770840] ipmi_si: SPMI: io 0xe4 regsize 1 spacing 1 irq 0
>>>>>>>>>>>> [ 42.770841] ipmi_si: Adding SPMI-specified kcs state machine
>>>>>>>>>>>> [ 42.770843] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
>>>>>>>>>>>> [ 42.798137] ipmi_si ipmi_si.0: Error clearing flags: cc
>>>>>>>>>>>> [ 42.801011] ipmi_si ipmi_si.0: Found new BMC (man_id: 0x002a7c, prod_id: 0x0624, dev_id: 0x20)
>>>>>>>>>>>> [ 42.801068] ipmi_si ipmi_si.0: IPMI kcs interface initialized
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> dmidecode:
>>>>>>>>>>>>
>>>>>>>>>>>> IPMI Device Information
>>>>>>>>>>>> Interface Type: KCS (Keyboard Control Style)
>>>>>>>>>>>> Specification Version: 2.0
>>>>>>>>>>>> I2C Slave Address: 0x00
>>>>>>>>>>>> NV Storage Device: Not Present
>>>>>>>>>>>> Base Address: 0x0000000000000CA2 (I/O)
>>>>>>>>>>>> Register Spacing: Successive Byte Boundaries
>>>>>>>>>>>>
>>>>>>>>>>>> Base Board Information
>>>>>>>>>>>> Manufacturer: Supermicro
>>>>>>>>>>>> Product Name: X9SCL/X9SCM
>>>>>>>>>>>>
>>>>>>>>>>>> (but we're experiencing this on various supermicro bords, ie X8DTL)
>>>>>>>>>>>>
>>>>>>>>>>>> Tried setting parameters by hand didn't help:
>>>>>>>>>>>>
>>>>>>>>>>>> modprobe ipmi_si type=kcs addrs=0xca8 regspacings=1 regsizes=1 regshifts=0 irqs=0 slave_addrs=0x0
>>>>>>>>>>>>
>>>>>>>>>>>> (not sure whether I got them correct though, and values mostly seem to me to be defaults anyways..)
>>>>>>>>>>>>
>>>>>>>>>>> It is working for me on a SuperMicro system with ubuntu oneiric (3.0
>>>>>>>>>>> based).
>>>>>>>>>>>
>>>>>>>>>>> [597160.259728] ipmi_si: probing via SMBIOS
>>>>>>>>>>> [597160.259730] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
>>>>>>>>>>> [597160.259731] ipmi_si: Adding SMBIOS-specified kcs state machine
>>>>>>>>>>> [597160.259734] ipmi_si: probing via SPMI
>>>>>>>>>>> [597160.259735] ipmi_si: SPMI: io 0xe4 regsize 1 spacing 1 irq 0
>>>>>>>>>>> [597160.259737] ipmi_si: Adding SPMI-specified kcs state machine
>>>>>>>>>>> [597160.259739] ipmi_si: Trying SMBIOS-specified kcs state machine at
>>>>>>>>>>> i/o address 0xca2, slave address 0x0, irq 0
>>>>>>>>>>> [597160.378757] ipmi_si: Invalid return from get global enables command,
>>>>>>>>>>> cannot enable the event buffer.
>>>>>>>>>>> [597160.382032] ipmi_si ipmi_si.0: Found new BMC (man_id: 0x00b980,
>>>>>>>>>>> prod_id: 0x0624, dev_id: 0x20)
>>>>>>>>>>> [597160.382040] ipmi_si ipmi_si.0: IPMI kcs interface initialized
>>>>>>>>>>> [597179.973960] ipmi device interface
>>>>>>>>>>> localadm@...dy1:~$ ipmitool bmc info
>>>>>>>>>>> Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
>>>>>>>>>>> such file or directory
>>>>>>>>>>> Get Device ID command failed
>>>>>>>>>>> localadm@...dy1:~$ sudo ipmitool bmc info
>>>>>>>>>>> Device ID : 32
>>>>>>>>>>> Device Revision : 1
>>>>>>>>>>> Firmware Revision : 1.1
>>>>>>>>>>> IPMI Version : 2.0
>>>>>>>>>>> Manufacturer ID : 47488
>>>>>>>>>>> Manufacturer Name : Unknown (0xB980)
>>>>>>>>>>> Product ID : 1572 (0x0624)
>>>>>>>>>>> Product Name : Unknown (0x624)
>>>>>>>>>>> Device Available : yes
>>>>>>>>>>> Provides Device SDRs : no
>>>>>>>>>>> Additional Device Support :
>>>>>>>>>>> Sensor Device
>>>>>>>>>>> SDR Repository Device
>>>>>>>>>>> SEL Device
>>>>>>>>>>> FRU Inventory Device
>>>>>>>>>>> IPMB Event Receiver
>>>>>>>>>>> IPMB Event Generator
>>>>>>>>>>> Chassis Device
>>>>>>>>>>> Aux Firmware Rev Info :
>>>>>>>>>>> 0x06
>>>>>>>>>>> 0x00
>>>>>>>>>>> 0x00
>>>>>>>>>>> 0x00
>>>>>>>>>>> localadm@...dy1:~$ uname -a
>>>>>>>>>>> Linux sandy1 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC
>>>>>>>>>>> 2012 x86_64 x86_64 x86_64 GNU/Linux
>>>>>>>>>>>
>>>>>>>>>>> Rob
>>>>>>>>>>>
>>>>>>>>>>>> nik
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Apr 21, 2012 at 12:38:33AM +0200, 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?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks in advance!
>>>>>>>>>>>>>
>>>>>>>>>>>>> with best regards
>>>>>>>>>>>>>
>>>>>>>>>>>>> nik
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> -------------------------------------
>>>>>>>>>>>>> Ing. Nikola CIPRICH
>>>>>>>>>>>>> LinuxBox.cz, s.r.o.
>>>>>>>>>>>>> 28. rijna 168, 709 01 Ostrava
>>>>>>>>>>>>>
>>>>>>>>>>>>> tel.: +420 596 603 142
>>>>>>>>>>>>> fax: +420 596 621 273
>>>>>>>>>>>>> mobil: +420 777 093 799
>>>>>>>>>>>>>
>>>>>>>>>>>>> www.linuxbox.cz
>>>>>>>>>>>>>
>>>>>>>>>>>>> mobil servis: +420 737 238 656
>>>>>>>>>>>>> email servis: servis@...uxbox.cz
>>>>>>>>>>>>> -------------------------------------
>>>>>>>>>>> --
>>>>>>>>>>> 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/
>>> --
>>> -------------------------------------
>>> Ing. Nikola CIPRICH
>>> LinuxBox.cz, s.r.o.
>>> 28. rijna 168, 709 01 Ostrava
>>>
>>> tel.: +420 596 603 142
>>> fax: +420 596 621 273
>>> mobil: +420 777 093 799
>>>
>>> www.linuxbox.cz
>>>
>>> mobil servis: +420 737 238 656
>>> email servis: servis@...uxbox.cz
>>> -------------------------------------
>>
>>
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@...uxbox.cz
-------------------------------------
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists