installation to USB device results in a non-booting system with OOPS
Bug #562343 reported by
Oliver Grawert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-ti-omap (Ubuntu) |
Invalid
|
High
|
Amit Kucheria | ||
Lucid |
Invalid
|
High
|
Amit Kucheria |
Bug Description
currently booting a newly installed system from USB key results in a kernel oops on boot, while the system moves on i dont get to a final console which indicates the system gets stuck at filesystem access at some point.
boot log attached...
To post a comment you must log in.
The interesting parts of the log are:
[ 26.668640] Kernel panic - not syncing: Attempted to kill init! backtrace+ 0x0/0xe8) from [<c0422b24>] (panic+0x44/0x120) original_ parent+ 0x27c/0x294) original_ parent+ 0x27c/0x294) from [<c00633dc>] (exit_notify+ 0x14/0x158) 0x14/0x158) from [<c006366c>] (do_exit+ 0x14c/0x2f8) 0x14c/0x2f8) from [<c0063854>] (do_group_ exit+0x3c/ 0xac) exit+0x3c/ 0xac) from [<c00638d4>] (sys_exit_ group+0x10/ 0x18) group+0x10/ 0x18) from [<c0032a00>] (ret_fast_ syscall+ 0x0/0x2c)
[ 26.674804] [<c0039664>] (unwind_
[ 26.683166] [<c0422b24>] (panic+0x44/0x120) from [<c00633b0>] (forget_
[ 26.692230] [<c00633b0>] (forget_
[ 26.701812] [<c00633dc>] (exit_notify+
[ 26.710083] [<c006366c>] (do_exit+
[ 26.718414] [<c0063854>] (do_group_
[ 26.727203] [<c00638d4>] (sys_exit_
Tracing through forget_ original_ parent, we call find_new_reaper() which eventually calls panic() as we see above.
if (unlikely( pid_ns- >child_ reaper == father)) { unlock_ irq(&tasklist_ lock);
write_
if (unlikely(pid_ns == &init_pid_ns))
panic("Attempted to kill init!");
zap_pid_ ns_processes( pid_ns) ; lock_irq( &tasklist_ lock); original_ parent( ) must move them somewhere. >child_ reaper = init_pid_ ns.child_ reaper;
write_
/*
* We can not clear ->child_reaper or leave it alone.
* There may by stealth EXIT_DEAD tasks on ->children,
* forget_
*/
pid_ns-
}
So the suspicion is that /sbin/init exits.