On Thursday 15 Mar 2012 19:36:16 Paul Hartman wrote: > On Thu, Mar 15, 2012 at 2:25 PM, Michael Mol <[email protected]> wrote: > > On Thu, Mar 15, 2012 at 3:17 PM, Mick <[email protected]> wrote: > >> On Thursday 15 Mar 2012 17:02:15 Michael Mol wrote: > >>> On Thu, Mar 15, 2012 at 12:55 PM, Jarry <[email protected]> wrote: > >>> > On 14-Mar-12 19:41, ZHANG, Le wrote: > >>> >> > So my question is: Can I somehow deliberately trigger > >>> >> > "kernel panic" (or "kernel oops")? > >>> >> > >>> >> For panic, echo c > /proc/sysrq-trigger > >>> > > >>> > After I issued the above mentioned command, my system > >>> > instantly "froze to death". Nothing changed on screen, > >>> > no "kernel panic" or "Ooops" screen. Just frozen... > >>> > > >>> > No reaction to keyboard or mouse. No auto-reboot either. > >>> > The only thing I could do is to press "Reset". Not exactly > >>> > what I have been expecting... > >>> > >>> Were you running under X? The panic would have killed X, which > >>> wouldn't have released control over the video hardware. > >>> > >>> There's a SysRq sequence to get around this, but I don't remember it. > >> > >> Ctrl+Alt+ > >> > >> R E I S U B > >> > >> (busier in reverse) > >> > >> After a E or I you should be back into a console, unless things are > >> badly screwed. > > > > Is that Ctrl+Alt+SysRq+(R E I S U B), or is the SysRq key not actually > > used? > > Sysrq is definitely required :) Ctrl, on the other hand, is optional. > And AltGr may be substituted for Alt.
Oops! yes, I meant to write SysRq ... sorry! -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
