Kernel panic booting in QEMU

Bug #683217 reported by Paul Larson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-linaro (Ubuntu)
New
High
John Rigby

Bug Description

I have an automated job that tests the latest image under qemu. The most recent one I tested before this was in the 10.05 daily images from a few days back. On the 20101130 image, I hit this panic during boot with qemu-maemo:

[ 0.000000] Linux version 2.6.35-1008-linaro-omap (buildd@hawthorn) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #15-Ubuntu Fri Oct 22 11:56:29 UTC 2010 (Ubuntu 2.6.35-1008.15-linaro-omap 2.6.35.7
...
10:31:50
[ 0.000000] Kernel command line: console=tty0 console=ttyS2,115200n8 root=UUID=d7b85a1f-f156-4704-88ae-1022f1fa8cff rootwait ro earlyprintk fixrtc nocompcache vram=12M omapfb.debug=y omapfb.mode=dvi:1280x720MR-16@60
...
10:32:03 Begin: Running /scripts/init-bottom ... done.

10:32:04 /init: exec: line 331: run-init: Unknown error 29666828

10:32:04 [ 12.976226] Kernel panic - not syncing: Attempted to kill init!

10:32:04 [ 12.978088] [<c0055be4>] (unwind_backtrace+0x0/0x100) from [<c050e8f8>] (dump_stack+0x18/0x1c)

10:32:04 [ 12.979034] [<c050e8f8>] (dump_stack+0x18/0x1c) from [<c050e968>] (panic+0x6c/0xe4)

10:32:04 [ 12.979919] [<c050e968>] (panic+0x6c/0xe4) from [<c0084d64>] (forget_original_parent+0x2a0/0x2b0)

10:32:04 [ 12.980804] [<c0084d64>] (forget_original_parent+0x2a0/0x2b0) from [<c0084d90>] (exit_notify+0x1c/0x13c)

10:32:04 [ 12.988677] [<c0084d90>] (exit_notify+0x1c/0x13c) from [<c0085018>] (do_exit+0x168/0x318)

10:32:04 [ 12.995178] [<c0085018>] (do_exit+0x168/0x318) from [<c008520c>] (do_group_exit+0x44/0xb4)

10:32:04 [ 13.001953] [<c008520c>] (do_group_exit+0x44/0xb4) from [<c0085294>] (sys_exit_group+0x18/0x20)

10:32:04 [ 13.008697] [<c0085294>] (sys_exit_group+0x18/0x20) from [<c004e180>] (ret_fast_syscall+0x0/0x30)

Paul Larson (pwlars)
Changed in linux-linaro (Ubuntu):
importance: Undecided → High
assignee: nobody → John Rigby (jcrigby)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.