mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Fri, 6 Jun 2008 22:37:50 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806062234420.3235@apollo.tec.linutronix.de> (raw)
In-Reply-To: <484988C8.1080105@linux.intel.com>

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

  reply	other threads:[~2008-06-06 20:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 18:58 Arjan van de Ven
2008-06-06 20:37 ` Thomas Gleixner [this message]
2008-06-06 20:55   ` Arjan van de Ven
2008-06-06 21:06     ` Thomas Gleixner
2008-06-08  4:34 ` Greg KH
2008-06-08  4:55   ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.1.10.0806062234420.3235@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®