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.
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. Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-3123 [EMAIL PROTECTED] -----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
