From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162117AbbKTIru (ORCPT ); Fri, 20 Nov 2015 03:47:50 -0500 Received: from mx2.suse.de ([195.135.220.15]:48866 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162297AbbKTIrK (ORCPT ); Fri, 20 Nov 2015 03:47:10 -0500 Subject: Re: Hibernate resume bug around 3,18-rc2 - Full PAT support To: vasvir@iit.demokritos.gr References: <564CF10E.6000905@iit.demokritos.gr> <564D6090.9020604@suse.com> <564D91ED.4090403@suse.com> <564E32A4.7010406@iit.demokritos.gr> <564EAEB3.4000107@iit.demokritos.gr> Cc: linux-kernel@vger.kernel.org, Toshi Kani , "Luis R. Rodriguez" From: Juergen Gross X-Enigmail-Draft-Status: N1110 Message-ID: <564EDE0C.9060002@suse.com> Date: Fri, 20 Nov 2015 09:47:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <564EAEB3.4000107@iit.demokritos.gr> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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