Created attachment 390482 [details] boot log Description of problem: Kernel panics on boot in KVM. Used netinst.iso from: http://alt.fedoraproject.org/pub/alt/stage/13-Alpha.TC1/Fedora/x86_64/iso/ Error: ============================================= [ INFO: possible recursive locking detected ] 2.6.33-0.40.rc7.git0.fc13.x86_64 #1 --------------------------------------------- sh/241 is trying to acquire lock: (&bdev->bd_mutex){+.+.+.}, at: [<ffffffff81144c5d>] __blkdev_put+0x34/0x16c but task is already holding lock: (&bdev->bd_mutex){+.+.+.}, at: [<ffffffff81144c5d>] __blkdev_put+0x34/0x16c other info that might help us debug this: 1 lock held by sh/241: #0: (&bdev->bd_mutex){+.+.+.}, at: [<ffffffff81144c5d>] __blkdev_put+0x34/0x16c stack backtrace: Pid: 241, comm: sh Not tainted 2.6.33-0.40.rc7.git0.fc13.x86_64 #1 Call Trace: [<ffffffff8107eb05>] __lock_acquire+0xca2/0xd19 [<ffffffff81015238>] ? save_stack_trace+0x2f/0x4c [<ffffffff8107c5ae>] ? save_trace+0x3f/0xab [<ffffffff8107c698>] ? add_lock_to_list+0x7e/0xc3 [<ffffffff8107ec58>] lock_acquire+0xdc/0x102 [<ffffffff81144c5d>] ? __blkdev_put+0x34/0x16c [<ffffffff81144c5d>] ? __blkdev_put+0x34/0x16c [<ffffffff81475fcf>] __mutex_lock_common+0x4b/0x392 [<ffffffff81144c5d>] ? __blkdev_put+0x34/0x16c [<ffffffff81145417>] ? spin_unlock.clone.2+0x15/0x17 [<ffffffff810712ea>] ? sched_clock_cpu+0xc3/0xce [<ffffffff8107bc6e>] ? trace_hardirqs_off+0xd/0xf [<ffffffff81071338>] ? cpu_clock+0x43/0x5e [<ffffffff8107bc81>] ? lockstat_clock+0x11/0x13 [<ffffffff814763da>] mutex_lock_nested+0x3e/0x43 [<ffffffff81144c5d>] __blkdev_put+0x34/0x16c [<ffffffff81477d9b>] ? _raw_spin_unlock+0x2b/0x2f [<ffffffff81144da5>] blkdev_put+0x10/0x12 [<ffffffff81145de4>] close_bdev_exclusive+0x24/0x2c [<ffffffff81120e29>] kill_block_super+0x3a/0x3f [<ffffffff81121561>] deactivate_super+0x5b/0x72 [<ffffffff81135137>] mntput_no_expire+0xb2/0xe8 [<ffffffff8111fe4a>] __fput+0x1c8/0x1d7 [<ffffffff8111fe73>] fput+0x1a/0x1c [<ffffffff812f9c70>] loop_clr_fd+0x1b1/0x1bf [<ffffffff812fa328>] lo_release+0x47/0x71 [<ffffffff81144cbe>] __blkdev_put+0x95/0x16c [<ffffffff81477d9b>] ? _raw_spin_unlock+0x2b/0x2f [<ffffffff81144da5>] blkdev_put+0x10/0x12 [<ffffffff81145de4>] close_bdev_exclusive+0x24/0x2c [<ffffffff81120e29>] kill_block_super+0x3a/0x3f [<ffffffff81121561>] deactivate_super+0x5b/0x72 [<ffffffff81135137>] mntput_no_expire+0xb2/0xe8 [<ffffffff8111fe4a>] __fput+0x1c8/0x1d7 [<ffffffff8111fe73>] fput+0x1a/0x1c [<ffffffff810f7d65>] remove_vma+0x56/0x8c [<ffffffff810f7e9b>] exit_mmap+0x100/0x122 [<ffffffff8104dc28>] mmput+0x5e/0xcf [<ffffffff810523c0>] exit_mm+0x111/0x11e [<ffffffff81053e94>] do_exit+0x228/0x7a5 [<ffffffff8107bc81>] ? lockstat_clock+0x11/0x13 [<ffffffff81477d0e>] ? _raw_spin_unlock_irq+0x30/0x3c [<ffffffff81054495>] do_group_exit+0x84/0xb0 [<ffffffff810630e5>] get_signal_to_deliver+0x395/0x3b4 [<ffffffff81009001>] do_signal+0x72/0x6bc [<ffffffff8107d3a6>] ? trace_hardirqs_on_caller+0x111/0x135 [<ffffffff8107d3d7>] ? trace_hardirqs_on+0xd/0xf [<ffffffff812c205c>] ? tty_ldisc_deref+0xe/0x10 [<ffffffff812bab1c>] ? tty_read+0x8c/0xc5 [<ffffffff81009d09>] ? sysret_signal+0x5/0x4e [<ffffffff81009673>] do_notify_resume+0x28/0x86 [<ffffffff81009fc1>] int_signal+0x12/0x17 sh used greatest stack depth: 3656 bytes left init used greatest stack depth: 3384 bytes left Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.33-0.40.rc7.git0.fc13.x86_64 #1 Call Trace: [<ffffffff81474ab6>] panic+0x7a/0x142 [<ffffffff81054014>] ? do_exit+0x3a8/0x7a5 [<ffffffff81053ce7>] do_exit+0x7b/0x7a5 [<ffffffff814771c1>] ? lockdep_sys_exit_thunk+0x35/0x67 [<ffffffff81054495>] do_group_exit+0x84/0xb0 [<ffffffff810544d8>] sys_exit_group+0x17/0x1b [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b Version-Release number of selected component (if applicable): 2.6.33-0.40.rc7.git0.fc13.x86_64 How reproducible: always Additional information: Full log attached.
Kamil, are you observing this with F-13-Alpha-TC2? http://serverbeach1.fedoraproject.org/pub/alt/stage/13-Alpha.TC2/Fedora/
No, F13 Alpha TC2 boots ok, no kernel panic occurred.
Well, I think even on TC2 I still see this traceback, but only after Anaconda installation has finished and the computer restarts. It does not halt the computer in any way, the traceback just flashes through the console and the computer restarts immediately. So it does not cause any problems, but it's still there.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.