linux-kernel - Re: soft lockup - CPU#1 stuck for 15s! [swapper:0]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.99999.0712170904120.3670@localhost.localdomain>
Date:	Mon, 17 Dec 2007 09:05:49 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Parag Warudkar <parag.warudkar@...il.com>
cc:	Len Brown <lenb@...nel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Ingo Molnar <mingo@...e.hu>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: soft lockup - CPU#1 stuck for 15s! [swapper:0]

On Sun, 16 Dec 2007, Parag Warudkar wrote:

> On Dec 16, 2007 12:15 AM, Parag Warudkar <parag.warudkar@...il.com> wrote:
> > On Sat, 15 Dec 2007, Parag Warudkar wrote:
> >
> > >> I will run it for a little longer just to be sure - but I don't think it
> > >> will be a problem.
> >
> > No problems for last 10 hours - I consider this fixed.
> >
> 
> Arghh - spoke 8 hours too soon. I left it running overnight and
> morning I see a bunch of softlockups - so NO NOT FIXED.
> 
> Parag
> 
> BUG: soft lockup - CPU#1 stuck for 13s! [swapper:0]
> 
> Pid: 0, comm: swapper Not tainted (2.6.24-rc5 #21)
> EIP: 0060:[<c0533ca6>] EFLAGS: 00000206 CPU: 1
> EIP is at acpi_idle_enter_simple+0x166/0x1d0
> EAX: f7829f88 EBX: 00000dab ECX: 00000266 EDX: 00000000
> ESI: 00000000 EDI: 00c056e5 EBP: 00c0493a ESP: f7829f88
>  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> CR0: 8005003b CR2: 080f6c78 CR3: 00718000 CR4: 000006d0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff0ff0 DR7: 00000400

Sigh. You did not have the debug patch applied anymore, which printks
the timer_list data ? Can you apply it again and provide the output
please ?

Thanks,

	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/