public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Juergen Gross <jgross@suse.com>
Cc: vasvir@iit.demokritos.gr, linux-kernel@vger.kernel.org,
	Toshi Kani <toshi.kani@hp.com>
Subject: Re: Hibernate resume bug around 3,18-rc2 - Full PAT support
Date: Tue, 24 Nov 2015 23:46:06 +0100	[thread overview]
Message-ID: <20151124224606.GD9528@wotan.suse.de> (raw)
In-Reply-To: <56532064.2060502@suse.com>

On Mon, Nov 23, 2015 at 03:19:16PM +0100, Juergen Gross wrote:
> On 23/11/15 15:11, vasvir@iit.demokritos.gr wrote:
> > Ok I will send the .config when I get back home. I have all kernels I
> > build in .deb archive. The problem is that the debian kernel build
> > procedure does not hold somewhere in the deb file the git commit hash.
> > 
> > Fow which kernel would you care to see the config? 4.3?
> 
> Doesn't really matter anymore. I've posted a patch already to fix it and
> got the reply, that the fix is okay, but no harm can come from the
> current implementation, as the two config options are always either both
> set or reset.

Hrm, Vassilis seems to be able to reproduce this more effectively by heating up
his CPU prior to hibernation though. I have no idea what adding APIC_LVT_MASKED
((1 << 16)) to the Local Vector Table (LVT) Thermal Monitor (APIC_LVTTHMR 0x330) does but
clear_local_APIC() seems to be used to "cleanout any BIOS leftovers during
boot." If we're suspending but the fan is still on I wonder if this could cause
an issue with some settings the BIOS may have set prior to hibernation, and
a mismatch upon resume.

I can't find what APIC_LVT_MASKED does though, the best doc I found:

https://www-ssl.intel.com/content/dam/www/public/us/en/documents/white-papers/cpu-monitoring-dts-peci-paper.pdf

The inability to set the MTRR for the i915 card might be totally separate
issue at this point, not sure. One could test that I suppose by just
using vesa graphics card driver (disabling i915) to at least get
a basic screen to see things and compile/test things.

  Luis

  reply	other threads:[~2015-11-24 22:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 21:43 Hibernate resume bug around 3,18-rc2 - Full PAT support Vassilis Virvilis
2015-11-19  5:39 ` Juergen Gross
2015-11-19  7:50   ` vasvir
2015-11-19  9:10     ` Juergen Gross
2015-11-19 20:35       ` Vassilis Virvilis
2015-11-20  5:25         ` Vassilis Virvilis
2015-11-20  8:47           ` Juergen Gross
2015-11-20 10:04             ` vasvir
2015-11-20 12:23               ` Juergen Gross
2015-11-21 11:49                 ` Vassilis Virvilis
2015-11-23  7:32                   ` Juergen Gross
2015-11-23 14:11                     ` vasvir
2015-11-23 14:19                       ` Juergen Gross
2015-11-24 22:46                         ` Luis R. Rodriguez [this message]
2015-11-25  5:01                           ` Juergen Gross
2015-11-25 19:24                             ` Luis R. Rodriguez
2015-11-23 18:56                   ` Luis R. Rodriguez
2015-11-23 23:01                     ` Vassilis Virvilis
2015-11-24 22:16                       ` Luis R. Rodriguez
2015-11-23 18:48   ` Luis R. Rodriguez
2015-11-24  9:36     ` vasvir
2015-11-24 22:03       ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151124224606.GD9528@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toshi.kani@hp.com \
    --cc=vasvir@iit.demokritos.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox