diff options
author | Angelos Mouzakitis <a.mouzakitis@virtualopensystems.com> | 2023-10-10 14:33:42 +0000 |
---|---|---|
committer | Angelos Mouzakitis <a.mouzakitis@virtualopensystems.com> | 2023-10-10 14:33:42 +0000 |
commit | af1a266670d040d2f4083ff309d732d648afba2a (patch) | |
tree | 2fc46203448ddcc6f81546d379abfaeb323575e9 /roms/skiboot/doc/release-notes/skiboot-5.9.6.rst | |
parent | e02cda008591317b1625707ff8e115a4841aa889 (diff) |
Change-Id: Iaf8d18082d3991dec7c0ebbea540f092188eb4ec
Diffstat (limited to 'roms/skiboot/doc/release-notes/skiboot-5.9.6.rst')
-rw-r--r-- | roms/skiboot/doc/release-notes/skiboot-5.9.6.rst | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/roms/skiboot/doc/release-notes/skiboot-5.9.6.rst b/roms/skiboot/doc/release-notes/skiboot-5.9.6.rst new file mode 100644 index 000000000..0be7c5300 --- /dev/null +++ b/roms/skiboot/doc/release-notes/skiboot-5.9.6.rst @@ -0,0 +1,30 @@ +.. _skiboot-5.9.6: + +============= +skiboot-5.9.6 +============= + +skiboot 5.9.6 was released on Friday December 15th, 2017. It replaces +:ref:`skiboot-5.9.5` as the current stable release in the 5.9.x series. + +Over :ref:`skiboot-5.9.5`, we have a few bug fixes, they are: + +- sensors: occ: Skip counter type of sensors + + Don't add counter type of sensors to device-tree as they don't + fit into hwmon sensor interface. +- p9_stop_api updates to support IMC across deep stop states. +- opal/xscom: Add recovery for lost core wakeup scom failures. + + Due to a hardware issue where core responding to scom was delayed due to + thread reconfiguration, leaves the SCOM logic in a state where the + subsequent scom to that core can get errors. This is affected for Core + PC scom registers in the range of 20010A80-20010ABF + + The solution is if a xscom timeout occurs to one of Core PC scom registers + in the range of 20010A80-20010ABF, a clearing scom write is done to + 0x20010800 with data of '0x00000000' which will also get a timeout but + clears the scom logic errors. After the clearing write is done the original + scom operation can be retried. + + The scom timeout is reported as status 0x4 (Invalid address) in HMER[21-23]. |