Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

Hi Len, On Wed, May 25, 2016 at 12:09 AM, Len Brown wrote: > +mjg59, who may be seeing this issue on a skylake laptop > > Chen-yu, > > Great debugging, but I think there is a more general fix possible than > this DMI quirk. > > I agree that in this example, a grantley server, it

Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

Hi Len, On Wed, May 25, 2016 at 12:09 AM, Len Brown wrote: > +mjg59, who may be seeing this issue on a skylake laptop > > Chen-yu, > > Great debugging, but I think there is a more general fix possible than > this DMI quirk. > > I agree that in this example, a grantley server, it seems the BIOS

Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

+mjg59, who may be seeing this issue on a skylake laptop Chen-yu, Great debugging, but I think there is a more general fix possible than this DMI quirk. I agree that in this example, a grantley server, it seems the BIOS is erroneously returning a bogus value of MSR_IA32_THERM_CONTROL on resume

Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

+mjg59, who may be seeing this issue on a skylake laptop Chen-yu, Great debugging, but I think there is a more general fix possible than this DMI quirk. I agree that in this example, a grantley server, it seems the BIOS is erroneously returning a bogus value of MSR_IA32_THERM_CONTROL on resume

RE: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

ucw.cz; Brown, Len; l...@kernel.org; > b...@suse.de; li...@horizon.com; Kaszewski, Marcin; linux- > p...@vger.kernel.org; x...@kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for > suspend > > > * Chen Yu wrote:

Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

* Chen Yu wrote: > A bug was reported that on certain Broadwell platforms, after resuming from > S3, > the CPU is running at an anomalously low speed. > > It turns out that the BIOS has modified the value of the THERM_CONTROL > register > during S3, and changed it from 0 to 0x10, thus

Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

* Chen Yu wrote: > A bug was reported that on certain Broadwell platforms, after resuming from > S3, > the CPU is running at an anomalously low speed. > > It turns out that the BIOS has modified the value of the THERM_CONTROL > register > during S3, and changed it from 0

RE: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

ucw.cz; Brown, Len; l...@kernel.org; > b...@suse.de; li...@horizon.com; Kaszewski, Marcin; linux- > p...@vger.kernel.org; x...@kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH][v7] x86, suspend: Save/restore extra MSR registers for > suspend > > > * Chen Yu <yu.c.c..

[PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

A bug was reported that on certain Broadwell platforms, after resuming from S3, the CPU is running at an anomalously low speed. It turns out that the BIOS has modified the value of the THERM_CONTROL register during S3, and changed it from 0 to 0x10, thus enabled clock modulation(bit4), but with

[PATCH][v7] x86, suspend: Save/restore extra MSR registers for suspend

A bug was reported that on certain Broadwell platforms, after resuming from S3, the CPU is running at an anomalously low speed. It turns out that the BIOS has modified the value of the THERM_CONTROL register during S3, and changed it from 0 to 0x10, thus enabled clock modulation(bit4), but with