| 1 |
On Thursday 15 Mar 2012 19:36:16 Paul Hartman wrote: |
| 2 |
> On Thu, Mar 15, 2012 at 2:25 PM, Michael Mol <mikemol@×××××.com> wrote: |
| 3 |
> > On Thu, Mar 15, 2012 at 3:17 PM, Mick <michaelkintzios@×××××.com> wrote: |
| 4 |
> >> On Thursday 15 Mar 2012 17:02:15 Michael Mol wrote: |
| 5 |
> >>> On Thu, Mar 15, 2012 at 12:55 PM, Jarry <mr.jarry@×××××.com> wrote: |
| 6 |
> >>> > On 14-Mar-12 19:41, ZHANG, Le wrote: |
| 7 |
> >>> >> > So my question is: Can I somehow deliberately trigger |
| 8 |
> >>> >> > "kernel panic" (or "kernel oops")? |
| 9 |
> >>> >> |
| 10 |
> >>> >> For panic, echo c > /proc/sysrq-trigger |
| 11 |
> >>> > |
| 12 |
> >>> > After I issued the above mentioned command, my system |
| 13 |
> >>> > instantly "froze to death". Nothing changed on screen, |
| 14 |
> >>> > no "kernel panic" or "Ooops" screen. Just frozen... |
| 15 |
> >>> > |
| 16 |
> >>> > No reaction to keyboard or mouse. No auto-reboot either. |
| 17 |
> >>> > The only thing I could do is to press "Reset". Not exactly |
| 18 |
> >>> > what I have been expecting... |
| 19 |
> >>> |
| 20 |
> >>> Were you running under X? The panic would have killed X, which |
| 21 |
> >>> wouldn't have released control over the video hardware. |
| 22 |
> >>> |
| 23 |
> >>> There's a SysRq sequence to get around this, but I don't remember it. |
| 24 |
> >> |
| 25 |
> >> Ctrl+Alt+ |
| 26 |
> >> |
| 27 |
> >> R E I S U B |
| 28 |
> >> |
| 29 |
> >> (busier in reverse) |
| 30 |
> >> |
| 31 |
> >> After a E or I you should be back into a console, unless things are |
| 32 |
> >> badly screwed. |
| 33 |
> > |
| 34 |
> > Is that Ctrl+Alt+SysRq+(R E I S U B), or is the SysRq key not actually |
| 35 |
> > used? |
| 36 |
> |
| 37 |
> Sysrq is definitely required :) Ctrl, on the other hand, is optional. |
| 38 |
> And AltGr may be substituted for Alt. |
| 39 |
|
| 40 |
Oops! yes, I meant to write SysRq ... sorry! |
| 41 |
-- |
| 42 |
Regards, |
| 43 |
Mick |
Archives