[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E
From: |
Al Chu |
Subject: |
Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E |
Date: |
Tue, 22 Jan 2008 15:50:46 -0800 |
On Tue, 2008-01-22 at 18:34 -0500, Chris Morgan wrote:
> On Jan 22, 2008 4:59 PM, Al Chu <address@hidden> wrote:
> > Hey Chris,
> >
> > The issue w/ ipmimonitoring is there is some bogus info being returned
> > from the BMC on your motherboard.
> >
> > > [ 0h] = sdr_version_major[ 4b]
> > > [ 0h] = sdr_version_minor[ 4b]
> > > [ 0h] = record_count[16b]
> >
> > My code, which requires version number > 0, is a bug I should fix.
> > However, the record_count == 0 is definitely a bug. I will have to
> > implement a workaround for this (as well as in the 0.6.0 code that I've
> > been working on).
> >
> > Does ipmi-sensors work for you? The code in ipmi-sensors does not check
> > the record_count ahead of time, so perhaps it'll work by being
> > blissfully unaware :-)
> >
>
> address@hidden:~# ipmi-sensors
> ipmi-udm.c: 642: ipmi_open_inband: errnum (5): 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
>
> There is a pause at "Fetching SDR repository information before the
> expression failed on that line is actually printed.
>
>
>
> If I specify more information to ipmi-sensors there is more
> interesting output but it still appears a bit funny since most of the
> values are 0:
>
> address@hidden:~# ipmi-sensors -D SSIF --driver-address=0x42
> --driver-device=/dev/i2c-0 --register-spacing=1 --debug
> Fetching SDR repository information...
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 20h] = cmd[ 8b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 0h] = cmd[ 8b]
> [ 0h] = comp_code[ 8b]
> [ 0h] = sdr_version_major[ 4b]
> [ 0h] = sdr_version_minor[ 4b]
> [ 0h] = record_count[16b]
> [ 0h] = free_space[16b]
> [ 0h] = most_recent_addition_timestamp[32b]
> [ 0h] = most_recent_erase_timestamp[32b]
> [ 0h] = get_sdr_repository_allocation_info_command_supported[
> 1b]
> [ 0h] = reserve_sdr_repository_command_supported[ 1b]
> [ 0h] = partial_add_sdr_command_supported[ 1b]
> [ 0h] = delete_sdr_command_supported[ 1b]
> [ 0h] = reserved[ 1b]
> [ 0h] =
> modal_non_modal_sdr_repository_update_operation_supported[ 2b]
> [ 0h] = overflow_flag[ 1b]
> ================================================================
> done
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 22h] = cmd[ 8b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 0h] = cmd[ 8b]
> [ 0h] = comp_code[ 8b]
> [ 0h] = reservation_id[16b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 23h] = cmd[ 8b]
> [ 0h] = reservation_id[16b]
> [ 0h] = record_id[16b]
> [ 0h] = offset_into_record[ 8b]
> [ 5h] = bytes_to_read[ 8b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 0h] = cmd[ 8b]
> [ 0h] = comp_code[ 8b]
> [ 0h] = next_record_id[16b]
> [ BYTE ARRAY ... ] = record_data[255B]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h 00h ]
> [ 00h 00h 00h 00h 00h 00h 00h ]
> ================================================================
> FAILED: Retrieval of SDR record 0x0
> SDR Cache creation failed: internal error
Whoah. Now that is really bad. All the commands seem to returning
just 0s.
Can you run bmc-info from before with --debug? That one (from your
earlier e-mail) outputted useful information.
BTW, before the end of today, I'll e-mail you a tar.gz that I believe
solves the SSIF loading problems so you don't have to type all the
address information constantly.
Al
>
>
>
> > BTW, thanks for all your help getting to the bottom of all this. Since
> > (it seems) Intel motherboards are the only ones with SSIF, a lot of this
> > stuff hasn't been flushed out.
> >
>
> It's really no trouble, I appreciate your help. I wish I had more time
> to be able to look at the code and try to see what might be going on.
>
> Chris
--
Albert Chu
address@hidden
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, (continued)
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Bala.A, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E,
Al Chu <=
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/22
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/23
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/23
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/23
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Chris Morgan, 2008/01/23
- Re: [Freeipmi-users] problem with freeipmi 0.5.3 and intel SE7221BK1-E, Al Chu, 2008/01/23