On Tue, 2010-09-14 at 14:25 -0700, Kenneth Stailey wrote:
> --- On Tue, 9/14/10, Albert Chu <[email protected]> wrote:
> > This trace is the same as when the patch wasn't
> > applied. Are you sure
> > you applied the patch on this particular version?
>
>
> sure I am sure.
Doh! I read it wrong. It is infact a different trace. My bad.
> k...@niobium:~/src/freeipmi-0.8.9$ grep -C 3
> '!=.*IPMI_ADDRESS_SPACE_ID_SYSTEM_IO' libfreeipmi/src/api/ipmi-api.c
>
> /* At this point we only support SYSTEM_IO, i.e. inb/outb style IO.
> If we cant find the bass address, we better exit. -- Anand Babu */
> if (locate_info.address_space_id != IPMI_ADDRESS_SPACE_ID_SYSTEM_IO)
> {
> API_SET_ERRNUM (ctx, IPMI_ERR_DEVICE_NOT_SUPPORTED);
> goto cleanup;
>
> k...@niobium:~/src/freeipmi-0.8.9$ ls -l libfreeipmi/src/api/ipmi-api.c
> -rw-r--r-- 1 ksta users 63943 2010-09-13 13:17 libfreeipmi/src/api/ipmi-api.c
>
> k...@niobium:~/src/freeipmi-0.8.9$ ls -l /opt/freeipmi/sbin/ipmi-sensors
> -rwxr-xr-x 1 root root 683561 2010-09-14 11:01 /opt/freeipmi/sbin/ipmi-sensors
> k...@niobium:~/src/freeipmi-0.8.9$
>
> --- On Tue, 9/14/10, Albert Chu <[email protected]> wrote:
> > On the one w/ the patch applied, could you send a --debug
> > output? Maybe
> > there is something w/n the IPMI protocol I'm missing.
>
> k...@niobium:~/src/freeipmi-0.8.9$ sudo rmmod ipmi_si ipmi_devintf
> ipmi_msghandler
>
> k...@niobium:~/src/freeipmi-0.8.9$ lsmod | grep ipmi
> k...@niobium:~/src/freeipmi-0.8.9$
>
> k...@niobium:~/src/freeipmi-0.8.9$ sudo /opt/freeipmi/sbin/ipmi-sensors
> --debug
> ipmi-openipmi-driver.c: 379: ipmi_openipmi_ctx_io_init: errno '' (2)
> ipmi-api.c: 1004: ipmi_ctx_open_inband: error 'device not found' (5)
> ipmi-sunbmc-driver.c: 330: ipmi_sunbmc_ctx_io_init: errno '' (2)
> ipmi-api.c: 1031: ipmi_ctx_open_inband: error 'device not found' (5)
> ipmi-api.c: 849: ipmi_ctx_open_inband: error 'device not supported' (17)
> ipmi-locate-dmidecode.c: 562: ipmi_locate_dmidecode_get_device_info: error
> 'internal system error' (6)
> ipmi-locate-smbios.c: 411: _copy_ipmi_dev_info: error 'internal system error'
> (6)
> ipmi-locate-pci.c: 301: ipmi_locate_pci_get_device_info: error 'internal
> system error' (6)
> ipmi-locate.c: 161: _ipmi_locate_get_device_info: error 'internal system
> error' (6)
> ipmi-api.c: 849: ipmi_ctx_open_inband: error 'device not supported' (17)
> ipmi-locate-dmidecode.c: 562: ipmi_locate_dmidecode_get_device_info: error
> 'internal system error' (6)
> ipmi-locate-smbios.c: 411: _copy_ipmi_dev_info: error 'internal system error'
> (6)
> ipmi-locate-pci.c: 301: ipmi_locate_pci_get_device_info: error 'internal
> system error' (6)
> ipmi-ssif-driver.c: 683: ipmi_ssif_ctx_io_init: errno '' (2)
> ipmi-api.c: 977: ipmi_ctx_open_inband: error 'device not found' (9)
> ipmi-api.c: 1994: ipmi_ctx_close: error 'device not open' (16)
> could not find inband device
> k...@niobium:~/src/freeipmi-0.8.9$
>
> k...@niobium:~/src/freeipmi-0.8.9$ sudo modprobe ipmi_si
> k...@niobium:~/src/freeipmi-0.8.9$ sudo modprobe ipmi_devintf
>
> k...@niobium:~/src/freeipmi-0.8.9$ lsmod | grep ipmi
> ipmi_devintf 20624 0
> ipmi_si 57164 0
> ipmi_msghandler 50680 2 ipmi_devintf,ipmi_si
>
> k...@niobium:~/src/freeipmi-0.8.9$ sudo /opt/freeipmi/sbin/ipmi-sensors
> --debug > ~/freeipmi-debug 2>&1
>
> see attachment
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?
Thanks,
Al
--
Albert Chu
[email protected]
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
_______________________________________________
Freeipmi-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/freeipmi-devel
