It's not that it's stopping because of a console event, it's just dropping dead at the OS level and I can't even bring it back with the console.
-m On Mon, Jun 24, 2002 at 06:16:38PM -0700, John Alvord wrote: > There used to be a command... something like CP SET RUN ON which would > let the virtual machine continue processing after a console > interrupt... > > john alvord > > > On Mon, 24 Jun 2002 15:34:02 -0400, Mike Kershaw > <[EMAIL PROTECTED]> wrote: > > >On Mon, Jun 24, 2002 at 09:34:39AM -0400, Coffin Michael C wrote: > >> Hi Mike, > >> > >> When your Linux/390 guest is in CP READ mode, have you tried entering "B" > >> (for BEGIN) to see if the virtual machine resumes running? If you have, and > >> your guest does NOT start running, you should see some CP error messages > >> about why it hasn't started - that might be a good place to start. > >> > > > >No - once it drops dead I go over to the console and whack enter to see > >what's going on, and it drops into CP. I do 'B' to begin it again, and > >it does nothing - no errors, no system. Hit enter again, and it drops into > >CP again. Repeat. It basically stops handling remote OR console input and > >as soon as you try to pass it console data it drops into CP. > > > >No errors anywhere. It just drops dead. > > > >> If entering "B" gets your system back up and running - it probably means > >> somebody pressed ENTER on the virtual machine console (either a logged on > >> console, or via SCIF) causing the virtual machine to go into a CP READ. > >> That's something you'll have to address with your staff if you find it to be > >> the case. > > > >Yeah - I'm VM savvy enough to have thought of that one, this is actually just > >on my test system running on my own console. > > > >I've tried it with the console attached and disconnected. > > > >-m > > > >> > >> > >> -----Original Message----- > >> From: Mike Kershaw [mailto:[EMAIL PROTECTED]] > >> Sent: Thursday, June 20, 2002 12:31 PM > >> To: [EMAIL PROTECTED] > >> Subject: 2.4.17-may timer pop problems > >> > >> > >> I'm running 2.4.17-may with the no timer patch, qdio, and guest lans. > >> > >> I've noticed it has the highly unfortunate tendency to just completely drop > >> dead with no errors on the console. The console drops into CP READ on any > >> attempt to interact with the linux/390 system, and will not resume. a re-IPL > >> is the only route left. > >> > >> No panic message or anything useful. > >> > >> It doesn't seem to be load dependent - happens fully idle, happens in the > >> middle of compiling. Happens doing network traffic, happens sitting there > >> doing nothing, happens with the console attached and with the console > >> disconnected (hey, it was worth a shot). Usually happens within 15-25 > >> minutes of IPL. > >> > >> Anyone else encounter this? > >> > >> -m > >> > >> -- > >> Michael Kershaw > >> [EMAIL PROTECTED] > >> Linux Systems Programmer, Information Technology > >> > >> "Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash -- Michael Kershaw [EMAIL PROTECTED] Linux Systems Programmer, Information Technology "Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash
