Date: Fri, 6 Jun 2008 22:37:50 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Arjan van de Ven <arjan@linux.intel.com>
cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Linus Torvalds <torvalds@linux-foundation.org>,
       Andrew Morton <akpm@linux-foundation.org>,
       Jeff Garzik <jeff@garzik.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Top kernel oopses/warnings for the week of Friday June 6th,
 2008
In-Reply-To: <484988C8.1080105@linux.intel.com>
Message-ID: <alpine.LFD.1.10.0806062234420.3235@apollo.tec.linutronix.de>
References: <484988C8.1080105@linux.intel.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 926
Lines: 26

On Fri, 6 Jun 2008, Arjan van de Ven wrote:
> 
> Rank 8: tick_broadcast_oneshot_control (deadlock)
> 	Reported 95 times (315 total reports)
> 	The deadlock/timeout detector triggers in this codepath rather
> agressively. I'm hesitant
> 	to pin this one on bad hardware, it's happening too repeastedly too
> much.
> 	This deadlock was last seen in version 2.6.25.3, and first seen in
> 2.6.24-rc4.
> 	More info:
> http://www.kerneloops.org/searchweek.php?search=tick_broadcast_oneshot_control

Is there a way to tell on which kind of systems this shows up ?

I'm stll looking for someone having this problem, who is willing to go
through a meticulous debug session.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/