pradeep which node? It needs node 2, 3, and 4 need some extra step as per
shashi. Can you try it node 1 if it is not node one. Otherwise you need to
get the steps from shashi to enabled i2c on those nodes.
Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
On Tue, Aug 5, 2014 at 10:16 PM, Kodamati Pradeep Vinesh Reddy <
<email address hidden>> wrote:
> I am seeing the error like mentioned by manoj above comment #4
>
> root@ubuntu:~# bmc-info --no-probing --driver-type=SSIF
> --driver-address=0x10 --driver-device=/dev/i2c-2 --get-device-id --debug
> =====================================================
> Get Device ID Request
> =====================================================
> SSIF Header:
> ------------
> [ 0h] = lun[ 2b]
> [ 6h] = net_fn[ 6b]
> IPMI Command Data:
> ------------------
> [ 1h] = cmd[ 8b]
> ipmi_cmd_get_device_id: internal system error
> root@ubuntu:~#
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1324992
>
> Title:
> freeipmi patch for HP moonshot ARM cartridges with I2c
>
> Status in “freeipmi” package in Ubuntu:
> Fix Released
> Status in “freeipmi” source package in Trusty:
> Fix Committed
> Status in “freeipmi” package in Debian:
> New
>
> Bug description:
> [Impact]
> freeipmi is unable to reliable communicate with the BMC on ARM HP
> Moonshot cartridges
> [Test Case]
>
> [Regression Potential]
> Should be minimal, given the new code only runs in a case that would've
> previous resulted in a failure.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992/+subscriptions
>
pradeep which node? It needs node 2, 3, and 4 need some extra step as per
shashi. Can you try it node 1 if it is not node one. Otherwise you need to
get the steps from shashi to enabled i2c on those nodes.
Thanks and Regards, 07[skype]
Narinder Gupta (PMP) <email address hidden>
Canonical, Ltd. narindergupta [irc.freenode.net]
+1.281.736.5150 narindergupta20
Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
On Tue, Aug 5, 2014 at 10:16 PM, Kodamati Pradeep Vinesh Reddy <
<email address hidden>> wrote:
> I am seeing the error like mentioned by manoj above comment #4 address= 0x10 --driver- device= /dev/i2c- 2 --get-device-id --debug ======= ======= ======= ======= ======= ======= ==== ======= ======= ======= ======= ======= ======= ==== get_device_ id: internal system error /bugs.launchpad .net/bugs/ 1324992 /bugs.launchpad .net/ubuntu/ +source/ freeipmi/ +bug/1324992/ +subscriptions
>
> root@ubuntu:~# bmc-info --no-probing --driver-type=SSIF
> --driver-
> =======
> Get Device ID Request
> =======
> SSIF Header:
> ------------
> [ 0h] = lun[ 2b]
> [ 6h] = net_fn[ 6b]
> IPMI Command Data:
> ------------------
> [ 1h] = cmd[ 8b]
> ipmi_cmd_
> root@ubuntu:~#
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> freeipmi patch for HP moonshot ARM cartridges with I2c
>
> Status in “freeipmi” package in Ubuntu:
> Fix Released
> Status in “freeipmi” source package in Trusty:
> Fix Committed
> Status in “freeipmi” package in Debian:
> New
>
> Bug description:
> [Impact]
> freeipmi is unable to reliable communicate with the BMC on ARM HP
> Moonshot cartridges
> [Test Case]
>
> [Regression Potential]
> Should be minimal, given the new code only runs in a case that would've
> previous resulted in a failure.
>
> To manage notifications about this bug go to:
>
> https:/
>