Messages in this thread | | | Date | Fri, 5 Jan 2018 14:34:34 +0100 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH 4.4 00/37] 4.4.110-stable review |
| |
On Fri, Jan 05, 2018 at 02:03:17PM +0100, Mike Galbraith wrote: > On Fri, 2018-01-05 at 13:17 +0100, Greg Kroah-Hartman wrote: > > 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... > > SLE12-SP[23]-RT, currently 4.4.104 based. Parent trees boot fine in the > vm too. I thought perhaps it was a config difference, but seems not, > 4.4.110-rc1 built with as close to enterprise config as you can get > blows up the same as my light config.
Ok, we found two patches that were missing in 4.4-stable that were in the SLES12 tree (thanks to Jamie Iles), now I only have 19k more to sift through :)
I should probably do an "interm" release to get people to be able to sync up to a common place easier for testing, dealing with patch sets and random emails saying different git ids is not easy for anyone.
thanks,
greg k-h
| |