linux-kernel - Re: 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() [occurs when ACPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0911121850190.5147@p34.internal.lan>
Date:	Thu, 12 Nov 2009 18:53:11 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	john stultz <johnstul@...ibm.com>
cc:	lkml <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390
 hpet_next_event+0x70/0x80() [occurs when ACPI_PROCESSOR=y]



On Thu, 12 Nov 2009, john stultz wrote:

> On Thu, 2009-11-12 at 18:45 -0500, Justin Piszcz wrote:
>>
>> On Thu, 12 Nov 2009, john stultz wrote:
>>
>>> Forgot to CC lkml, re-adding.
>>>
>>> On Thu, 2009-11-12 at 18:25 -0500, Justin Piszcz wrote:
>>>> On Thu, 12 Nov 2009, john stultz wrote:
>>>>> On Thu, Nov 12, 2009 at 8:33 AM, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
>>>>>> On Thu, 12 Nov 2009, Justin Piszcz wrote:
>>>>>>> On Wed, 11 Nov 2009, Justin Piszcz wrote:
>>>>>>> Again, the problem:
>>>>>>> [    3.318770] cpuidle: using governor ladder
>>>>>>> [    3.321556] ------------[ cut here ]------------
>>>>>>> [    3.321560] WARNING: at arch/x86/kernel/hpet.c:390
>>>>>>> hpet_next_event+0x70/0x80()
>>>>>>> [    3.321561] Hardware name:
>>>>>>> [    3.321562] Modules linked in:
>>>>>>> [    3.321564] Pid: 0, comm: swapper Not tainted 2.6.31.5 #17
>>>>>>> [    3.321565] Call Trace:
>>>>>>> [    3.321567]  [<ffffffff81042f00>] ? hpet_next_event+0x70/0x80
>>>>>>> [    3.321568]  [<ffffffff81042f00>] ? hpet_next_event+0x70/0x80
>>>>>>> [    3.321571]  [<ffffffff81056724>] ? warn_slowpath_common+0x74/0xd0
>>>>>>> [    3.321573]  [<ffffffff81042f00>] ? hpet_next_event+0x70/0x80
>>>>>>> [    3.321576]  [<ffffffff81077696>] ? tick_dev_program_event+0x36/0xb0
>>>>>>> [    3.321578]  [<ffffffff81077079>] ?
>>>>>>> tick_broadcast_oneshot_control+0x119/0x120
>>>>>>> [    3.321579]  [<ffffffff8107683d>] ? tick_notify+0x22d/0x420
>>>>>>> [    3.321581]  [<ffffffff8106fe37>] ? notifier_call_chain+0x37/0x70
>>>>>>> [    3.321583]  [<ffffffff8107612b>] ? clockevents_notify+0x2b/0x90
>>>>>>> [    3.321586]  [<ffffffff81244848>] ? acpi_idle_enter_bm+0x15f/0x2d3
>>>>>>> [    3.321587]  [<ffffffff812446de>] ? acpi_idle_enter_c1+0xf1/0xfc
>>>>>>> [    3.321590]  [<ffffffff812e6d7a>] ? cpuidle_idle_call+0xba/0x120
>>>>>>> [    3.321593]  [<ffffffff8102b832>] ? cpu_idle+0x62/0xc0
>>>>>>> [    3.321596] ---[ end trace cac202f11005305c ]---
>>>>>>> [    3.553852] cpuidle: using governor menu
>>>>>>
>>>>>> Other user with this problem:
>>>>>> http://lkml.org/lkml/2009/10/2/330 - Nobody responded to his report.
>>>>>>
>>>>>> This has been also been reported on other forums with no fix / conclusion on
>>>>>> any type of fix or work-around.
>>>>>
>>>>> Looks like your hpet is busted, or maybe something is resetting the
>>>>> hpet at exactly the wrong time.
>>>>>
>>>>> What does booting with the attached patch do?
>>>>
>>>> Unfortunately I cannot login fast enough to get a full dmesg:
>>>
>>> So if you comment out the printk I added, does it boot?
>> I can login ok, its just a little slower with the message printing so quickly.
>
> And just to be clear, without the patch it doesn't boot at all?
It is fine without the patch, but see notes below.

> Or is it fine, and you get just an annoying warning?
It is fine, just an annoying warning.

Without the patch it displays the annoying warning and works fine under load
for days, never had a problem with stability.  However, for those who can 
hear high pitch noise, it emits a high-pitch/frequency that is irritating
when there is no CPU utilization/when the machine is idle.  This does not
occur when processor.ko is not loaded (the message, or the noise).


>
> thanks
> -john
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/