freeipmi-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-users] freeipmi 0.3.3 on a dell poweredge 2950


From: Florian Schlums
Subject: Re: [Freeipmi-users] freeipmi 0.3.3 on a dell poweredge 2950
Date: Tue, 7 Aug 2007 21:25:49 +0200
User-agent: Thunderbird 2.0.0.6 (Windows/20070728)

Hi Al

You're right, I'm not really familiar with freeipmi.
I think I will check freeipmi 0.4.2. if possible.
bmc-info brought no positive response:
on my 2950:
Bus error: 10
and on my 2850:
Bus error:
Nothing else.
Also those two ipmi-sensors suggestions didn't help.

Regards Florian

Al Chu schrieb:
Hi Florian,

Not sure of your familiar w/ FreeIPMI, just to double check, you
attempted to flush, and then re-run ipmi-sensors again?

I've pinged the other FreeIPMI develoeprs to throw in some of their
ideas.  But some of mine:

1)

Could you try running bmc-info?  Since that doesn't require an SDR
cache, it will remove at least 1 variable from this trouble-shooting.

2)

It looks like the default addresses were utilized on the 2600, so maybe
it's worth a shot trying them on the 2800/2900:

ipmi-sensors --no-probing -D KCS --driver-address=0xCA2 --register-
spacing 1

and for kicks try register spacing of 4 too

ipmi-sensors --no-probing -D KCS --driver-address=0xCA2 --register-
spacing 4

in fact it may be worth trying a few combinations, including 0xCA8 in
there too b/c that is the probed driver address.

3)

I re-wrote the SDR cache debugging/stableness code in 0.4.X.  It
includes some extra debugging.  It may be worthwhile trying to install a
newer version to get extra info.
Al

On Tue, 2007-08-07 at 16:24 +0200, TestmailBBnewcop wrote:
Hi Al

thanks for your answer.
ipmi-locate looks a bit different on my poweredge 2600:

--------------------------<snip>------------------------------
Probing KCS device using DMIDECODE... FAILED

Probing SMIC device using DMIDECODE... FAILED

Probing BT device using DMIDECODE... done
IPMI Version: 1.0
IPMI locate driver: DMIDECODE
IPMI interface: BT
BMC driver device:
BMC I/O base address: E4
Register space: 1

Probing SSIF device using DMIDECODE... FAILED
Probing KCS device using SMBIOS... FAILED
Probing SMIC device using SMBIOS... FAILED
Probing BT device using SMBIOS... FAILED
Probing SSIF device using SMBIOS... FAILED
Probing KCS device using ACPI... FAILED
Probing SMIC device using ACPI... FAILED
Probing BT device using ACPI... FAILED
Probing SSIF device using ACPI... FAILED
Probing KCS device using PCI... FAILED
Probing SMIC device using PCI... FAILED
Probing BT device using PCI... FAILED
Probing SSIF device using PCI... FAILED

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 space: 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 space: 1

BT device default values:

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 space: 1

--------------------------<snap>------------------------------
I checked it also on a poweredge 2850 and got the same error.
The poweredge 2600 seems to be the only working system.
The differences between 2850 and 2950:
2950:
--------------------------<snip>------------------------------
Probing KCS device using DMIDECODE... done
IPMI Version: 2.0
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device:
BMC I/O base address: CA8
Register space: 4
--------------------------<snip>------------------------------

2850:
--------------------------<snip>------------------------------
Probing KCS device using DMIDECODE... done
IPMI Version: 1.5
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device:
BMC I/O base address: CA8
Register space: 4
--------------------------<snip>------------------------------

I tried the flush cache option but it didn't solve it.

Florian


Albert Chu schrieb:
Hi Florian,

Out of my curiosity, did ipmi-locate return the same info on the dell
poweredge 2600??

I'm not 100% on what your bug could be right now, but could you also try
to flush the SDR cache using the -f option.  There was a similar fread()
error message on the FreeIPMI 0.4.X trunk that I fixed.  I suppose it's
possible it existed in 0.3.X too.

Al

Hello
i'm testing freeipmi 0.3.3 on a freebsd 6.2 server (dell poweredge 2950).
Freeipmi was installed from ports and der is no newer version there at
the moment.
ipmi-locate gives me the following:
--------------------------<snip>------------------------------
FILTER3.GGAMAUR.NET # ipmi-locate
Probing KCS device using DMIDECODE... done
IPMI Version: 2.0
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device:
BMC I/O base address: CA8
Register space: 4

Probing SMIC device using DMIDECODE... FAILED
Probing BT device using DMIDECODE... FAILED
Probing SSIF device using DMIDECODE... FAILED
Probing KCS device using SMBIOS... FAILED
Probing SMIC device using SMBIOS... FAILED
Probing BT device using SMBIOS... FAILED
Probing SSIF device using SMBIOS... FAILED
Probing KCS device using ACPI... FAILED
Probing SMIC device using ACPI... FAILED
Probing BT device using ACPI... FAILED
Probing SSIF device using ACPI... FAILED
Probing KCS device using PCI... FAILED
Probing SMIC device using PCI... FAILED
Probing BT device using PCI... FAILED
Probing SSIF device using PCI... FAILED

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 space: 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 space: 1

BT device default values:

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 space: 1
--------------------------<snap>------------------------------
And ipmi-sensors that:
--------------------------<snip>------------------------------
FILTER3.GGAMAUR.NET # ipmi-sensors
FAILED: _fread_record: Invalid argument
Fetching SDR repository information... Bus error: 10
--------------------------<snap>------------------------------

I tried the same on an older Dell Poweredge 2600 and there it works
without a problem.
Could anybody give me a hint what it could be?

Regards
Florian





_______________________________________________
Freeipmi-users mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/freeipmi-users






reply via email to

[Prev in Thread] Current Thread [Next in Thread]