Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E

[Chris Morgan]

Hi Albert.

Replies inline.



On Jan 16, 2008 10:22 AM, Albert Chu <address@hidden> wrote:
> Hey Chris,
>
> I know a few intel boards use SSIF only, and the below does indicate SSIF
> is the inband driver.  Does ipmi-locate not find the SSIF device when it
> probes via dmi?
>

I think it does use SSIF and I think ipmi-locate finds it. I listed
the output from ipmi-locate in my first mail and I think it listed a
SSIF device at the end of the output.



> Could you try giving ipmi-sensors the -D SSIF option to tell it to use
> SSIF.  I don't know too much about SSIF, so more advanced stuff I've CCed
> the fellow who wrote the SSIF driver.
>


It seems to want more information:
~$ sudo ipmi-sensors -D SSIF
ipmi-udm.c: 510: ipmi_open_inband: errnum (27): expression failed
ipmi-udm.c: 808: ipmi_close_device: errnum (15): expression failed
ipmi_open_inband: driver path required


I've tried providing the driver path using the information from
ipmi-locate but that didn't seem to work properly either.







> If the FreeIPMI SSIF driver doesn't work, one alternative you can do is to
> use the linux kernel ipmi driver, which FreeIPMI can also read/write off
> of.
> The mini-script I use to load it is:
>
> /sbin/modprobe ipmi_devintf
> maj=`cat /proc/devices | awk '/ipmidev/{print $1}'`
> if [ -c /dev/ipmi0 ]
> then
>    rm -f /dev/ipmi0
>    /bin/mknod /dev/ipmi0 c $maj 0
> else
>    /bin/mknod /dev/ipmi0 c $maj 0
> fi
> /sbin/modprobe ipmi_si
>
> Al
>

I actually tried for a while using the kernel ipmi and openipmi before
I switched over to freeipmi. I see:

[  969.276186] ipmi message handler version 39.1
[  969.278319] ipmi device interface
[ 1011.466147] IPMI System Interface driver.
[ 1011.523848] ipmi_si: Unable to find any System Interface(s)

in dmesg after trying to load the ipmi_si driver.


>
> > I'm having trouble reading ipmi data with freeipmi and this particular
> > intel board. Running ubuntu gutsy, 2.6.22.
> >
> > dmidecode outputs:
> > ...
> >
> > Handle 0x0030, DMI type 38, 18 bytes
> > IPMI Device Information
> >         Interface Type: SSIF (SMBus System Interface)
> >         Specification Version: 1.5
> >         I2C Slave Address: 0x42
> >         NV Storage Device Address: 0
> >         Base Address: 0x42 (SMBus)
> >
> > Handle 0x0031, DMI type 127, 4 bytes
> > End Of Table
> >
> >
> >
> > ipmi-locate has entries like:
> > ...
> > KCS device default values:
> > IPMI Version: 1.5
> > IPMI locate driver: DEFAULT
> > IPMI interface: KCS
> > BMC driver device:
> > BMC I/O base address: CA2
> > Register spacing: 1
> >
> > SMIC device default values:
> > IPMI Version: 1.5
> > IPMI locate driver: DEFAULT
> > IPMI interface: SMIC
> > BMC driver device:
> > BMC I/O base address: CA9
> > Register spacing: 1
> >
> > BT device default values:
> > ipmi-locate-defaults.c: 49: ipmi_locate_defaults_get_dev_info: errno
> > (22): expression failed
> >
> > SSIF device default values:
> > IPMI Version: 1.5
> > IPMI locate driver: DEFAULT
> > IPMI interface: SSIF
> > BMC driver device: /dev/i2c-0
> > BMC SMBUS slave address: 42
> > Register spacing: 1
> >
> >
> > But when I try to actually read via ipmi-sensors I get:
> > ~/freeipmi-0.5.3$ sudo ipmi-sensors
> > ipmi-openipmi-api.c: 319: ipmi_openipmi_ctx_io_init: errno (22):
> > expression failed
> > ipmi-udm.c: 642: ipmi_open_inband: errnum (8): expression failed
> > ipmi-locate-smbios.c: 385: ipmi_locate_smbios_get_dev_info: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 918: ipmi_acpi_get_table: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 839: ipmi_acpi_get_rsdp: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 1034: ipmi_acpi_get_firmware_table: errno
> > (9): expression failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 918: ipmi_acpi_get_table: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 839: ipmi_acpi_get_rsdp: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 1034: ipmi_acpi_get_firmware_table: errno
> > (9): expression failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 918: ipmi_acpi_get_table: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 839: ipmi_acpi_get_rsdp: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 1034: ipmi_acpi_get_firmware_table: errno
> > (9): expression failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 918: ipmi_acpi_get_table: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 839: ipmi_acpi_get_rsdp: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 1034: ipmi_acpi_get_firmware_table: errno
> > (9): expression failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 918: ipmi_acpi_get_table: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 681: ipmi_ioremap: errno (9): expression failed
> > ipmi-locate-acpi-spmi.c: 720: ipmi_get_physical_mem_data: errno (9):
> > expression failed
> > ipmi-locate-acpi-spmi.c: 839: ipmi_acpi_get_rsdp: errno (9): expression
> > failed
> > ipmi-locate-acpi-spmi.c: 1034: ipmi_acpi_get_firmware_table: errno
> > (9): expression failed
> > ipmi-locate-acpi-spmi.c: 1239: ipmi_locate_acpi_spmi_get_dev_info:
> > errno (9): expression failed
> > Fetching SDR repository information... ipmi-kcs-api.c: 662:
> > ipmi_kcs_write: errno (2): expression failed
> > ipmi-kcs-api-udm.c: 74: ipmi_kcs_cmd_udm: errnum (10): expression failed
> > SDR Cache creation failed: ipmi communication error
> >
> >
> > I enabled the tracing and debug options after reading a few other
> > emails of users with similar issues.
> >
> > I'd really like to get ipmi working on these servers so we can
> > retrieve more details about the current hardware status. Does anyone
> > have an idea what might be going wrong here?
> >
> > Chris
> >
> >
> > _______________________________________________
> > Freeipmi-users mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/freeipmi-users
> >
>
>
> --
> Albert Chu
> address@hidden
> 925-422-5311
> Computer Scientist
> High Performance Systems Division
> Lawrence Livermore National Laboratory
>
>
>
> _______________________________________________
> Freeipmi-users mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/freeipmi-users
>