Simon,
Dump triggers is certainly a thing of interest to us. But not just a
keyboard sequence, and API call and in fact the ability to dump from any
code path. That latter can be achieved today using DProbes to trigger a
dump. What we're considering is enhancing lkcd to be able to let the system
continue to run having invoked a dump for non-crash reasons.
Question: what's the right key sequence?
Presumably there's no definitive answer. In which case we need a
configurable sequence. See any problems with that?
Richard
Richard Moore - RAS Project Lead - Linux Technology Centre (ATS-PIC).
http://oss.software.ibm.com/developerworks/opensource/linux
Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183
IBM UK Ltd, MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK
Simon Falvey <simon.falvey@xxxxxxxxxxx>@oss.sgi.com on 01/08/2001 08:39:25
Please respond to Simon Falvey <simon.falvey@xxxxxxxxxxx>
Sent by: owner-lkcd@xxxxxxxxxxx
To: "'lkcd@xxxxxxxxxxx'" <lkcd@xxxxxxxxxxx>
cc:
Subject: LKCD in mainstream release?
Hi all,
Does any one have any idea when we can expect lkcd in the main kernel
release? It seems to be pretty stable now.
Also has anyone considered putting a hook into the SysRq key sequence
to get it to crash on demand? I put one in on my system and find it very
useful in diagnosing hangs.
Simon