On 1/30/07, Andrew Morton <[email protected]> wrote:
On Fri, 5 Jan 2007 17:20:38 +0300
"Tomasz Kvarsin" <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]