On Tue, 2008-01-22 at 11:24 -0800, Al Chu wrote: > Hey Chris, > > It looks like you can communicate w/ the BMC now, which is good. So we > need to figure out why the the SSIF driver is not working by default. > That's bug #1. I have a few ideas about it, hopefully I can deal with > that later.
Hey Chris, One more question, if you do only > bmc-info -D SSIF does it work? It would indicate the the SSIF probing works. We are just not selecting the initial driver correctly. Thanks, Al > > [EMAIL PROTECTED]:~# ipmimonitoring --no-probing -D SSIF > > --driver-address=0x42 --driver-device=/dev/i2c-0 > > --register-spacing=1 > > ipmi_monitoring_sensor_readings_by_record_id: internal error > > This a more major concern. Could you run w/ --debug and see if there is > any extra info it outputs. > > Thanks, > Al > > On Tue, 2008-01-22 at 12:15 -0500, Chris Morgan wrote: > > [EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF --driver-address=0x42 > > --driver-device=/dev/i2c-0 --register-spacing=1 > > 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 > > 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. > > 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. > > 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. > > 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. > > 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. > > 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 > > [EMAIL PROTECTED]:~# > > > > > > [EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF --driver-address=0x84 > > --driver-device=/dev/i2c-0 --register-spacing=1 > > ipmi-ssif-api.c: 548: ipmi_ssif_ctx_io_init: errno (22): expression failed > > ipmi-udm.c: 627: ipmi_open_inband: errnum (10): expression failed > > ipmi-udm.c: 808: ipmi_close_device: errnum (15): expression failed > > ipmi_open_inband: internal error > > [EMAIL PROTECTED]:~# > > > > So the device at 0x42 worked, 0x84 didn't. > > > > > > > > [EMAIL PROTECTED]:~# ipmi-sensors --no-probing -D SSIF --driver-address=0x42 > > --driver-device=/dev/i2c-0 --register-spacing=1 -i > > SDR version: 0.0 > > SDR record count: 0 > > Free space remaining: 0 bytes > > Most recent addition timestamp: 12/31/1969 - 19:00:00 > > Most recent erase timestamp: 12/31/1969 - 19:00:00 > > Get SDR Repository Allocation Information Command supported: No > > Reserve SDR Repository Command supported: No > > Partial Add SDR Command supported: No > > Delete SDR Command supported: No > > Modal/non-modal SDR Repository Update operation supported: > > Unspecified > > SDR could not be written due to lack of space in the SDR Repository: No > > > > [EMAIL PROTECTED]:~# ipmimonitoring --no-probing -D SSIF > > --driver-address=0x42 --driver-device=/dev/i2c-0 > > --register-spacing=1 > > ipmi_monitoring_sensor_readings_by_record_id: internal error > > > > > > I'm not sure how to get fan information out now. it still appears that > > something may not be working properly due to protocol issues with this > > particular server model. > > > > Chris > > > > > > > > > > On Jan 22, 2008 2:18 AM, Bala.A <[EMAIL PROTECTED]> wrote: > > > > > > I found that base of number should be specified in --driver-address value. > > > > > > Please try the following commands > > > > > > bmc-info --no-probing -D SSIF --driver-address=0x42 \ > > > --driver-device=/dev/i2c-0 --register-spacing=1 > > > > > > bmc-info --no-probing -D SSIF --driver-address=0x84 \ > > > --driver-device=/dev/i2c-0 --register-spacing=1 > > > > > > I hope this will work. > > > > > > Thanks, > > > > > > > > > Regards, > > > Bala > > > --- > > > Free as in freedom > > > http://www.gnu.org/ > > > > > > > > > > Here is the entire output from dmidecode, aplogizes because its a lot > > > > of text but I wanted the entire output here for reference. > > > > > > > > # dmidecode 2.9 > > > > SMBIOS 2.3 present. > > > > 50 structures occupying 2332 bytes. > > > > Table at 0x000FCFD0. > > > > > > > > Handle 0x0000, DMI type 0, 20 bytes > > > > BIOS Information > > > > Vendor: Intel Corporation > > > > Version: SE7221BK1E.86B.P.08.00.0034.063020060918 > > > > Release Date: 06/30/2006 > > > > Address: 0xF0000 > > > > Runtime Size: 64 kB > > > > ROM Size: 2048 kB > > > > Characteristics: > > > > ISA is supported > > > > PCI is supported > > > > PNP is supported > > > > BIOS is upgradeable > > > > BIOS shadowing is allowed > > > > ESCD support is available > > > > Boot from CD is supported > > > > Selectable boot is supported > > > > BIOS ROM is socketed > > > > EDD is supported > > > > Print screen service is supported (int 5h) > > > > 8042 keyboard services are supported (int 9h) > > > > Serial services are supported (int 14h) > > > > CGA/mono video services are supported (int 10h) > > > > ACPI is supported > > > > USB legacy is supported > > > > LS-120 boot is supported > > > > ATAPI Zip drive boot is supported > > > > BIOS boot specification is supported > > > > Function key-initiated network boot is supported > > > > > > > > Handle 0x0001, DMI type 1, 25 bytes > > > > System Information > > > > Manufacturer: Intel > > > > Product Name: > > > > Version: > > > > Serial Number: > > > > UUID: 57B8F269-3E78-0010-80D8-000E0C4B1C84 > > > > Wake-up Type: Power Switch > > > > > > > > Handle 0x0002, DMI type 2, 15 bytes > > > > Base Board Information > > > > Manufacturer: Intel > > > > Product Name: SE7221BK1E > > > > Version: FRU V0.01 > > > > Serial Number: QTFMVO53700456 > > > > Asset Tag: > > > > Features: > > > > Board is a hosting board > > > > Board is replaceable > > > > Location In Chassis: > > > > Chassis Handle: 0x0003 > > > > Type: Motherboard > > > > Contained Object Handles: 0 > > > > > > > > Handle 0x0003, DMI type 3, 21 bytes > > > > Chassis Information > > > > Manufacturer: > > > > Type: Rack Mount Chassis > > > > Lock: Not Present > > > > Version: > > > > Serial Number: ESDW6060367 > > > > Asset Tag: > > > > Boot-up State: Safe > > > > Power Supply State: Safe > > > > Thermal State: Safe > > > > Security Status: None > > > > OEM Information: 0x00000000 > > > > Height: Unspecified > > > > Number Of Power Cords: 1 > > > > Contained Elements: 0 > > > > > > > > Handle 0x0004, DMI type 4, 35 bytes > > > > Processor Information > > > > Socket Designation: CPU 1 > > > > Type: Central Processor > > > > Family: Pentium 4 > > > > Manufacturer: Intel > > > > ID: 41 0F 00 00 FF FB EB BF > > > > Signature: Type 0, Family 15, Model 4, Stepping 1 > > > > Flags: > > > > FPU (Floating-point unit on-chip) > > > > VME (Virtual mode extension) > > > > DE (Debugging extension) > > > > PSE (Page size extension) > > > > TSC (Time stamp counter) > > > > MSR (Model specific registers) > > > > PAE (Physical address extension) > > > > MCE (Machine check exception) > > > > CX8 (CMPXCHG8 instruction supported) > > > > APIC (On-chip APIC hardware supported) > > > > SEP (Fast system call) > > > > MTRR (Memory type range registers) > > > > PGE (Page global enable) > > > > MCA (Machine check architecture) > > > > CMOV (Conditional move instruction supported) > > > > PAT (Page attribute table) > > > > PSE-36 (36-bit page size extension) > > > > CLFSH (CLFLUSH instruction supported) > > > > DS (Debug store) > > > > ACPI (ACPI supported) > > > > MMX (MMX technology supported) > > > > FXSR (Fast floating-point save and restore) > > > > SSE (Streaming SIMD extensions) > > > > SSE2 (Streaming SIMD extensions 2) > > > > SS (Self-snoop) > > > > HTT (Hyper-threading technology) > > > > TM (Thermal monitor supported) > > > > PBE (Pending break enabled) > > > > Version: Intel(R) Pentium(R) 4 CPU 3.00GHz > > > > Voltage: 3.3 V 2.9 V > > > > External Clock: 200 MHz > > > > Max Speed: 3000 MHz > > > > Current Speed: 3000 MHz > > > > Status: Populated, Enabled > > > > Upgrade: Other > > > > L1 Cache Handle: 0x0005 > > > > L2 Cache Handle: 0x0006 > > > > L3 Cache Handle: Not Provided > > > > Serial Number: > > > > Asset Tag: > > > > Part Number: > > > > > > > > Handle 0x0005, DMI type 7, 19 bytes > > > > Cache Information > > > > Socket Designation: L1-Cache > > > > Configuration: Enabled, Not Socketed, Level 1 > > > > Operational Mode: Varies With Memory Address > > > > Location: Internal > > > > Installed Size: 16 KB > > > > Maximum Size: 16 KB > > > > Supported SRAM Types: > > > > Pipeline Burst > > > > Installed SRAM Type: Pipeline Burst > > > > Speed: Unknown > > > > Error Correction Type: Single-bit ECC > > > > System Type: Data > > > > Associativity: 8-way Set-associative > > > > > > > > Handle 0x0006, DMI type 7, 19 bytes > > > > Cache Information > > > > Socket Designation: L2-Cache > > > > Configuration: Enabled, Not Socketed, Level 2 > > > > Operational Mode: Varies With Memory Address > > > > Location: Internal > > > > Installed Size: 1024 KB > > > > Maximum Size: 1024 KB > > > > Supported SRAM Types: > > > > Pipeline Burst > > > > Installed SRAM Type: Pipeline Burst > > > > Speed: Unknown > > > > Error Correction Type: Single-bit ECC > > > > System Type: Unified > > > > Associativity: 8-way Set-associative > > > > > > > > Handle 0x0007, DMI type 126, 19 bytes > > > > Inactive > > > > > > > > Handle 0x0008, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: KM1 > > > > Internal Connector Type: PS/2 > > > > External Reference Designator: PS2Mouse > > > > External Connector Type: PS/2 > > > > Port Type: Mouse Port > > > > > > > > Handle 0x0009, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: KM > > > > Internal Connector Type: PS/2 > > > > External Reference Designator: Keyboard > > > > External Connector Type: PS/2 > > > > Port Type: Keyboard Port > > > > > > > > Handle 0x000A, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J3 > > > > Internal Connector Type: Access Bus (USB) > > > > External Reference Designator: USB1 > > > > External Connector Type: Access Bus (USB) > > > > Port Type: USB > > > > > > > > Handle 0x000B, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J3 > > > > Internal Connector Type: Access Bus (USB) > > > > External Reference Designator: USB2 > > > > External Connector Type: Access Bus (USB) > > > > Port Type: USB > > > > > > > > Handle 0x000C, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J10 > > > > Internal Connector Type: DB-15 female > > > > External Reference Designator: VGA > > > > External Connector Type: DB-15 male > > > > Port Type: Video Port > > > > > > > > Handle 0x000D, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J10 > > > > Internal Connector Type: DB-9 male > > > > External Reference Designator: COM A > > > > External Connector Type: DB-9 female > > > > Port Type: Serial Port 16550A Compatible > > > > > > > > Handle 0x000E, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J11 > > > > Internal Connector Type: RJ-45 > > > > External Reference Designator: LAN > > > > External Connector Type: RJ-45 > > > > Port Type: Network Port > > > > > > > > Handle 0x000F, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J12 > > > > Internal Connector Type: RJ-45 > > > > External Reference Designator: LAN > > > > External Connector Type: RJ-45 > > > > Port Type: Network Port > > > > > > > > Handle 0x0010, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: JP1 - FLOPPY > > > > Internal Connector Type: On Board Floppy > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0011, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J4 - FNT USB 3-4 > > > > Internal Connector Type: Other > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0012, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J5 - SATA_0 > > > > Internal Connector Type: Other > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0013, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J6 - SATA_1 > > > > Internal Connector Type: Other > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0014, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J7 - SATA_2 > > > > Internal Connector Type: Other > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0015, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J8 - SATA_3 > > > > Internal Connector Type: Other > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0016, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J9 - PRI IDE > > > > Internal Connector Type: On Board IDE > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0017, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J23 - COM B > > > > Internal Connector Type: DB-9 male > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Serial Port 16550A Compatible > > > > > > > > Handle 0x0018, DMI type 8, 9 bytes > > > > Port Connector Information > > > > Internal Reference Designator: J27 - FRONT PNL > > > > Internal Connector Type: Other > > > > External Reference Designator: Not Specified > > > > External Connector Type: None > > > > Port Type: Other > > > > > > > > Handle 0x0019, DMI type 9, 13 bytes > > > > System Slot Information > > > > Designation: PCI6 > > > > Type: 64-bit PCI Express > > > > Current Usage: Available > > > > Length: Short > > > > ID: 0 > > > > Characteristics: > > > > 3.3 V is provided > > > > Opening is shared > > > > PME signal is supported > > > > > > > > Handle 0x001A, DMI type 9, 13 bytes > > > > System Slot Information > > > > Designation: PCI5 > > > > Type: 64-bit PCI-X > > > > Current Usage: Available > > > > Length: Short > > > > ID: 1 > > > > Characteristics: > > > > 3.3 V is provided > > > > Opening is shared > > > > PME signal is supported > > > > > > > > Handle 0x001B, DMI type 9, 13 bytes > > > > System Slot Information > > > > Designation: PCI4 > > > > Type: 64-bit PCI-X > > > > Current Usage: Available > > > > Length: Short > > > > ID: 2 > > > > Characteristics: > > > > 3.3 V is provided > > > > Opening is shared > > > > PME signal is supported > > > > > > > > Handle 0x001C, DMI type 9, 13 bytes > > > > System Slot Information > > > > Designation: PCI1 > > > > Type: 32-bit PCI > > > > Current Usage: Available > > > > Length: Short > > > > ID: 3 > > > > Characteristics: > > > > 5.0 V is provided > > > > Opening is shared > > > > PME signal is supported > > > > > > > > Handle 0x001D, DMI type 10, 6 bytes > > > > On Board Device Information > > > > Type: Video > > > > Status: Enabled > > > > Description: INTEL I.G.D. > > > > > > > > Handle 0x001E, DMI type 10, 6 bytes > > > > On Board Device Information > > > > Type: Ethernet > > > > Status: Enabled > > > > Description: INTEL 82541PI > > > > > > > > Handle 0x001F, DMI type 10, 6 bytes > > > > On Board Device Information > > > > Type: Ethernet > > > > Status: Enabled > > > > Description: INTEL 82541PI > > > > > > > > Handle 0x0020, DMI type 11, 5 bytes > > > > OEM Strings > > > > String 1: To Be Filled By O.E.M. > > > > > > > > Handle 0x0021, DMI type 12, 5 bytes > > > > System Configuration Options > > > > Option 1: J1f2 :2-3 Close to clear CMOS > > > > Option 2: J1F2 :6-7 Close to clear password > > > > Option 3: J1F2 :10-11 Close to boot in recovery > > > > Option 4: JP1E1:BIOS select pin > > > > > > > > Handle 0x0022, DMI type 13, 22 bytes > > > > BIOS Language Information > > > > Installable Languages: 5 > > > > en|US|iso8859-1 > > > > fr|FR|iso8859-1 > > > > de|DE|iso8859-1 > > > > it|IT|iso8859-1 > > > > es|ES|iso8859-1 > > > > Currently Installed Language: en|US|iso8859-1 > > > > > > > > Handle 0x0023, DMI type 16, 15 bytes > > > > Physical Memory Array > > > > Location: System Board Or Motherboard > > > > Use: System Memory > > > > Error Correction Type: Single-bit ECC > > > > Maximum Capacity: 4 GB > > > > Error Information Handle: Not Provided > > > > Number Of Devices: 4 > > > > > > > > Handle 0x0024, DMI type 19, 15 bytes > > > > Memory Array Mapped Address > > > > Starting Address: 0x00000000000 > > > > Ending Address: 0x0007FFFFFFF > > > > Range Size: 2 GB > > > > Physical Array Handle: 0x0023 > > > > Partition Width: 0 > > > > > > > > Handle 0x0025, DMI type 17, 27 bytes > > > > Memory Device > > > > Array Handle: 0x0023 > > > > Error Information Handle: Not Provided > > > > Total Width: 72 bits > > > > Data Width: 64 bits > > > > Size: 512 MB > > > > Form Factor: DIMM > > > > Set: 2 > > > > Locator: DIMM_1A > > > > Bank Locator: BANK0 > > > > Type: DDR > > > > Type Detail: Synchronous > > > > Speed: 533 MHz (1.9 ns) > > > > Manufacturer: Manufacturer0 > > > > Serial Number: SerNum0 > > > > Asset Tag: AssetTagNum0 > > > > Part Number: PartNum0 > > > > > > > > Handle 0x0026, DMI type 20, 19 bytes > > > > Memory Device Mapped Address > > > > Starting Address: 0x00000000000 > > > > Ending Address: 0x0001FFFFFFF > > > > Range Size: 512 MB > > > > Physical Device Handle: 0x0025 > > > > Memory Array Mapped Address Handle: 0x0024 > > > > Partition Row Position: 1 > > > > Interleaved Data Depth: 1 > > > > > > > > Handle 0x0027, DMI type 17, 27 bytes > > > > Memory Device > > > > Array Handle: 0x0023 > > > > Error Information Handle: Not Provided > > > > Total Width: 72 bits > > > > Data Width: 64 bits > > > > Size: 512 MB > > > > Form Factor: DIMM > > > > Set: 2 > > > > Locator: DIMM_2A > > > > Bank Locator: BANK1 > > > > Type: DDR > > > > Type Detail: Synchronous > > > > Speed: 533 MHz (1.9 ns) > > > > Manufacturer: Manufacturer1 > > > > Serial Number: SerNum1 > > > > Asset Tag: AssetTagNum1 > > > > Part Number: PartNum1 > > > > > > > > Handle 0x0028, DMI type 20, 19 bytes > > > > Memory Device Mapped Address > > > > Starting Address: 0x00020000000 > > > > Ending Address: 0x0003FFFFFFF > > > > Range Size: 512 MB > > > > Physical Device Handle: 0x0027 > > > > Memory Array Mapped Address Handle: 0x0024 > > > > Partition Row Position: 1 > > > > Interleaved Data Depth: 1 > > > > > > > > Handle 0x0029, DMI type 17, 27 bytes > > > > Memory Device > > > > Array Handle: 0x0023 > > > > Error Information Handle: Not Provided > > > > Total Width: 72 bits > > > > Data Width: 64 bits > > > > Size: 512 MB > > > > Form Factor: DIMM > > > > Set: 1 > > > > Locator: DIMM_1B > > > > Bank Locator: BANK0 > > > > Type: DDR > > > > Type Detail: Synchronous > > > > Speed: 533 MHz (1.9 ns) > > > > Manufacturer: Manufacturer2 > > > > Serial Number: SerNum2 > > > > Asset Tag: AssetTagNum2 > > > > Part Number: PartNum2 > > > > > > > > Handle 0x002A, DMI type 20, 19 bytes > > > > Memory Device Mapped Address > > > > Starting Address: 0x00040000000 > > > > Ending Address: 0x0005FFFFFFF > > > > Range Size: 512 MB > > > > Physical Device Handle: 0x0029 > > > > Memory Array Mapped Address Handle: 0x0024 > > > > Partition Row Position: 1 > > > > Interleaved Data Depth: 1 > > > > > > > > Handle 0x002B, DMI type 17, 27 bytes > > > > Memory Device > > > > Array Handle: 0x0023 > > > > Error Information Handle: Not Provided > > > > Total Width: 72 bits > > > > Data Width: 64 bits > > > > Size: 512 MB > > > > Form Factor: DIMM > > > > Set: 1 > > > > Locator: DIMM_2B > > > > Bank Locator: BANK1 > > > > Type: DDR > > > > Type Detail: Synchronous > > > > Speed: 533 MHz (1.9 ns) > > > > Manufacturer: Manufacturer3 > > > > Serial Number: SerNum3 > > > > Asset Tag: AssetTagNum3 > > > > Part Number: PartNum3 > > > > > > > > Handle 0x002C, DMI type 20, 19 bytes > > > > Memory Device Mapped Address > > > > Starting Address: 0x00060000000 > > > > Ending Address: 0x0007FFFFFFF > > > > Range Size: 512 MB > > > > Physical Device Handle: 0x002B > > > > Memory Array Mapped Address Handle: 0x0024 > > > > Partition Row Position: 1 > > > > Interleaved Data Depth: 1 > > > > > > > > Handle 0x002D, DMI type 24, 5 bytes > > > > Hardware Security > > > > Power-On Password Status: Disabled > > > > Keyboard Password Status: Disabled > > > > Administrator Password Status: Disabled > > > > Front Panel Reset Status: Enabled > > > > > > > > Handle 0x002E, DMI type 30, 6 bytes > > > > Out-of-band Remote Access > > > > Manufacturer Name: INTEL > > > > Inbound Connection: Disabled > > > > Outbound Connection: Enabled > > > > > > > > Handle 0x002F, DMI type 32, 20 bytes > > > > System Boot Information > > > > Status: No errors detected > > > > > > > > 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 > > > > > > > > > > > > > > > > Looking at the end of the output from ipmi-locate: > > > > 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 > > > > > > > > > > > > It looks like the SSIF information matches the output at the very end > > > > of dmidecode for SSIF. > > > > > > > > Chris > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Jan 21, 2008 7:10 AM, Bala.A <[EMAIL PROTECTED]> wrote: > > > >> > > > >> dmidecode code is used inside device probing. If there is a difference > > > >> in > > > >> ipmi-locate and latest dmidecode output, then we need to update our > > > >> dmidecode device probing code. > > > >> > > > >> Regards, > > > >> Bala > > > >> --- > > > >> Free as in freedom > > > >> http://www.gnu.org/ > > > >> > > > >> > > > >> > > > >> > I don't think this would be a kernel related issue. Bala, you have > > > >> any > > > >> > ideas? > > > >> > > > > >> > Al > > > >> > > > > >> >> Any more ideas? Have there been any important kernel changes that > > > >> >> should cause me to try to upgrade to 2.6.24? > > > >> >> > > > >> >> Chris > > > >> >> > > > >> >> > > > >> >> > > > >> >> On Jan 17, 2008 11:44 AM, Chris Morgan <[EMAIL PROTECTED]> wrote: > > > >> >>> > > > >> >>> On Jan 17, 2008 11:36 AM, Albert Chu <[EMAIL PROTECTED]> wrote: > > > >> >>> > > > > >> >>> > > > > >> >>> > > Hi Bala. Thank you for replying. > > > >> >>> > > > > > >> >>> > > On Jan 16, 2008 11:10 PM, Bala.A <[EMAIL PROTECTED]> wrote: > > > >> >>> > >> > > > >> >>> > >> Hi, > > > >> >>> > >> > > > >> >>> > >> Please find inline replies > > > >> >>> > >> > > > >> >>> > >> > > > > >> >>> > >> > # ipmi-locate > > > >> >>> > >> > Probing KCS device using DMIDECODE... FAILED > > > >> >>> > >> > > > > >> >>> > >> > Probing SMIC device using DMIDECODE... FAILED > > > >> >>> > >> > > > > >> >>> > >> > Probing BT device using DMIDECODE... FAILED > > > >> >>> > >> > > > > >> >>> > >> > Probing SSIF device using DMIDECODE... done > > > >> >>> > >> > IPMI Version: 1.5 > > > >> >>> > >> > IPMI locate driver: DMIDECODE > > > >> >>> > >> > IPMI interface: SSIF > > > >> >>> > >> > BMC driver device: /dev/i2c-0 > > > >> >>> > >> > BMC SMBUS slave address: 42 > > > >> >>> > >> > Register spacing: 1 > > > >> >>> > >> > > > > >> >>> > >> > Probing KCS device using SMBIOS... FAILED > > > >> >>> > >> > Probing SMIC device using SMBIOS... FAILED > > > >> >>> > >> > Probing BT device using SMBIOS... FAILED > > > >> >>> > >> > > > > >> >>> > >> > Probing SSIF device using SMBIOS... done > > > >> >>> > >> > IPMI Version: 1.5 > > > >> >>> > >> > IPMI locate driver: SMBIOS > > > >> >>> > >> > IPMI interface: SSIF > > > >> >>> > >> > BMC driver device: /dev/i2c-0 > > > >> >>> > >> > BMC SMBUS slave address: 84 > > > >> >>> > >> > Register spacing: 1 > > > >> >>> > >> > > > > >> >>> > >> > > > >> >>> > >> Please try the following commands and let me know they work or > > > >> not > > > >> >>> > >> > > > >> >>> > >> bmc-info --no-probing -D SSIF --driver-address=42 > > > >> >>> > >> --driver-device=/dev/i2c-0 --register-spacing=1 > > > >> >>> > >> > > > >> >>> > >> bmc-info --no-probing -D SSIF --driver-address=84 > > > >> >>> > >> --driver-device=/dev/i2c-0 --register-spacing=1 > > > >> >>> > >> > > > >> >>> > > > > > >> >>> > > > > > >> >>> > > [EMAIL PROTECTED]:~# ls /dev/i2c* > > > >> >>> > > /dev/i2c-0 > > > >> >>> > > > > > >> >>> > > [EMAIL PROTECTED]:~# lsmod | grep i2c > > > >> >>> > > i2c_i801 10128 0 > > > >> >>> > > i2c_dev 8708 0 > > > >> >>> > > i2c_core 26112 2 i2c_i801,i2c_dev > > > >> >>> > > > > > >> >>> > > [EMAIL PROTECTED]:~# lspci > > > >> >>> > > 00:00.0 Host bridge: Intel Corporation E7220/E7221 Memory > > > >> >>> Controller > > > >> >>> > > Hub (rev 05) > > > >> >>> > > 00:02.0 VGA compatible controller: Intel Corporation E7221 > > > >> >>> Integrated > > > >> >>> > > Graphics Controller (rev 05) > > > >> >>> > > 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW > > > >> (ICH6 > > > >> >>> > > Family) PCI Express Port 1 (rev 03) > > > >> >>> > > 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW > > > >> >>> (ICH6 > > > >> >>> > > Family) USB UHCI #1 (rev 03) > > > >> >>> > > 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW > > > >> >>> (ICH6 > > > >> >>> > > Family) USB UHCI #2 (rev 03) > > > >> >>> > > 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW > > > >> >>> (ICH6 > > > >> >>> > > Family) USB UHCI #3 (rev 03) > > > >> >>> > > 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW > > > >> >>> (ICH6 > > > >> >>> > > Family) USB2 EHCI Controller (rev 03) > > > >> >>> > > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) > > > >> >>> > > 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) > > > >> LPC > > > >> >>> > > Interface Bridge (rev 03) > > > >> >>> > > 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW > > > >> >>> (ICH6 > > > >> >>> > > Family) IDE Controller (rev 03) > > > >> >>> > > 00:1f.2 IDE interface: Intel Corporation 82801FR/FRW > > > >> (ICH6R/ICH6RW) > > > >> >>> > > SATA Controller (rev 03) > > > >> >>> > > 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 > > > >> >>> Family) > > > >> >>> > > SMBus Controller (rev 03) > > > >> >>> > > 01:03.0 Ethernet controller: Intel Corporation 82541GI Gigabit > > > >> >>> > > Ethernet Controller (rev 05) > > > >> >>> > > 02:00.0 PCI bridge: Intel Corporation 6700PXH PCI > > > >> >>> > > Express-to-PCI > > > >> >>> > > Bridge A (rev 09) > > > >> >>> > > 02:00.2 PCI bridge: Intel Corporation 6700PXH PCI > > > >> >>> > > Express-to-PCI > > > >> >>> > > Bridge B (rev 09) > > > >> >>> > > 04:03.0 Ethernet controller: Intel Corporation 82541GI Gigabit > > > >> >>> > > Ethernet Controller (rev 05) > > > >> >>> > > > > > >> >>> > > [EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF > > > >> >>> > > --driver-address=42 > > > >> >>> > > --driver-device=/dev/i2c-0 --register-spacing=1 > > > >> >>> > > ipmi-ssif-api-udm.c: 81: ipmi_ssif_cmd_udm: errnum (4): > > > >> expression > > > >> >>> failed > > > >> >>> > > ipmi_cmd_get_device_id: permission denied > > > >> >>> > > > > > >> >>> > > [EMAIL PROTECTED]:~# bmc-info --no-probing -D SSIF > > > >> >>> > > --driver-address=84 > > > >> >>> > > --driver-device=/dev/i2c-0 --register-spacing=1 > > > >> >>> > > ipmi-ssif-api-udm.c: 81: ipmi_ssif_cmd_udm: errnum (4): > > > >> expression > > > >> >>> failed > > > >> >>> > > ipmi_cmd_get_device_id: permission denied > > > >> >>> > > > > >> >>> > Bala, FYI line 81 is a call to 'ipmi_ssif_write'. > > > >> >>> > > > > >> >>> > errnum 4 in the ssif lib is IPMI_SSIF_CTX_ERR_PERMISSION. > > > >> >>> > > > > >> >>> > the errnum seems to be set via this code chunk: > > > >> >>> > > > > >> >>> > if (buf_len <= IPMI_I2C_SMBUS_BLOCK_MAX) > > > >> >>> > { > > > >> >>> > count = ipmi_ssif_single_part_write (ctx->device_fd, > > > >> >>> > buf, > > > >> >>> > buf_len); > > > >> >>> > } > > > >> >>> > else > > > >> >>> > { > > > >> >>> > count = ipmi_ssif_multi_part_write (ctx->device_fd, > > > >> >>> > buf, > > > >> >>> > buf_len); > > > >> >>> > } > > > >> >>> > > > > >> >>> > if (count < 0) > > > >> >>> > { > > > >> >>> > if (errno == EACCES || errno == EPERM) > > > >> >>> > ctx->errnum = IPMI_SSIF_CTX_ERR_PERMISSION; > > > >> >>> > else > > > >> >>> > ERR_LOG(ctx->errnum = IPMI_SSIF_CTX_ERR_SYSTEM_ERROR); > > > >> >>> > goto cleanup; > > > >> >>> > } > > > >> >>> > > > > >> >>> > tracing this into the deeper write calls, the errno is coming > > > >> >>> > from > > > >> >>> the > > > >> >>> > core ioctl() call for ssif. > > > >> >>> > > > > >> >>> > It looks like Chris is root above, so EACCES is not the likely > > > >> >>> returned > > > >> >>> > errno, EPERM = "Operation Not Permitted" is. So the question is > > > >> why > > > >> >>> is > > > >> >>> > the ioctl not allowed. > > > >> >>> > > > > >> >>> > Chris, does anything interesting show up in the 'dmesg' logs? > > > >> >>> > > > > >> >>> > > > >> >>> You know I checked to see if there might have been something going > > > >> on > > > >> >>> but this is the end of dmesg: > > > >> >>> > > > >> >>> ... > > > >> >>> [ 67.895740] input: Power Button (CM) as /class/input/input3 > > > >> >>> [ 67.895768] ACPI: Power Button (CM) [PWRB] > > > >> >>> [ 68.882998] NET: Registered protocol family 10 > > > >> >>> [ 68.883919] lo: Disabled Privacy Extensions > > > >> >>> [ 79.554513] eth0: no IPv6 routers present > > > >> >>> [ 381.528584] i2c /dev entries driver > > > >> >>> [ 386.804841] ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 > > > >> >>> (level, > > > >> >>> low) -> IRQ 20 > > > >> >>> > > > >> >>> Chris > > > >> >>> > > > >> >> > > > >> > > > > >> > > > > >> > -- > > > >> > Albert Chu > > > >> > [EMAIL PROTECTED] > > > >> > 925-422-5311 > > > >> > Computer Scientist > > > >> > High Performance Systems Division > > > >> > Lawrence Livermore National Laboratory > > > >> > > > > >> > > > >> > > > >> > > > >> > > > >> _______________________________________________ > > > >> Freeipmi-users mailing list > > > >> [email protected] > > > >> http://lists.gnu.org/mailman/listinfo/freeipmi-users > > > >> > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > [email protected] > > > http://lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > [email protected] > > http://lists.gnu.org/mailman/listinfo/freeipmi-users -- Albert Chu [EMAIL PROTECTED] 925-422-5311 Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-users
