Subject: Re: [PATCH] HPET: Drop WARN_ON for mismatch on HPET CMP readback
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
       "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
In-Reply-To: <20100204193224.GA8957@basil.fritz.box>
References: <20100204191112.GA10135@basil.fritz.box>
	 <1265311335.16916.586.camel@localhost.localdomain>
	 <20100204193224.GA8957@basil.fritz.box>
Content-Type: text/plain
Date: Thu, 04 Feb 2010 11:40:42 -0800
Message-Id: <1265312442.16916.588.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1023
Lines: 27

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/