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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0911191811520.15711@p34.internal.lan>
Date:	Thu, 19 Nov 2009 18:12:24 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
cc:	Thomas Gleixner <tglx@...utronix.de>,
	john stultz <johnstul@...ibm.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>
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, 19 Nov 2009, Pallipadi, Venkatesh wrote:

> On Tue, 2009-11-17 at 14:53 -0800, Justin Piszcz wrote:
>>
>> On Tue, 17 Nov 2009, Pallipadi, Venkatesh wrote:
>>
>>> On Tue, Nov 17, 2009 at 03:45:31AM -0800, Justin Piszcz wrote:
>>> +		WARN_ON_ONCE((u32)hpet_readl(HPET_Tn_CMP(timer)) != cnt);
>>>
>>> 	return (s32)((u32)hpet_readl(HPET_COUNTER) - cnt) >= 0 ? -ETIME : 0;
>>> }
>>> --
>>> 1.6.0.6
>>
>> Hi, that omits the message @ boot and you are correct, all is/continues to work fine.
>>
>> Thanks..
>>
>> As far as the DP55KG reboots, the workaround is set append="reboot=a" -
>> will a BIOS fix address this (other) issue? Try rebooting Linux without
>> any special parameters (2.6.30+) and the DP55KG will hang at reboot
>> (note, shutdown does shut the machine off).
>>
>
> I haven't seen this reboot problem on my test system here. So, I don't
> know what the problem is. Probably some BIOS issue.
>
> Does "reboot=b" work? Quickest solution will be to add platform dmi
> entry in reboot.c and workaround this.
>
> Thanks,
> Venki
>

Hi,

>From my previous e-mail:

reboot=a * SUCCESS
reboot=b * FAIL
reboot=cold * FAIL
reboot=efi * FAIL
reboot=force * FAIL
reboot=h * FAIL
reboot=p * SUCCESS
reboot=s * FAIL
reboot=t * SUCCESS
reboot=warm * FAIL

Justin.
--
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/