<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-host-ipmid/app, branch master</title>
<subtitle>OpenBMC Phosphor local IPMI daemon sources</subtitle>
<id>https://git.raptorcs.com/git/phosphor-host-ipmid/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/phosphor-host-ipmid/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/'/>
<updated>2020-01-14T12:12:45+00:00</updated>
<entry>
<title>Don't report serviceable action if the watchdog service is not present</title>
<updated>2020-01-14T12:12:45+00:00</updated>
<author>
<name>Tom Joseph</name>
<email>tomjoseph@in.ibm.com</email>
</author>
<published>2019-09-24T12:22:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=c665652df4c6d05f34ae1af49b2e7756629abbe3'/>
<id>urn:sha1:c665652df4c6d05f34ae1af49b2e7756629abbe3</id>
<content type='text'>
There were a few cases where a service action was reported because the
watchdog service was not present. It was because of a race condition where
the power down operation is trigerred and the watchdog service is shutdown
but if was followed by a watchdog reset. Since the watchdog service is absent
it resulted in an error log which calls for serviceable action. The IPMI error
response code will report the failure to the host platform software.

Change-Id: Iaf0a860b53fbd85dc451fc4d4a337406ba74e0d6
Signed-off-by: Tom Joseph &lt;tomjoseph@in.ibm.com&gt;
</content>
</entry>
<entry>
<title>app/watchdog: Always use resetTimeRemaining</title>
<updated>2020-01-06T23:37:15+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-12-06T01:04:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=ebc53cb165ea26aa48f0bbf01d9bce0e4abb0b7d'/>
<id>urn:sha1:ebc53cb165ea26aa48f0bbf01d9bce0e4abb0b7d</id>
<content type='text'>
The SetWatchdog function currently sets the intervals and then the time
remaining on the watchdog. It uses the user provided interval for both
values. Recently, the watchdog was extended to allow for the interval to
be capped above a certain value to prevent the user from setting
watchdogs that are known to be too short. In order to keep the
timeRemaining in sync with the value in the watchdog, just use the
resetTimeRemaining() function which reads the current interval to set
the timeRemaining.

Change-Id: I3f15030a85c625fcb1ed8040add03496618a5ece
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>Expiration flags fix for watchdog get/set commands</title>
<updated>2019-11-01T14:50:13+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2019-10-14T04:42:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=a729bf414b8d44bbb7ca28eefe1003786d37c353'/>
<id>urn:sha1:a729bf414b8d44bbb7ca28eefe1003786d37c353</id>
<content type='text'>
The expiration flags should be retain their state
across system resets and power cycles.

Tested:
Set “BIOS FRB2” and start
ipmitool raw 0x06 0x24 0x01 0x00 0x00 0x00 0x30 0x00
ipmitool mc watchdog reset

after stopped:
Timer Expiration Flags should be : (0x02)
                        * BIOS FRB2

Then Set “BIOS/POST” and start,
ipmitool raw 0x06 0x24 0x02 0x00 0x00 0x00 0x30 0x00
ipmitool mc watchdog reset

after stopped:
Timer Expiration Flags should be : (0x06)
                        * BIOS FRB2
                        * BIOS/POST

“impitool mc watchdog get” displays the correct Timer Expiration Flags
when the timer is running;

Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
Change-Id: Ic0c27c6c1e8bed2db8ce30fc0eec2a6538bb1992
</content>
</entry>
<entry>
<title>channel:Fix get channel ciphersuite - payloadtypes</title>
<updated>2019-10-24T18:11:42+00:00</updated>
<author>
<name>jayaprakash Mutyala</name>
<email>mutyalax.jayaprakash@intel.com</email>
</author>
<published>2019-10-03T19:36:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=69daefa04a4f7d5ab21480137991b88c6b34ee1d'/>
<id>urn:sha1:69daefa04a4f7d5ab21480137991b88c6b34ee1d</id>
<content type='text'>
Issue: Get channel CipherSuite command passed with invalid payload type

Fix: Added the check now to allow only valid payload types

Tested:
Command:  ipmitool raw 0x06 0x54 0x01 0xff 0x80
Response: Unable to send RAW command (channel=0x0 netfn=0x6 lun=0x0 cmd=0x54
          rsp=0x80): Unknown (0x80)

Command:  ipmitool raw 0x06 0x54 0x01 0x12 0x80
Response: 01 c0 03 01 41 81 c0 11 03 44 81

Command:  ipmitool raw 0x06 0x54 0x01 0x09 0x80
Response: Unable to send RAW command (channel=0x0 netfn=0x6 lun=0x0 cmd=0x54
          rsp=0x80): Unknown (0x80)

Command:  ipmitool raw 0x06 0x54 0x01 0x02 0x00
Response: Unable to send RAW command (channel=0x0 netfn=0x6 lun=0x0 cmd=0x54
          rsp=0x80): Unknown (0x80)
Command:  ipmitool raw 0x06 0x54 0x01 0x12 0x00
Response: 01 01 03 41 44 81

Signed-off-by: jayaprakash Mutyala &lt;mutyalax.jayaprakash@intel.com&gt;
Change-Id: I552250736d7e898191ddbb45fd1bff42681b9c63
</content>
</entry>
<entry>
<title>Data checking fix for watchdog set/get commands</title>
<updated>2019-10-11T15:27:52+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2019-09-29T06:18:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=4dd71af3d5262064c8d8700825f8cb4d616b5fa7'/>
<id>urn:sha1:4dd71af3d5262064c8d8700825f8cb4d616b5fa7</id>
<content type='text'>
data length check for timeout action and byte 1 reserved field check
are missing, causing not to throw the error;
Log flags is on bit 7, also needs to right-shift this flag;
This commit fixes these issues;

Tested:
Set different timer use/actions:
ipmitool raw 0x06 0x24 0x85 0x0 0x0 0x0 0x64 0x00
ipmitool raw 0x06 0x24 0x84 0x1 0x0 0x0 0x64 0x00

Check the settings are correct:
ipmitool raw 0x06 0x25

Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
Change-Id: Ia4226bb4597d2c670f93522aa763e43d15eb6cf1
</content>
</entry>
<entry>
<title>transporthandler: Rewrite + New Handler</title>
<updated>2019-09-27T17:18:29+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2019-04-07T01:19:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=c514d874e4ce3ed1f747cfcb4bab5990393c55e8'/>
<id>urn:sha1:c514d874e4ce3ed1f747cfcb4bab5990393c55e8</id>
<content type='text'>
This rewrites the old transport handler to use the new ipmi handler
registration functions. It attempts to clean up the old code, by
refactoring any business logic out of the code that parses the IPMI
messages. This makes the code paths easier to understand and allows for
better code re-use.

This also gets rid of the concept of the settings change timer. Clients
expect to see their settings take effect as soon as they are set,
regardless of the "Set In Progress" flag. This means we no longer need a
cache for our network settings that are about to be set by the daemon,
and a client can hold the BMC in "Set In Progress" while it verifies
settings like other BMC implementations.

Change-Id: I5406a674f087600afdfc2c0b3adeacde10986abc
Signed-off-by: William A. Kennington III &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>Fix: execute get channel cipher suite in lan chan</title>
<updated>2019-09-25T05:36:40+00:00</updated>
<author>
<name>Ayushi Smriti</name>
<email>smriti.ayushi@linux.intel.com</email>
</author>
<published>2019-09-03T06:13:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=d7dadc27792747c00c3bfef4fc45d6f3184ba815'/>
<id>urn:sha1:d7dadc27792747c00c3bfef4fc45d6f3184ba815</id>
<content type='text'>
Get channel cipher suites command was executed for non lan channels.
Fixing the same by adding active lan channel support check.

Tested:
ipmitool raw 0x06 0x54 0x01 0x00 0x80
 01 c0 03 01 41 81 c0 11 03 44 81
                             //cmd executed for lan chan 1

ipmitool raw 0x06 0x54 0x00 0x00 0x80
Unable to send RAW command (channel=0x0 netfn=0x6 lun=0x0
cmd=0x54 rsp=0xcc): Invalid data field in request
                          //cc resulted for non lan chan 0

Signed-off-by: Ayushi Smriti &lt;smriti.ayushi@linux.intel.com&gt;
Change-Id: Ic3c2dfa3f4537be789e2afc912fa8f4c2a49bda4
</content>
</entry>
<entry>
<title>Fix: refactor get channel cipher suite command</title>
<updated>2019-09-25T05:31:25+00:00</updated>
<author>
<name>Ayushi Smriti</name>
<email>smriti.ayushi@linux.intel.com</email>
</author>
<published>2019-08-30T13:47:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=5c3b72c6c167bf69de1dfd813745a7170b5ae995'/>
<id>urn:sha1:5c3b72c6c167bf69de1dfd813745a7170b5ae995</id>
<content type='text'>
Get channel cipher suites command updated as per new ipmi structure.

Tested:
ipmitool raw 0x06 0x54 0x01 0x00 0x80
01 c0 03 01 41 81 c0 11 03 44 81                //response

Also verified by issuing cmd:
ipmitool channel getciphers ipmi 0x01
which listed supported CIA algorithms as response

Signed-off-by: Ayushi Smriti &lt;smriti.ayushi@linux.intel.com&gt;
Change-Id: Ibc942f5b197c72071cd35a138fbe244db7519824
</content>
</entry>
<entry>
<title>Static code analysis scan issue fix</title>
<updated>2019-09-23T17:50:41+00:00</updated>
<author>
<name>Chen,Yugang</name>
<email>yugang.chen@linux.intel.com</email>
</author>
<published>2019-09-06T03:03:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=0e862fabcc4772ec8f98c60ed3ddd004f785b6ce'/>
<id>urn:sha1:0e862fabcc4772ec8f98c60ed3ddd004f785b6ce</id>
<content type='text'>
Fix the issues found during code static scan

Tested:
test in board, function works fine.
1. busctl set-property for watchdog, it works fine.
2. It works by running "ipmitool chassis power soft".
3. run "ipmitool raw 0x6 0x46 1", get expected user information.

Change-Id: I7a2cc3c934db6a7531f8a8ea05956cb6d6337633
Signed-off-by: Chen,Yugang &lt;yugang.chen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Watchdog: move get and set watchdog to new api.</title>
<updated>2019-09-10T23:39:02+00:00</updated>
<author>
<name>Deepak Kumar Sahu</name>
<email>deepakx.sahu@intel.com</email>
</author>
<published>2019-05-20T14:58:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-host-ipmid/commit/?id=cfae948b82765c8dbaec809e0f13744e8dedb934'/>
<id>urn:sha1:cfae948b82765c8dbaec809e0f13744e8dedb934</id>
<content type='text'>
Rewrite "get and set watchdog" command to use the newly
introduced ipmi api.

Tested:
Verified using ipmitool "get and set watchdog",
timer behavior is same before and after the changes.

Testing Procedure:
default watchdog timer is 11.2 seconds.

ipmitool raw 0x06 0x25      ---&gt; Get
Output: 00 00 00 00 70 17 70 17

Note: Here 70 count(hex value)-&gt;112 count(decimal value)-&gt;112*100=11200ms
[100ms per count]-&gt;11.2sec (watchdog timer)

watchdog timer set to 20 seconds.

ipmitool raw 0x06 0x24 0x44 0x01 0x00 0x10 0xc8 0x00   ----&gt; Set
output:

ipmitool raw 0x06 0x25    ---&gt; Get
output: 04 01 00 00 c8 00 c8 00

Note: Here 20sec-&gt;20000ms-&gt;200count-&gt;c8 (hex value)

Signed-off-by: Deepak Kumar Sahu &lt;deepakx.sahu@intel.com&gt;
Change-Id: Id8c096bc1635d1900ee842a9726c49fb690fa8bc
</content>
</entry>
</feed>
