Date: Fri, 5 Jan 2018 13:17:01 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Guenter Roeck <linux@roeck-us.net>, linux-kernel@vger.kernel.org,
        torvalds@linux-foundation.org, akpm@linux-foundation.org,
        shuahkh@osg.samsung.com, patches@kernelci.org,
        ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org,
        stable@vger.kernel.org, Tao Wu <lepton@google.com>
Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review
Message-ID: <20180105121701.GD19551@kroah.com>
References: <20180103195056.837404126@linuxfoundation.org>
 <20180104234555.GA4143@roeck-us.net>
 <1515127074.7787.12.camel@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1515127074.7787.12.camel@gmx.de>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org

On Fri, Jan 05, 2018 at 05:37:54AM +0100, Mike Galbraith wrote:
> On Thu, 2018-01-04 at 15:45 -0800, Guenter Roeck wrote:
> > 
> > The crash part of this problem may be solved with the following patch
> > (thanks to Hugh for the hint). There is still another problem, though -
> > with this patch applied, the qemu session aborts with "VCPU Shutdown
> > request", whatever that means.
> 
> The crash part is not fixed by your patch here, w/wo I get this, and it
> is PTI, as virgin 109 boots/works with identical everything else. ?My
> shiny new PTI equipped enterprise 4.4 RT kernels also boot/work fine,
> which seems a bit odd.. and not particularly comforting.

Might I ask _what_ enterprise 4.4 kernels you are trying here?  This
should be the identical set to what is in the SLES12 tree, which worries
me a lot...

thanks,

greg k-h