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@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx> 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
