From ff65dc98df8acbc4d3d21e8d9a47fa538a61685c Mon Sep 17 00:00:00 2001 From: Stewart Smith Date: Wed, 29 Nov 2017 11:07:03 +1100 Subject: skiboot 5.9.4 release notes Signed-off-by: Stewart Smith (cherry picked from commit 1a1a2bd43829dc49c63fda07c569fbfcb73353a5) Signed-off-by: Stewart Smith --- doc/release-notes/skiboot-5.9.4.rst | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/release-notes/skiboot-5.9.4.rst (limited to 'doc') diff --git a/doc/release-notes/skiboot-5.9.4.rst b/doc/release-notes/skiboot-5.9.4.rst new file mode 100644 index 0000000..a222f21 --- /dev/null +++ b/doc/release-notes/skiboot-5.9.4.rst @@ -0,0 +1,26 @@ +.. _skiboot-5.9.4: + +============= +skiboot-5.9.4 +============= + +skiboot 5.9.4 was released on Wednesday November 29th, 2017. It replaces +:ref:`skiboot-5.9.3` as the current stable release in the 5.9.x series. + +Over :ref:`skiboot-5.9.3`, we have one NPU2/NVLink2 fix that works around +a potential glitch (the one :ref:`skiboot-5.9.3` would hard crash on rather +than let a system continue to run until it mysteriously crashed later on). + +That fix is in two parts: + +- npu2: hw-procedures: Change phy_rx_clock_sel values to recover from a + potential glitch. + +- npu2: hw-procedures: Manipulate IOVALID during training + + Ensure that the IOVALID bit for this brick is raised at the start of + link training, in the reset_ntl procedure. + + Then, to protect us from a glitch when the PHY clock turns off or gets + chopped, lower IOVALID for the duration of the phy_reset and + phy_rx_dccal procedures. -- cgit v1.1