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>,
"Theodore Ts'o" <tytso@mit.edu>,
gregkh@novell.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Oops/Warning report for the week of September 10th, 2008
Date: Wed, 10 Sep 2008 21:36:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0809102133210.13819@apollo.tec.linutronix.de> (raw)
In-Reply-To: <48C81D20.9040302@linux.intel.com>
>
> Rank 6: tick_dev_program_event (warning)
> Reported 110 times
> [debug] temporary WARN_ON() inserted in -rc5 for diagnostics purposes,
> removed for -rc6
> This warning was last seen in version 2.6.27-rc5-git10, and first seen
> in 2.6.27-rc5.
> More info:
> http://www.kerneloops.org/searchweek.php?search=tick_dev_program_event
WARN_ON() is removed in 2.6.27-rc6. It served it's purpose.
> Rank 10: tick_broadcast_oneshot_control (oops)
> Reported 58 times (1331 total reports)
> Some interaction betwee tickless and system with an AMD CPU and an ATI
> chipset
> This oops was last seen in version 2.6.25.14, and first seen in
> 2.6.24-rc4.
> More info:
> http://www.kerneloops.org/searchweek.php?search=tick_broadcast_oneshot_control
Fixed by the latest updates/fixes to clock events core and hpet
code. Working on a backport to 25/26 right now.
Thanks,
tglx
next prev parent reply other threads:[~2008-09-10 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 19:16 Arjan van de Ven
2008-09-10 19:36 ` Thomas Gleixner [this message]
2008-09-11 4:52 ` Greg KH
2008-09-11 13:23 ` Arjan van de Ven
2008-09-11 13:56 ` Arjan van de Ven
2008-09-11 20:52 ` Greg KH
2008-09-11 20:54 ` Arjan van de Ven
2008-09-11 21:53 ` Greg KH
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.0809102133210.13819@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=gregkh@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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®