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: <1258137165.21141.20.camel@localhost.localdomain>
Date:	Fri, 13 Nov 2009 10:32:45 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Justin Piszcz <jpiszcz@...idpixels.com>,
	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 Fri, 2009-11-13 at 01:38 -0800, Thomas Gleixner wrote:
> On Thu, 12 Nov 2009, Pallipadi, Venkatesh wrote:
> > Yes. Yes. This is a hardware errata. I have a patch to workaround this and
> > waiting on the errata description to get published..
> 
> Can we at least have some PCI quirk or whatever until you can push the
> final workaround out so peoples machines do not explode ?

Its a harmless bug functionality-wise and should not have any side
effect other than triggering the WARN_ON_ONCE in hpet next event code.

Thanks,
Venki

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