[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1173090869.24738.198.camel@localhost.localdomain>
Date: Mon, 05 Mar 2007 11:34:29 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Ingo Molnar <mingo@...e.hu>
Cc: Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21-rc2-git3 soft lockup detected on CPU#0 (crash dump
kernel)
On Mon, 2007-03-05 at 09:08 +0100, Ingo Molnar wrote:
> * Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote:
>
> > http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.21-rc2-git3-kdump/log2.txt
>
> weird. Could you do a dump with SysRq-T, SysRq-Q done /twice/ after each
> other, to see how the system progresses while in this lockup? Plus
> please also try to get a register dump via SysRq-P.
>
> Btw., the task state printout seems busted:
>
> udev_run_devd ? C15B0030 2544 979 853 (L-TLB)
>
> shouldnt that be 'R' instead of the question mark?
? are dead ones,
[<c16191d9>] do_exit+0x6f9/0x6fd
[<c161924d>] sys_exit_group+0x0/0x11
[<c161925c>] sys_exit_group+0xf/0x11
[<c1603e72>] sysenter_past_esp+0x5f/0x99
The interesting part is here:
1 lock held by udevd/918:
#0: (&mm->mmap_sem){----}, at: [<c161135b>] do_page_fault+0x150/0x50d
But udevd/918 is nowhere in the sysrq-t output.
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists