MIME-Version: 1.0
In-Reply-To: <CAOAebxsBVTyS2gSXh4c-g1b8Lvjv9MBG3Wjr_AC+LJpMLHRqEA@mail.gmail.com>
References: <CAOAebxvV3RHScmG=EXYcoMv3KmOXUbgevbJB-RzAppQ9kK4g5w@mail.gmail.com>
 <0C00DC80-5F7E-4417-872D-66473A6387A0@amacapital.net> <CAOAebxvNsQ4KTFGE0FcoJA2odvEFou-2ozyThtwMn=ptyKGQ-Q@mail.gmail.com>
 <20180105175229.GA29834@kroah.com> <CALCETrW3hfkeUAPzFhGdE56vn23Q462h2reMaT=3ftbNGeSb3Q@mail.gmail.com>
 <CAOAebxvbXrVV7-x6LdEsAEhjR=qrxNBxxBrWzk7RaBECcWqsiw@mail.gmail.com>
 <CAOAebxv47m34R1qteFaQB1-x4jsUVJPPvPLVe4jxRGZeFUY2qA@mail.gmail.com>
 <CAOAebxuqK4TOktLrHNLdW-S3oSxVO2og84js7N5u_QDC7mE2Ow@mail.gmail.com>
 <20180105204557.GA8839@kroah.com> <a93f30d1-e00e-419b-532d-203be16e2299@oracle.com>
 <20180107104540.GB14783@kroah.com> <CAOAebxsBVTyS2gSXh4c-g1b8Lvjv9MBG3Wjr_AC+LJpMLHRqEA@mail.gmail.com>
From: Pavel Tatashin <pasha.tatashin@oracle.com>
Date: Sun, 7 Jan 2018 10:06:59 -0500
Message-ID: <CAOAebxsP1LLV-Eg_h8brbxfsn_tpRDR46yrVZeokrFt3ArRuMA@mail.gmail.com>
Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Lutomirski <luto@kernel.org>, Hugh Dickins <hughd@google.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Thomas Voegtle <tv@lio96.de>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Guenter Roeck <linux@roeck-us.net>,
        Shuah Khan <shuahkh@osg.samsung.com>, patches@kernelci.org,
        Ben Hutchings <ben.hutchings@codethink.co.uk>,
        lkft-triage@lists.linaro.org, stable <stable@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org

Hi Greg,

I reverted suse12 back to:
13dae54cb229d078635f159dd8afe16ae683980b
x86/kaiser: Move feature detection up (bsc#1068032).

And, still do not see the problem. So, whatever fixes the issue comes
before kaiser.

Pavel

On Sun, Jan 7, 2018 at 9:17 AM, Pavel Tatashin
<pasha.tatashin@oracle.com> wrote:
> Hi Greg,
>
> I cloned and built suse12, and it does not have issues with EFI + PTI
> (kaiser) on my machine.
>
> BTW, i have also reproduced this problem on another machine with the
> same configuration, therefore, it is not specific only to one box.
> Also, as I mentioned earlier I am seeing the same issue with 4.1 +
> kaiser patches taken from 4.4.110.
>
> Thank you,
> Pavel
>
> On Sun, Jan 7, 2018 at 5:45 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>> On Fri, Jan 05, 2018 at 04:03:54PM -0500, Pavel Tatashin wrote:
>>> The hardware works :) I meant that before the patch linked in
>>> https://lkml.org/lkml/2018/1/5/534, I was never able to boot 4.4.110. But
>>> with that patch applied, I was able to boot it at least once, but it could
>>> be accidental. The hang/panic does not happen at the same time on every
>>> boot.
>>
>> Any chance you can grab the latest SLES 12 kernel and run it with pti
>> and efi enabled to see if that works properly for you or not?  I trust
>> SUSE's testing of their kernel, and odds are I'm just missing one of
>> their many other patches they have in their tree for other issues that
>> they have seen in the past.
>>
>> If you want, I can just send you the full patch that they run on top of
>> the latest 4.4 stable tree, so you don't have to dig it out of their git
>> repo if you can't find the binary image.
>>
>> thanks,
>>
>> greg k-h