From: Andrew Morton <akpm@osdl.org>
To: "Tomasz Kvarsin" <kvarsin@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.20-rc3-mm1: can not mount root
Date: Fri, 5 Jan 2007 10:49:27 -0800 [thread overview]
Message-ID: <20070105104927.b2dfd2d7.akpm@osdl.org> (raw)
In-Reply-To: <5157576d0701050620l14fd0a6emdf5793c5214931a8@mail.gmail.com>
On Fri, 5 Jan 2007 17:20:38 +0300
"Tomasz Kvarsin" <kvarsin@gmail.com> wrote:
> I can not boot machine with 2.6.20-rc3-mm1 and 2.6.20-rc2-mm1.
> I made binary search, patch bellow cause this bug:
> $quilt top
> patches/sched-improve-sched_clock-on-i686.patch
>
> backtrace which I got by connecting "gdb" to machine:
How did you manage to use gdb on an i386 kernel? Using qemu or something?
> _raw_spin_lock (lock=0xc06c0c60) at lib/spinlock_debug.c:108
> 108 for (i = 0; i < loops; i++) {
> (gdb) bt
> #0 _raw_spin_lock (lock=0xc06c0c60) at lib/spinlock_debug.c:108
> #1 0xc056ac42 in _spin_lock (lock=0xc06c0c60) at kernel/spinlock.c:182
> #2 0xc011c3bb in vprintk (fmt=0xc0649c00 "<0>BUG: spinlock %s on
> CPU#%d, %s/%d\n",
> args=0xc1167a84 "") at kernel/printk.c:534
> #3 0xc011c6c7 in printk (fmt=0xc0649c00 "<0>BUG: spinlock %s on
> CPU#%d, %s/%d\n")
> at kernel/printk.c:508
> #4 0xc027be42 in spin_bug (lock=0xc06c0c60, msg=0xc065fc00
> "recursion") at lib/spinlock_debug.c:61
> #5 0xc027c178 in _raw_spin_lock (lock=0xc06c0c60) at lib/spinlock_debug.c:79
> #6 0xc056ac42 in _spin_lock (lock=0xc06c0c60) at kernel/spinlock.c:182
> #7 0xc011c3bb in vprintk (fmt=0xc0626ed0 "<1>BUG: unable to handle
> kernel paging request",
> args=0xc1167b8c "") at kernel/printk.c:534
> #8 0xc011c6c7 in printk (fmt=0xc0626ed0 "<1>BUG: unable to handle
> kernel paging request")
> at kernel/printk.c:508
> #9 0xc0116de4 in do_page_fault (regs=0xc1167bcc, error_code=0) at
> arch/i386/mm/fault.c:555
> #10 0xc056b11c in page_fault ()
> #11 0xc0808160 in ?? ()
> #12 0xc0626ed0 in kallsyms_token_index ()
> #13 0xc1167cac in ?? ()
> #14 0x00000001 in ?? ()
> #15 0xc0808163 in printk_buf.19225 ()
> #16 0xc1167c0c in ?? ()
> #17 0x00000000 in ?? ()
It looks like the machine was trying to oops, only it gets stuck on
logbuf_lock. Perhaps it hit an oops while running printk_clock() inside
vprintk() then tried to go recursive.
oopses while holding logbuf_lock are rare, and appear to be fatal. Perhaps
we should ignore logbuf_lock if oops_in_progress, but the chances are we'll
just hit the same oops again..
Do you have "time" on the kernel boot command line? If so, does removing
that option make the hang go away?
next prev parent reply other threads:[~2007-01-05 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 14:20 [BUG] 2.6.20-rc3-mm1: can not mount root Tomasz Kvarsin
2007-01-05 17:42 ` Tomasz Kvarsin
2007-01-05 18:49 ` Andrew Morton [this message]
2007-01-05 19:41 ` Tomasz Kvarsin
2007-01-30 8:12 ` Andrew Morton
2007-01-30 8:22 ` Ingo Molnar
2007-01-30 8:30 ` Ingo Molnar
2007-01-30 14:48 ` Tomasz Kvarsin
2007-01-30 9:04 ` Tomasz Kvarsin
2007-01-30 14:45 ` Tomasz Kvarsin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070105104927.b2dfd2d7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kvarsin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox