1.. _skiboot-5.1.19: 2 3skiboot-5.1.19 4-------------- 5 6skiboot-5.1.19 was released on Monday 16th January 2017. 7 8skiboot-5.1.19 is the 20th stable release of 5.1, it follows skiboot-5.1.18 9(which was released 26th August 2016). 10 11This release contains a few minor bug fixes. 12 13Changes are: 14 15Generic: 16 17- Makefile: Disable stack protector due to gcc problems 18- stack: Don't recurse into __stack_chk_fail 19- Makefile: Use -ffixed-r13 20 We did not find evidence of this ever being a problem, but this fix 21 is good and preventative. 22- Limit number of "Poller recursion detected" errors to display 23 In some error conditions, we could spiral out of control on this 24 and spend all of our time printing the exact same backtrace. 25 Limit it to 16 times, because 16 is a nice number. 26 27FSP based Systems: 28 29- fsp: Don't recurse pollers in ibm_fsp_terminate 30 If we were to terminate in a poller, we'd call op_display() which 31 called pollers which hit the recursive poller warning, which ended 32 in not much fun at all. 33 34PCI: 35 36- hw/phb3: set PHB retry state correctly when fresetting during a creset 37- phb3: Lock the PHB on set_xive callbacks 38 Those are called by the interrupts core and thus skip the locking 39 implicit in the PCI opal calls. 40- hw/{phb3, p7ioc}: Return success for freset on empty PHB 41 OPAL_CLOSED is returned when fundamental reset is issued on the 42 PHB who doesn't have subordinate devices (root port excluded). 43 The kernel raises an error message, which is unnecessary. This 44 returns OPAL_SUCCESS for this case to avoid the error message. 45- hw/phb3: fix error handling in complete reset 46 During a complete reset, when we get a timeout waiting for pending 47 transaction in state PHB3_STATE_CRESET_WAIT_CQ, we mark the PHB as broken 48 and return OPAL_PARAMETER. 49 Change the return code to OPAL_HARDWARE which is way more sensible, and set 50 the state to PHB3_STATE_FENCED so that the kernel can retry the complete 51 reset. 52