<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/provingground.git, branch master</title>
<subtitle>Intel BMC provingground (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/atom?h=master</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/'/>
<updated>2020-02-27T10:59:52+00:00</updated>
<entry>
<title>Update PFR event mappings in mainapp.</title>
<updated>2020-02-27T10:59:52+00:00</updated>
<author>
<name>Chalapathi</name>
<email>chalapathix.venkataramashetty@intel.com</email>
</author>
<published>2020-02-14T15:43:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=bee56d62b209088454d166d1efae4825a2b175df'/>
<id>urn:sha1:bee56d62b209088454d166d1efae4825a2b175df</id>
<content type='text'>
Updated the last panic reason, recovery reason and major/minor code
event log mappings, as per latest PFR document changes

Tested:
1. Update BIOS fw via Redfish
POST: https://&lt;BMC_IP&gt;/redfish/v1/UpdateService
Upload binary: &lt;BIOS binary file&gt;
2. Validate in redfish event logs:
   GET: https://&lt;BMC_IP&gt;/redfish/v1/Systems/system/LogServices/EventLog/Entries

    {
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog
                   /Entries/1581504982",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "2020-02-12T10:56:22+00:00",
      "EntryType": "Event",
      "Id": "1581504982",
      "Message": "BIOS firmware update to version 10069-fixme
                  completed successfully.",
      "MessageArgs": [
        "BIOS",
        "10069-fixme"
      ],
      "MessageId": "OpenBMC.0.1.FirmwareUpdateCompleted",
      "Name": "System Event Log Entry",
      "Severity": "OK"
    },
    {
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog
                   /Entries/1581505600_2",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "2020-02-12T11:06:40+00:00",
      "EntryType": "Event",
      "Id": "1581505600_2",
      "Message": "BMC firmware panic occurred due to BMC
                  update intent.",
      "MessageArgs": [
        "BMC update intent"
      ],
      "MessageId": "OpenBMC.0.1.BMCFirmwarePanicReason",
      "Name": "System Event Log Entry",
      "Severity": "Warning"
    }

Change-Id: Ic6eb10757ba7af9e610f8563a86d9a3ec2b83a4c
Signed-off-by: Chalapathi &lt;chalapathix.venkataramashetty@intel.com&gt;
</content>
</entry>
<entry>
<title>Add WrEndPointConfig MMIO to peci_cmds</title>
<updated>2020-02-27T01:45:32+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2020-02-18T23:10:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=cc7cab726c778145f44dc3f5caee1a9655cc893e'/>
<id>urn:sha1:cc7cab726c778145f44dc3f5caee1a9655cc893e</id>
<content type='text'>
This adds WrEndPointConfig MMIO support to the peci_cmds utility.

Tested:
Ran this command:
peci_cmds WrEndpointConfigMMIO 6 0 0 0x7e 0x1a 0x0 0x224e0 0x5f5a56

and got the expected command buffer in the driver log:
[  795.207278] peci_aspeed 1e78b000.peci-bus: HEAD : 0x00011730
[  795.212980] TX : c5 00 05 00 00 00 06 00 d0 7e e0 24 02 00 00 00  .........~.$....
[  795.220556] TX : 00 00 56 5a 5f 00 a8                             ..VZ_..

Change-Id: Ibccaa8c390b89556162b7c131f7176b4883e06ec
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add WrEndPointConfig MMIO to the PECI library</title>
<updated>2020-02-27T01:45:32+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2020-02-18T23:06:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=ef7772033c6072375a845ca139da78e0c54c1318'/>
<id>urn:sha1:ef7772033c6072375a845ca139da78e0c54c1318</id>
<content type='text'>
This adds WrEndPointConfig MMIO support to the PECI library.

Tested:
Combined with the peci_cmds change, ran this command:
peci_cmds WrEndpointConfigMMIO 6 0 0 0x7e 0x1a 0x0 0x224e0 0x5f5a56

and got the expected command buffer in the driver log:
[  795.207278] peci_aspeed 1e78b000.peci-bus: HEAD : 0x00011730
[  795.212980] TX : c5 00 05 00 00 00 06 00 d0 7e e0 24 02 00 00 00  .........~.$....
[  795.220556] TX : 00 00 56 5a 5f 00 a8                             ..VZ_..

Change-Id: I991ab7b1138981cd773f7344a7ad33cbc5292e08
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Change the CapabilitiesFlags property into booleans</title>
<updated>2020-02-24T16:49:07+00:00</updated>
<author>
<name>Karthick Sundarrajan</name>
<email>karthick.sundarrajan@intel.com</email>
</author>
<published>2019-11-25T20:17:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=1a380b0a106eb9194fb271212e821141d09f0812'/>
<id>urn:sha1:1a380b0a106eb9194fb271212e821141d09f0812</id>
<content type='text'>
Each bit in CapabilitiesFlags dbus property is a chassis
capability. Setting a capability overwrites other capabilities.
Read-and-update of the property results in race condition/confusion.
To tackle this, added a boolean property for each of chassis
capability. The new properties will be read and updated in ipmi
command handling code.

The capabilities listed below are supported by Intel and so enabled
the corresponding bits/properties by default.
1. Intrusion sensor (bit 0)
2. Front panel lockout (bit 1)
3. NMI (bit 2)

The original CapabilitiesFlags property will be deprecated once the
changes are made to use new booleans in all the repos.

Tested:
------

root@intel-obmc:~# ipmitool raw 0x00 0x00
 07 22 44 66 88 aa

Change-Id: I7f9ec00c1bf94d550dd000634011ef8e7a460967
Signed-off-by: Karthick Sundarrajan &lt;karthick.sundarrajan@intel.com&gt;
</content>
</entry>
<entry>
<title>Add handling of exit code property.</title>
<updated>2020-02-20T10:51:20+00:00</updated>
<author>
<name>Agata Olender</name>
<email>agata.olender@intel.com</email>
</author>
<published>2020-02-04T13:09:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=a4f173e6e8ed11ad2d5f54b8fcd30df5443cd053'/>
<id>urn:sha1:a4f173e6e8ed11ad2d5f54b8fcd30df5443cd053</id>
<content type='text'>
Property returns exit code value from nbd-client process for
proxy mode and from nbdkit process for legacy mode.
The initial value for this property is -1 and will be returned
before starting the process and in the process execution time.

Tested manually for proxy and legacy mode:
- initial value before process first run
- initial value in process execution time
- 0 value for successful exit
- specific value for forced process termination

Change-Id: I4cefa423bade522fc2fac0cab620cbba0b66cce2
Signed-off-by: Agata Olender &lt;agata.olender@intel.com&gt;
</content>
</entry>
<entry>
<title>Increase the timeout value to fix netipmid crash issue during stress test</title>
<updated>2020-02-13T12:58:58+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2020-02-13T12:56:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=414068e084f9865a1c3dc4fc98b7be3de4cdb667'/>
<id>urn:sha1:414068e084f9865a1c3dc4fc98b7be3de4cdb667</id>
<content type='text'>
During stress test, netipmid service will crash with "bad executor" error,
the current Character Accumulate Interval is too small,
after increase it to 100, no more crash issue.

Tested:
Start "ipmitool sel list", "ipmitool sensor list"
and "ipmitool sol looptest 200 500" at the same time,
no "sol looptest fail" error

Change-Id: Idf8ba1fdc3478bda408cf668f671411a02574b68
Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add updateable association to PFR fw objects</title>
<updated>2020-02-08T14:39:25+00:00</updated>
<author>
<name>AppaRao Puli</name>
<email>apparao.puli@linux.intel.com</email>
</author>
<published>2020-01-28T21:37:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=b3a14b22bc6c5cc233c63463100d8d637edfd2f8'/>
<id>urn:sha1:b3a14b22bc6c5cc233c63463100d8d637edfd2f8</id>
<content type='text'>
All the PFR firmware objects are programmable.
So add 'updateable' associations to those objects
for fetching all programmable firmware components
in system.

Remove BMC and BIOS objects from 'functional'
association as there is redundant firmware version
objects exist for same. BMC version is fetched from
/etc/os-release and BIOS version is fetched from
SMBIOS, those will have more version information
which can't be fetched from PFR CPLD today. Down the
line we need to remove the redundant firmware version
objects and stick to one.

Tested:
 - Redfish firmware inventory shows appropriate
   'Updateable' Property values.
 - There will be single functional association
   object per component.

Change-Id: Ie5dc5cfaa7da268e0b9ea746e63bf4e9c48cf817
Signed-off-by: AppaRao Puli &lt;apparao.puli@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>[Mfg-mode]: Configure root user with null passwd</title>
<updated>2020-02-08T02:12:38+00:00</updated>
<author>
<name>Richard Marian Thomaiyar</name>
<email>richard.marian.thomaiyar@linux.intel.com</email>
</author>
<published>2020-02-05T15:26:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=dd00e1aa35fce669ad6665904dc096f1f792a96b'/>
<id>urn:sha1:dd00e1aa35fce669ad6665904dc096f1f792a96b</id>
<content type='text'>
Configure special user with null password when entering manufacturing
mode and special user password is in disabled state.

Note: This feature is under VALIDATION_UNSECURE flag, and hence
will be available for reference only image.

Tested:
1. Built the image without debug-tweaks and flashed the same
2. Confirmed that root user is not enabled during regular boot
3. Pressed power button for 15 seconds during AC Cycle, and
entered manufacturing mode
4. Able to login to root user with no password and
updated the password to new one, due to enforcement
5. Verified upon rebooting, the newly configured password can be
used to login to the serial console.
6. Entered Manufacturing mode again, to make sure root user
password is not set to null again as it is already configured.

Change-Id: I6aab8713a7c4d7d75b63b1b58ee063b09d9db990
Signed-off-by: Richard Marian Thomaiyar &lt;richard.marian.thomaiyar@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Print the completion code on error</title>
<updated>2020-02-07T20:29:44+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2020-02-03T23:38:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=fdb1caccf85564a28b8a11b6d9c1daa70886eaca'/>
<id>urn:sha1:fdb1caccf85564a28b8a11b6d9c1daa70886eaca</id>
<content type='text'>
In some cases, such as timeout, the PECI completion code can still
provide additional data, so print it along with the error code.

Tested:
peci_cmds RdPCIConfig 0 0 0
ERROR 6: command failed
   cc:0x40

Change-Id: Ib4e8cdc5f6c45e2cd873df344a4e5d2e237a98ee
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add PECI_CC_TIMEOUT response</title>
<updated>2020-02-06T16:07:45+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2020-02-03T23:36:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/provingground.git/commit/?id=915fd4bb87508f88960eb2d4e51ae1bdc454b5b0'/>
<id>urn:sha1:915fd4bb87508f88960eb2d4e51ae1bdc454b5b0</id>
<content type='text'>
If the driver times-out on a PECI call and returns ETIMEDOUT,
return a new PECI_CC_TIMEOUT response to the caller.

Tested:
Ran a PECI command with a timeout and confirmed that it returns
PECI_CC_TIMEOUT.

Change-Id: I93e25948ef05d0e7f137500310a4dfa99ed8980c
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
</feed>
