Re: Top kernel oopses/warnings for the week of Friday June 6th, 2008

[Thomas Gleixner <tglx@linutronix.de>]

On Fri, 6 Jun 2008, Arjan van de Ven wrote:
> On Fri, 6 Jun 2008 22:37:50 +0200 (CEST)
> Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> > 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 ?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=444059
> https://bugzilla.redhat.com/show_bug.cgi?id=442920
> 
> either one of those persons might be willing to help;)

Sigh, the magically resolved bug which takes ages to reproduce and
therefor makes bisection across thousands of commits a nightmare.

I was more looking for an "easy" reproducer :)

Thanks,

	tglx