linux-kernel - Re: [PATCH] HPET: Drop WARN_ON for mismatch on HPET CMP readback

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: <1265312442.16916.588.camel@localhost.localdomain>
Date:	Thu, 04 Feb 2010 11:40:42 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	"tglx@...utronix.de" <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] HPET: Drop WARN_ON for mismatch on HPET CMP readback

On Thu, 2010-02-04 at 11:32 -0800, Andi Kleen wrote:
> On Thu, Feb 04, 2010 at 11:22:15AM -0800, Pallipadi, Venkatesh wrote:
> > On Thu, 2010-02-04 at 11:11 -0800, Andi Kleen wrote:
> > >  HPET: Drop WARN_ON for mismatch on HPET CMP readback
> > >     
> > >     At least one Intel chipset seems to always return a constant value
> > >     when reading back the HPET CMP register. This triggers the WARN_ON_ONCE
> > >     on each boot.
> > 
> > I don't know of chipset returning a constant value. Which chipset is
> > this one?
> 
> Ibex Peak. That is I'm not sure it's fully constant, but at least
> it's always the same value on the HPET read triggering on boot.

OK. Yes. Ibexpeak is the same problem as ICH9, with reads not returning
the most recent write.

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/