From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.33: Problem continues: WARNING: at arch/x86/kernel/hpet.c:404 hpet_next_event+0x70/0x80
Date: Wed, 24 Feb 2010 18:37:04 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002241835120.4716@p34.internal.lan> (raw)
Hello,
Again, on the Intel DP55KG board:
# uname -a
Linux host 2.6.33 #1 SMP Wed Feb 24 18:31:00 EST 2010 x86_64 GNU/Linux
[ 1.237600] ------------[ cut here ]------------
[ 1.237890] WARNING: at arch/x86/kernel/hpet.c:404 hpet_next_event+0x70/0x80()
[ 1.238221] Hardware name:
[ 1.238504] hpet: compare register read back failed.
[ 1.238793] Modules linked in:
[ 1.239315] Pid: 0, comm: swapper Not tainted 2.6.33 #1
[ 1.239605] Call Trace:
[ 1.239886] <IRQ> [<ffffffff81056c13>] ? warn_slowpath_common+0x73/0xb0
[ 1.240409] [<ffffffff81079608>] ? tick_dev_program_event+0x38/0xc0
[ 1.240699] [<ffffffff81056cb0>] ? warn_slowpath_fmt+0x40/0x50
[ 1.240992] [<ffffffff81079608>] ? tick_dev_program_event+0x38/0xc0
[ 1.241281] [<ffffffff81041ad0>] ? hpet_next_event+0x70/0x80
[ 1.241573] [<ffffffff81079608>] ? tick_dev_program_event+0x38/0xc0
[ 1.241859] [<ffffffff81078e32>] ? tick_handle_oneshot_broadcast+0xe2/0x100
[ 1.246533] [<ffffffff8102a67a>] ? timer_interrupt+0x1a/0x30
[ 1.246826] [<ffffffff81085499>] ? handle_IRQ_event+0x39/0xd0
[ 1.247118] [<ffffffff81087368>] ? handle_edge_irq+0xb8/0x160
[ 1.247407] [<ffffffff81029f55>] ? handle_irq+0x15/0x20
[ 1.247689] [<ffffffff810294a2>] ? do_IRQ+0x62/0xe0
[ 1.247976] [<ffffffff8146be53>] ? ret_from_intr+0x0/0xa
[ 1.248262] <EOI> [<ffffffff8102f277>] ? mwait_idle+0x57/0x80
[ 1.248796] [<ffffffff8102645c>] ? cpu_idle+0x5c/0xb0
[ 1.249080] ---[ end trace db7f668fb6fef4e1 ]---
Is this something Intel has to fix or is it a bug in the kernel?
Justin.
next reply other threads:[~2010-02-24 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 23:37 Justin Piszcz [this message]
2010-02-25 14:03 ` Thomas Backlund
2010-02-25 14:22 ` Justin Piszcz
2010-02-25 18:53 ` Pallipadi, Venkatesh
2010-02-25 20:38 ` Thomas Gleixner
2010-04-01 22:58 ` [tip:x86/urgent] x86, hpet: Erratum workaround for read after write of HPET comparator tip-bot for Pallipadi, Venkatesh
2010-04-29 1:36 ` [tip:x86/timers] x86, hpet: Restrict read back to affected ATI chipsets tip-bot for Thomas Gleixner
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.DEB.2.00.1002241835120.4716@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.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®