From 4a4840a304ba123a0793085b3b9d5bc2e7622cfc Mon Sep 17 00:00:00 2001 From: Stewart Smith Date: Mon, 28 May 2018 18:00:40 +1000 Subject: skiboot 5.9.9 release notes Signed-off-by: Stewart Smith (cherry picked from commit 81e58346c8b8a9f85d7b116f2d3c1b6bc724daea) Signed-off-by: Stewart Smith --- doc/release-notes/skiboot-5.9.9.rst | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/release-notes/skiboot-5.9.9.rst (limited to 'doc') diff --git a/doc/release-notes/skiboot-5.9.9.rst b/doc/release-notes/skiboot-5.9.9.rst new file mode 100644 index 00000000..81674f83 --- /dev/null +++ b/doc/release-notes/skiboot-5.9.9.rst @@ -0,0 +1,27 @@ +.. _skiboot-5.9.9: + +============= +skiboot-5.9.9 +============= + +skiboot 5.9.9 was released on Monday May 28th, 2018. It replaces +:ref:`skiboot-5.9.8` as the current stable release in the 5.9.x series. + +Over :ref:`skiboot-5.9.8`, we have two bug fixes and a build fix, they are: + +- OPAL_PCI_SET_POWER_STATE: fix locking in error paths + + Otherwise we could exit OPAL holding locks, potentially leading + to all sorts of problems later on. +- lpc: Clear pending IRQs at boot + + When we come in from hostboot the LPC master has the bus reset indicator + set. This error isn't handled until the host kernel unmasks interrupts, + at which point we get the following suprious error: :: + + [ 20.053560375,3] LPC: Got LPC reset on chip 0x0 ! + [ 20.053564560,3] LPC[000]: Unknown LPC error Error address reg: 0x00000000 + + Fix this by clearing the various error bits in the LPC status register + before we initalise the skiboot LPC bus driver. +- stb: Build fixes in constructing secure and trusted boot header -- cgit v1.2.1