The APAR is VM63943. Our use of VM doesn't fit the normal mold, so I am not surprised that you haven't run into it. We have another LPAR that had been running 5.2 for Linux guests since last March, and it has never encountered any of the show-stopper problems we ran into on our main system. This one, fortunately, was not a show-stopper. We did not have to revert to 4.4 because of it.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] > Behalf Of Brian Nielsen > Sent: Wednesday, September 13, 2006 10:26 AM > To: [email protected] > Subject: Re: LPAR Frozen with HIGH CPU > > > Do you have a PTF/APAR number? I've been running z/VM 5.2 > with SLU 0501 = > > since March and havn't encountered this problem. (Our last > IPL was June = > > 3rd.) > > Brian Nielsen > > On Wed, 13 Sep 2006 09:48:26 -0700, Schuh, Richard > <[EMAIL PROTECTED]> wrot= > e: > > >Are you sure that you are not on 5.2? :-) > > > >We recently had something like this happen on a 5.2 system; > however, it = > > apparently was a result of the conversion to 64-bit CP and > not applicable= > > to 5.1. It was a 2GB line issue. Because of a memory leak > below the 2G = > > line, CP was finding it difficult to locate two adjacent > pages and was = > > looping. When it got to the point that all 5 cpus were in the same > condition, the system was dead. We lost, in order, VTAM, VMSECURE, > OPERATOR, and TCPIP as the system slowly ground to a halt. A > RESTART dump= > > enabled IBM to identify the problem. Our failure occurred > early in our = > > fourth day of running 5.2. It has now been almost 1 month > since our last = > > IPL, so the leak appears to have been plugged. >
