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