## Paul Durrant (paul.durr...@citrix.com):
> Actually no need... The underlying issue was really a bug and has
> been fixed in 4.14.11.
Oh. That explains why reverting the other patch "fixed" the problem -
I had skipped 4.14.10 and 4.14.11 - and the problem has gone away
independently of that.
Co
Hi,
my system is:
- amd64
- xen from Debian 9 (stable), package versions 4.8.2+xsa245-0+deb9u1
- home-build kernel Linux 4.14.8 (I believe I saw this with something
like 4.14.1, but I didn't get the logs at that point and had no time
to investigate, so I just reverted to 4.13.16).
- all DomUs
## Alex Braunegg (alex.braun...@gmail.com):
> With Christoph any myself reporting the same kernel crash when using
> 4.14.x kernels and Xen 4.8.2 is there any chance to look at this bug
> before 4.8.3 is released?
As "our" bug seems to be kernel-side (I've no problems in 4.13.16, or
any other 4.
## Paul Durrant (paul.durr...@citrix.com):
> How easy is it to trigger this? I'm assuming, from the original
> description, that I can probably trigger it by forcibly terminating
> a running domain and then trying to restart it.
As Alex said: in the "common cases" (like his and mine) it seems to
## Paul Durrant (paul.durr...@citrix.com):
> > I could try a new kernel (KPTI, yay!) with that "mildly suspicious" commit
> > cc8737a5fe9051b7fa052b08c57ddb9f539c389a reverted on the weekend and
> > report back (just to rule that out - like you, I don't really believe
> > that this is the cause).
