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