On Sat, 1 December 2007 19:32:56 +0100, Ingo Molnar wrote:
> * Jörn Engel <[email protected]> wrote:
>
> > I have to change my qemu setup a little to see the top of those
> > dumps...
>
> btw., if you start qemu like this:
>
> qemu -cdrom ./cdrom.iso -hda ./hda.img -boot c -full-screen -kernel
> ~/bzImage -append "root=/dev/hda1 earlyprintk=serial,ttyS0,9600
> console=tty console=ttyS0,9600 enforcing=0 debug"
>
> you'll get the inner kernel's serial console log to qemu's standard
> output. Pretty useful for capturing kernel crashes.
Almost. "-serial stdio" was missing. Much better now.
stopped custom tracer.
BUG: spinlock recursion on CPU#0, sh/953
lock: c030f280, .magic: dead4ead, .owner: sh/953, .owner_cpu: 0
Pid: 953, comm: sh Not tainted 2.6.24-rc3-ge1cca7e8-dirty #2
[<c0103a04>] show_trace_log_lvl+0x35/0x54
[<c010450a>] show_trace+0x2c/0x2e
[<c0104e6d>] dump_stack+0x84/0x8a
[<c01ded7c>] spin_bug+0xa7/0xae
[<c01def14>] _raw_spin_lock+0x45/0xfa
[<c02a02b1>] _spin_lock_irqsave+0x68/0x7a
[<c01087e7>] pit_read+0x14/0x99
[<c0130ee9>] get_monotonic_cycles+0xf/0x2d
[<c013c0ef>] now+0x2a/0x7c
[<c013c33b>] ____trace+0x4d/0x1e8
[<c013dbf3>] __mcount+0x95/0xa6
[<c010d35c>] mcount+0x14/0x18
[<c0135a44>] lock_acquired+0xe/0x1d7
[<c02a02b9>] _spin_lock_irqsave+0x70/0x7a
[<c01087e7>] pit_read+0x14/0x99
[<c0130791>] update_wall_time+0x23/0x692
[<c0121756>] do_timer+0x24/0xb1
[<c01331fe>] tick_periodic+0x49/0x84
[<c013325b>] tick_handle_periodic+0x22/0x73
[<c0106315>] timer_interrupt+0x4f/0x56
[<c013e2c7>] handle_IRQ_event+0x24/0x4f
[<c013f44a>] handle_edge_irq+0xb8/0x125
[<c01054ee>] do_IRQ+0x89/0xa3
[<c01033df>] common_interrupt+0x23/0x28
[<c015d924>] vfs_write+0xa6/0x14c
[<c015df6e>] sys_write+0x4c/0x70
[<c0102a1f>] syscall_call+0x7/0xb
=======================
I assume you have the latency tracer working. If you could send me your
config, I could do a manual config-bisect and see which part of mine
causes the problem.
Jörn
--
Admonish your friends privately, but praise them openly.
-- Publilius Syrus
--
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]
