[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 16:15:24 -0800 |
Hey Chris,
Could you try a few other commands too so we can get an idea what is
working/not working so far.
> bmc-config --list
> pef-config --list
> ipmi-chassis -c
> ipmi-chassis -s
Al
On Tue, 2008-01-22 at 19:01 -0500, Chris Morgan wrote:
> On Jan 22, 2008 6:50 PM, Al Chu <address@hidden> wrote:
> >
> > 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.
> >
>
>
>
> Sure, I think this is the bmc-info you were asking for. It does
> produce a lot more nicely formatted output with the --debug option.
>
> address@hidden:~# bmc-info --no-probing -D SSIF --driver-address=0x42
> --driver-device=/dev/i2c-0 --register-spacing=1 --debug
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 1h] = cmd[ 8b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 1h] = cmd[ 8b]
> [ 0h] = comp_code[ 8b]
> [ 20h] = device_id[ 8b]
> [ 1h] = device_revision.revision[ 4b]
> [ 0h] = device_revision.reserved1[ 3b]
> [ 1h] = device_revision.sdr_support[ 1b]
> [ 2h] = firmware_revision1.major_revision[ 7b]
> [ 0h] = firmware_revision1.device_available[ 1b]
> [ 40h] = firmware_revision2.minor_revision[ 8b]
> [ 1h] = ipmi_version.ms_bits[ 4b]
> [ 5h] = ipmi_version.ls_bits[ 4b]
> [ 1h] = additional_device_support.sensor_device[ 1b]
> [ 1h] = additional_device_support.sdr_repository_device[ 1b]
> [ 1h] = additional_device_support.sel_device[ 1b]
> [ 1h] = additional_device_support.fru_inventory_device[ 1b]
> [ 1h] = additional_device_support.ipmb_event_receiver[ 1b]
> [ 0h] = additional_device_support.ipmb_event_generator[ 1b]
> [ 0h] = additional_device_support.bridge[ 1b]
> [ 1h] = additional_device_support.chassis_device[ 1b]
> [ 157h] = manufacturer_id.id[20b]
> [ 0h] = manufacturer_id.reserved1[ 4b]
> [ 4311h] = product_id[16b]
> ================================================================
> Device ID: 20
> Device Revision: 1
> [SDR Support]
> Firmware Revision: 2.64
> [Device Available (normal operation)]
> IPMI Version: 1.5
> Additional Device Support:
> [Sensor Device]
> [SDR Repository Device]
> [SEL Device]
> [FRU Inventory Device]
> [IPMB Event Receiver]
> [Chassis Device]
> Manufacturer ID: 157h
> Product ID: 4311h
> Aux Firmware Revision Info: Boot Code v00. 0, PIA v00. 0
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 0h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ C9h] = comp_code[ 8b]
> ================================================================
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi-messaging-support-cmds-udm.c: 383: ipmi_cmd_get_channel_info:
> errmsg = Parameter out of range. One or more parameters in the data
> field of the Request are out of range. This is different from
> 'Invalid data field' (CCh) code in that it indicates that the
> erroneous field(s) has a contiguous range of possible values.
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 1h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 0h] = comp_code[ 8b]
> [ 1h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ 4h] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 1h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 0h] = active_session_count[ 6b]
> [ 2h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 2h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 0h] = comp_code[ 8b]
> [ 2h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ Ch] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 4h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 1h] = active_session_count[ 6b]
> [ 0h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 3h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ C9h] = comp_code[ 8b]
> [ 2h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ Ch] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 4h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 1h] = active_session_count[ 6b]
> [ 0h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi-messaging-support-cmds-udm.c: 383: ipmi_cmd_get_channel_info:
> errmsg = Parameter out of range. One or more parameters in the data
> field of the Request are out of range. This is different from
> 'Invalid data field' (CCh) code in that it indicates that the
> erroneous field(s) has a contiguous range of possible values.
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 4h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ C9h] = comp_code[ 8b]
> [ 2h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ Ch] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 4h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 1h] = active_session_count[ 6b]
> [ 0h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi-messaging-support-cmds-udm.c: 383: ipmi_cmd_get_channel_info:
> errmsg = Parameter out of range. One or more parameters in the data
> field of the Request are out of range. This is different from
> 'Invalid data field' (CCh) code in that it indicates that the
> erroneous field(s) has a contiguous range of possible values.
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 5h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ C9h] = comp_code[ 8b]
> [ 2h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ Ch] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 4h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 1h] = active_session_count[ 6b]
> [ 0h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi-messaging-support-cmds-udm.c: 383: ipmi_cmd_get_channel_info:
> errmsg = Parameter out of range. One or more parameters in the data
> field of the Request are out of range. This is different from
> 'Invalid data field' (CCh) code in that it indicates that the
> erroneous field(s) has a contiguous range of possible values.
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 6h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ C9h] = comp_code[ 8b]
> [ 2h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ Ch] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 4h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 1h] = active_session_count[ 6b]
> [ 0h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi-messaging-support-cmds-udm.c: 383: ipmi_cmd_get_channel_info:
> errmsg = Parameter out of range. One or more parameters in the data
> field of the Request are out of range. This is different from
> 'Invalid data field' (CCh) code in that it indicates that the
> erroneous field(s) has a contiguous range of possible values.
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ 7h] = channel_number[ 4b]
> [ 0h] = reserved[ 4b]
> ================================================================
> ================================================================
> [ VALUE TAG NAME:LENGTH ]
> ================================================================
> [ 42h] = cmd[ 8b]
> [ C9h] = comp_code[ 8b]
> [ 2h] = actual_channel_number[ 4b]
> [ 0h] = actual_channel_number.reserved[ 4b]
> [ Ch] = channel_medium_type[ 7b]
> [ 0h] = channel_medium_type.reserved[ 1b]
> [ 4h] = channel_protocol_type[ 5b]
> [ 0h] = channel_protocol_type.reserved[ 3b]
> [ 1h] = active_session_count[ 6b]
> [ 0h] = session_support[ 2b]
> [ 157h] = vendor_id[24b]
> [ 0h] = auxiliary_channel_info[16b]
> ================================================================
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi_check_completion_code: completion code invalid: c9
> ipmi-messaging-support-cmds-udm.c: 383: ipmi_cmd_get_channel_info:
> errmsg = Parameter out of range. One or more parameters in the data
> field of the Request are out of range. This is different from
> 'Invalid data field' (CCh) code in that it indicates that the
> erroneous field(s) has a contiguous range of possible values.
> Channel Information:
> Channel No: 1
> Medium Type: 802.3 LAN
> Protocol Type: IPMB-1.0
> Channel No: 2
> Medium Type: System Interface (KCS, SMIC, or BT)
> Protocol Type: IPMI-SMBus
> address@hidden:~#
>
> 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, 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, 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/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
- 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