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 13:23:49 +0100 [thread overview]
Message-ID: <564F10D5.3090309@suse.com> (raw)
In-Reply-To: <30cf6b91068d178445adac701fe49c79.squirrel@webmail.iit.demokritos.gr>
On 20/11/15 11:04, vasvir@iit.demokritos.gr wrote:
>> 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.
>>
>
> I don't have access right now. I will test it later tonight (This is my
> home machine).
>
> Would $dmesg | grep -i mtrr suffice or I need to look for the mtrr
> somewere else e.g. /proc /sys etc?
I think grepping for MTRR in dmesg should be enough.
Juergen
next prev parent reply other threads:[~2015-11-20 12:23 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 [this message]
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=564F10D5.3090309@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox