Re: 4.16 regression: s2ram broken on non-PAE i686

On Wed, 28 Feb 2018, Woody Suwalski wrote: > Thanks for the patch, good news, it did fix the problem. > I did 2 builds and both worked OK over the s2ram cycle. Good. > It will be necessary to add the patch to 4.15-stable and 4.14-stable, I > believe that both have now broken s2ram. Right, it's

Re: 4.16 regression: s2ram broken on non-PAE i686

On Wed, 28 Feb 2018, Woody Suwalski wrote: > Thanks for the patch, good news, it did fix the problem. > I did 2 builds and both worked OK over the s2ram cycle. Good. > It will be necessary to add the patch to 4.15-stable and 4.14-stable, I > believe that both have now broken s2ram. Right, it's

Re: 4.16 regression: s2ram broken on non-PAE i686

Thomas Gleixner wrote: Woody, On Wed, 28 Feb 2018, Woody Suwalski wrote: 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 for providing the data. It did not pinpoint the issue but at least it gave me

Re: 4.16 regression: s2ram broken on non-PAE i686

Thomas Gleixner wrote: Woody, On Wed, 28 Feb 2018, Woody Suwalski wrote: 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 for providing the data. It did not pinpoint the issue but at least it gave me

Re: 4.16 regression: s2ram broken on non-PAE i686

Woody, On Wed, 28 Feb 2018, Woody Suwalski wrote: > 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 for providing the data. It did not pinpoint the issue but at least it gave me the hint to look into

Re: 4.16 regression: s2ram broken on non-PAE i686

Woody, On Wed, 28 Feb 2018, Woody Suwalski wrote: > 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 for providing the data. It did not pinpoint the issue but at least it gave me the hint to look into

Re: 4.16 regression: s2ram broken on non-PAE i686

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

Re: 4.16 regression: s2ram broken on non-PAE i686

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 >

4.16 regression: s2ram broken on non-PAE i686

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 > Date: Tue Jan 30 22:22:55 2018

4.16 regression: s2ram broken on non-PAE i686

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 mailto:william.gr...@canonical.com>> Date: Tue Jan 30 22:22:55 2018 +1100 x86/mm: Fix overlap of