[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da61401a-5d97-c925-ef0b-fcd937c2712a@gmail.com>
Date: Wed, 28 Feb 2018 05:46:39 -0500
From: Woody Suwalski <terraluna977@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Linux Kernel List <linux-kernel@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>,
William Grant <william.grant@...onical.com>
Subject: Re: 4.16 regression: s2ram broken on non-PAE i686
Thomas Gleixner wrote:
> Woody,
>
> On Tue, 27 Feb 2018, Woody Suwalski wrote:
>
>> There is a problem with s2ram on 4.16, and it has now been propagated
>> to 4.15 and 4.14 stable updates.
>>
>> It originates from
>>
>> commit 62c00e6122a6b5aa7b1350023967a2d7a12b54c9
>> Author: William Grant <william.grant@...onical.com
>> <mailto:william.grant@...onical.com>>
>> Date: Tue Jan 30 22:22:55 2018 +1100
>>
>> x86/mm: Fix overlap of i386 CPU_ENTRY_AREA with FIX_BTMAP
>>
>> s2ram works OK on PAE kernels, breaks badly on non-PAE. I do not think
>> that the problem can be duplicated in VMPlayer, but it is 100%
>> reproducible on a "real" hardware.
>> System goes to sleep OK, but when woken - it reboots the PC.
>>
>> The issue is tracked in Bugzilla bug 198763
>> [https://bugzilla.kernel.org/show_bug.cgi?id=198763]
> Thanks for digging into this so far. Can you please provide dmesg output
> from a PAE=y and PAE=n kernel after boot?
>
> Thanks,
>
> tglx
Certainly. I understand you want dmesg output for kernels build with and
without PAE, not just PAE=n on the cmdline :-)
Here it is...
Thanks, Woody
View attachment "dmesg.nopae.txt" of type "text/plain" (54882 bytes)
View attachment "dmesg.pae.txt" of type "text/plain" (55036 bytes)
Powered by blists - more mailing lists