The circumvention of using the TRACE PROG 28 did not work for us. We had some servers that failed and could not re-boot - most likely related to the trace being active. We are booting Linux back to the older kernel level that was not experiencing the problem - 2.6.32-696.18.7.el6.s390x. Clearly there seems to be something on those late kernel patches that makes the servers susceptible to this problem. I am also pushing to get at least one LPAR IPLed with VM65414 installed.
Rick Barlow On Thu, Apr 12, 2018 at 10:53 AM, Bill Bitner <bitn...@us.ibm.com> wrote: > > <snip> > > The real solution is to apply VM65414's PTF which is available. A > mitigation would be to do a CP TRACE PROG 28 NOTERM NOPRINT RUN for the > virtual machines through the console or if logged off and on, through a > directory command statement. > > Thank you for understanding the communication challenges in this space. I'm > sure you'll let us know if you need more info. :-) > > Regards, > Bill > ____________________________________________________________ > _______________________________ > > Bill Bitner - z/VM Customer Focus and Care - 607-429-3286 > bitn...@us.ibm.com > "Making systems practical and profitable for customers through > virtualization and its exploitation." - z/VM > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
