#5809 NORM Never A: Ctrl-alt-Fn-Erase produces "kernel panic - not syncing: Attempted to kill init!"

[Zarro Boogs per Child]

#5809: Ctrl-alt-Fn-Erase produces "kernel panic - not syncing: Attempted to kill
init!"
--------------------+-------------------------------------------------------
 Reporter:  gnu     |       Owner:  dilinger      
     Type:  defect  |      Status:  new           
 Priority:  normal  |   Milestone:  Never Assigned
Component:  kernel  |     Version:  Build 650     
 Keywords:          |    Verified:  0             
 Blocking:          |   Blockedby:                
--------------------+-------------------------------------------------------
 Build 650, Q2D07.

 Boot the machine.  When it comes up in the donut, switch to the first text
 console with ctrl-alt-f1.  To that screen, type ctrl-alt-fn-erase.
 Response:

 [  193.388835] Kernel panic - not syncing: Attempted to kill init!

 then later

 [  280.000970] atkbd.c: Spurious ACK on isa0060/serio0. Some program might
 be trying to access hardware directly.

 It never actually does shut down or reboot; it just hangs.  My only
 recourse seemed to be a 4-second power-off.

 (I was looking for a ctrl-alt-delete combination that would make it
 reboot, upon request from donor in rt# 3198.)

 When I did this key combination at a Sugar screen, the system stopped
 responding (no mouse tracking, no ctrl-alt-F1, etc) but produced no other
 indication of what had happened.

 When I did this key combination during the startup scripts (Starting udev,
 etc), I get the same panic message and hang.

 (Does this occur because we're running a weird Python process as pid 1,
 rather than the real init?)

-- 
Ticket URL: <http://dev.laptop.org/ticket/5809>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system