Reuben Farrelly <[email protected]> wrote:
>
> ...
>
> Some bad stuff seems to be happening here (this is new to -mm2; -mm1 did not
> have this problem).
>
> It's 100% reproduceable, although seems to happen at slightly different places
> in the bootup, especially at the end. Did I miss a patch for this?
>
Why do you keep breaking my kernel?
> ...
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [<c0103ad0>] dump_stack+0x17/0x19
> [<c01cab4b>] spin_bug+0x5b/0x67
> [<c01cac9c>] _raw_spin_lock+0x78/0x7a
> [<c0314ad9>] _spin_lock+0x8/0xa
> [<c0313370>] schedule+0x6c0/0xd68
> [<c0100d31>] cpu_idle+0x64/0x66
> [<c01002c5>] rest_init+0x25/0x27
> [<c03fe8af>] start_kernel+0x154/0x167
> [<c010020f>] 0xc010020f
> Kernel panic - not syncing: bad locking
That's odd - we lost a printk there:
printk("BUG: spinlock %s on CPU#%d, %s/%d, %p\n", msg,
smp_processor_id(), current->comm, current->pid, lock);
which is a shame, because it would have told us stuff. Do you have any
traces which do have that message?
Anyway, scary trace. It look like some spinlock is thought to be in the
wrong state in schedule(). Send the .config, please.
-
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]
