Subject: Re: [patch?] s2ram + P4 + tsc = annoyance
From: Mike Galbraith <efault@gmx.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
In-Reply-To: <1198780063.4425.59.camel@homer.simson.net>
References: <fa./Gg6lFn4vN7sfhp2nE3LSMDm0q4@ifi.uio.no>
	 <4773EA58.2040605@shaw.ca>  <1198780063.4425.59.camel@homer.simson.net>
Content-Type: text/plain
Date: Thu, 27 Dec 2007 19:40:40 +0100
Message-Id: <1198780840.4425.61.camel@homer.simson.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 606
Lines: 16


On Thu, 2007-12-27 at 19:27 +0100, Mike Galbraith wrote:
> On Thu, 2007-12-27 at 12:09 -0600, Robert Hancock wrote:
> 
> > Are we missing some logic to resync the TSCs after resume, or something?
> 
> They used to be forcibly synchronized during boot, but it seems that was
> dropped in 2.6.21.

(but out of sync isn't my problem, it's TSC having been reset)

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