On Fri, 2006-04-28 at 12:30 +0200, Rob van der Heij wrote: > On 4/28/06, Peter 1 Oberparleiter <[EMAIL PROTECTED]> wrote: > > > Note that the vmhalt function is only triggered after a user-initiated > > system halt (meaning 'shutdown -h' or equivalent actions). Specifically > > vmhalt will not be called after a kernel panic. > > Bummer! I guess that's a memory fault on my side then... > > Don't you agree it would be extremely useful to have a vmoops= > function then? If the kernel is still vital enough to show a trace > back and what have you, then I would be able to issue a diag8 (even > ignoring the response). The alternative is that people set up separate > things to monitor for servers sitting in CP READ (like HMF can do) or > watch the console with SCIF, or simply issue SEND CP xx IPL to any > Linux that appears to be unresponsive... :-(
Yes, I have heard that and similar needs from various sides now. Our testers for example would like to have a way to do an automatic dump as well. Trouble is how do we get to a consistent interface, one that is usable under z/VM and under LPAR? How do we specificy the dump device? A vmoops analog to vmhalt would solved the problem just for z/VM. We should be able to come up with a general interface for z/VM and LPAR, something along the lines of /sys/firmware/ipl. -- blue skies, Martin. Martin Schwidefsky Linux for zSeries Development & Services IBM Deutschland Entwicklung GmbH "Reality continues to ruin my life." - Calvin. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
