mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tomasz Kvarsin" <kvarsin@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: "Ingo Molnar" <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.20-rc3-mm1: can not mount root
Date: Tue, 30 Jan 2007 12:04:40 +0300	[thread overview]
Message-ID: <5157576d0701300104j7c55c03boca274cbcd7620a3c@mail.gmail.com> (raw)
In-Reply-To: <20070130001209.b716c14a.akpm@osdl.org>

On 1/30/07, Andrew Morton <akpm@osdl.org> wrote:
> 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:
> >
> > _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 ?? ()
>
> Tomasz, is this still happening in 2.6.20-rc6-mm3?
>

Have no idea, I tryied to test 2.6.20-rc6-mm2, but
build failed, I will try -mm3.

> err.  We merged that patch.  So perhaps 2.6.20-rc6 now crashes in the same
> manner?
>
>

Actually there is solution by Vivek Goyal
>
> -int tsc_disable __cpuinitdata = 0;
> +int tsc_disable = 0;

if you merge his patch also all should be fine.

  parent reply	other threads:[~2007-01-30  9:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 14:20 Tomasz Kvarsin
2007-01-05 17:42 ` Tomasz Kvarsin
2007-01-05 18:49 ` Andrew Morton
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 [this message]
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=5157576d0701300104j7c55c03boca274cbcd7620a3c@mail.gmail.com \
    --to=kvarsin@gmail.com \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®