All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: vasvir@iit.demokritos.gr
Cc: linux-kernel@vger.kernel.org, Toshi Kani <toshi.kani@hp.com>,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: Hibernate resume bug around 3,18-rc2 - Full PAT support
Date: Fri, 20 Nov 2015 09:47:08 +0100	[thread overview]
Message-ID: <564EDE0C.9060002@suse.com> (raw)
In-Reply-To: <564EAEB3.4000107@iit.demokritos.gr>

On 20/11/15 06:25, Vassilis Virvilis wrote:
> On 11/19/2015 10:35 PM, Vassilis Virvilis wrote:
>>
>> I compiled and I am running 4.3 right now.
>>
> 
> It failed this morning. Last night I did 3 hibernate / resume cycles. In
> the last one I I also turned off the PSU (this seems to push it over the
> edge - but it may be random behavior) and it worked. This morning 7h
> later failed to resume - but it didn't hang on _lapic_resume. This time
> it rebooted - and I seem to recall this behavior for 4.2+ kernels. I
> forgot to mention it because my testing with 4.x kernels were one month
> before.
> 
> So 4.3 kernel - reboots on resume after a long hibernation time.
> 
> I am testing with 4.3 and nopat right now.

I've just found a potential issue: In case MTRR is disabled by the BIOS
the PAT register of the boot processor won't be restored after resume.

Can you check whether pr_info("MTRR: Disabled\n") has been executed in
early boot? If yes, this might be a BIOS option.


Juergen





  reply	other threads:[~2015-11-20  8:47 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 [this message]
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
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=564EDE0C.9060002@suse.com \
    --to=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.