Re: [Freeipmi-devel] ipmi_ctx_find_inband: device already open

[Kenneth Stailey]

ipmi-sensors -D KCS --disable-auto-probe --driver-address=0xCA2
--register-spacing=1

does work

--- On Tue, 9/14/10, Albert Chu <address@hidden> wrote:

> From: Albert Chu <address@hidden>
> Subject: Re: [Freeipmi-devel] ipmi_ctx_find_inband: device already open
> To: "Kenneth Stailey" <address@hidden>
> Cc: "address@hidden" <address@hidden>
> Date: Tuesday, September 14, 2010, 7:23 PM
> Hey Kenneth,
> 
> I now see the full "path" of what's going on.  The key
> is the
> 'IPMI_ADDRESS_SPACE_ID_SYSTEM_IO' bit, that indicates that
> system IO
> isn't supported w/ KCS.
> 
> However, with the info from the ipmi-locate below, it
> strongly suggests
> that KCS is supported, but that maybe that bit was set
> wrong.  For fun,
> could you give the following a try?
> 
> ipmi-sensors -D KCS --disable-auto-probe
> --driver-address=0xCA2
> --register-spacing=1
> 
> and see if that works?  If it does, then we atleast
> have something we
> can point to HP and say there's an issue.
> 
> Thanks,
> Al
> 
> On Tue, 2010-09-14 at 15:28 -0700, Kenneth Stailey wrote:
> > 
> > --- On Tue, 9/14/10, Albert Chu <address@hidden>
> wrote:
> > 
> > > I'm beginning to wonder if your motherboard
> simply has an
> > > interface that
> > > is supported by the IPMI kernel driver but not
> by
> > > FreeIPMI's default
> > > libraries.  Could you run ipmi-locate real
> quick to
> > > see?
> > 
> > Using unpatched ipmi-locate:
> > 
> > address@hidden:~/src/freeipmi-0.8.9$ sudo rmmod ipmi_si
> ipmi_devintf ipmi_msghandler
> > 
> > address@hidden:~/src/freeipmi-0.8.9$ type ipmi-locate
> > ipmi-locate is /usr/sbin/ipmi-locate
> > 
> > address@hidden:~/src/freeipmi-0.8.9$ ipmi-locate
> --version
> > ipmi-locate - 0.8.9
> > Copyright (C) 2003-2010 FreeIPMI Core Team
> > This program is free software; you may redistribute it
> under the terms of
> > the GNU General Public License.  This program has
> absolutely no warranty.
> > 
> > address@hidden:~/src/freeipmi-0.8.9$ sudo ipmi-locate
> > Probing KCS device using DMIDECODE... done
> > IPMI Version: 1.5
> > IPMI locate driver: DMIDECODE
> > IPMI interface: KCS
> > BMC driver device: 
> > BMC memory base address: 0xCA2
> > Register spacing: 1
> > 
> > Probing SMIC device using DMIDECODE... FAILED
> > 
> > Probing BT device using DMIDECODE... FAILED
> > 
> > Probing SSIF device using DMIDECODE... FAILED
> > 
> > Probing KCS device using SMBIOS... done
> > IPMI Version: 1.5
> > IPMI locate driver: SMBIOS
> > IPMI interface: KCS
> > BMC driver device: 
> > BMC memory base address: 0xCA3
> > Register spacing: 1
> > 
> > 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: 0xCA2
> > 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: 0xCA9
> > Register spacing: 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: 0x42
> > Register spacing: 1
> -- 
> Albert Chu
> address@hidden
> Computer Scientist
> High Performance Systems Division
> Lawrence Livermore National Laboratory
> 
>