Bug 15218 - WARNING at hpet_next_event
Summary: WARNING at hpet_next_event
Status: RESOLVED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-03 15:36 UTC by Serkan Hosca
Modified: 2012-06-27 13:15 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.33-rc6
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (167.41 KB, text/plain)
2010-02-03 15:36 UTC, Serkan Hosca
Details
lspci (37.38 KB, text/plain)
2010-02-03 15:40 UTC, Serkan Hosca
Details
acpidump (252.72 KB, text/plain)
2010-02-03 16:06 UTC, Serkan Hosca
Details

Description Serkan Hosca 2010-02-03 15:36:05 UTC
Created attachment 24891 [details]
dmesg

[    2.508377] ------------[ cut here ]------------
[    2.508473] WARNING: at /home/kernel-ppa/mainline/build/arch/x86/kernel/hpet.c:404 hpet_next_event+0x82/0x90()
[    2.508572] Hardware name: HP ENVY 15 Notebook PC
[    2.508663] hpet: compare register read back failed.
[    2.508762] Modules linked in:
[    2.508948] Pid: 0, comm: swapper Not tainted 2.6.33-020633rc6-generic #020633rc6
[    2.509049] Call Trace:
[    2.509147]  [<ffffffff8102e602>] ? hpet_next_event+0x82/0x90
[    2.509249]  [<ffffffff81059ec7>] warn_slowpath_common+0x87/0xb0
[    2.509346]  [<ffffffff81059f74>] warn_slowpath_fmt+0x64/0x70
[    2.509449]  [<ffffffff8127dfa3>] ? cpumask_next_and+0x23/0x40
[    2.509543]  [<ffffffff81011046>] ? read_tsc+0x16/0x40
[    2.509639]  [<ffffffff8102e602>] hpet_next_event+0x82/0x90
[    2.509740]  [<ffffffff8102e62b>] hpet_legacy_next_event+0xb/0x10
[    2.509838]  [<ffffffff81087187>] clockevents_program_event+0x57/0xa0
[    2.509937]  [<ffffffff810887be>] tick_dev_program_event+0x3e/0xc0
[    2.510039]  [<ffffffff81087cb5>] tick_broadcast_set_event+0x15/0x20
[    2.510139]  [<ffffffff81088193>] tick_broadcast_oneshot_control+0x113/0x120
[    2.510234]  [<ffffffff8153e29f>] ? _raw_spin_lock_irqsave+0x2f/0x50
[    2.510335]  [<ffffffff81087b7a>] tick_notify+0x7a/0xd0
[    2.510432]  [<ffffffff8154186f>] notifier_call_chain+0x3f/0x70
[    2.510534]  [<ffffffff8107ee09>] __raw_notifier_call_chain+0x9/0x10
[    2.510631]  [<ffffffff8107ee21>] raw_notifier_call_chain+0x11/0x20
[    2.510731]  [<ffffffff81086fe6>] clockevents_do_notify+0x16/0x20
[    2.510833]  [<ffffffff81087331>] clockevents_notify+0x31/0x170
[    2.510929]  [<ffffffff8100a88e>] ? apic_timer_interrupt+0xe/0x20
[    2.511031]  [<ffffffff812e98ae>] lapic_timer_state_broadcast+0x41/0x43
[    2.511133]  [<ffffffff812ea062>] acpi_idle_enter_simple+0x92/0x110
[    2.511235]  [<ffffffff8141a186>] cpuidle_idle_call+0x96/0x120
[    2.511337]  [<ffffffff81008727>] cpu_idle+0x97/0xe0
[    2.511429]  [<ffffffff81538ece>] ? setup_APIC_timer+0x7e/0x90
[    2.511530]  [<ffffffff81538864>] start_secondary+0x94/0xc0
[    2.511633] ---[ end trace c0487cee148e0f94 ]---
Comment 1 Serkan Hosca 2010-02-03 15:40:27 UTC
Created attachment 24892 [details]
lspci
Comment 2 Serkan Hosca 2010-02-03 16:06:49 UTC
Created attachment 24896 [details]
acpidump

Note You need to log in before you can comment on or make changes to this bug.