------- Comment From <email address hidden> 2017-09-20 08:53 EDT-------
> @Breno, Commit e47057151 was not applied to Xenial. It did not apply
> cleanly because the following commit is already in Xenial as of 4.4.0-96(As
> Xenial SHA1 25e0720):
>
> 17d381054b1d6f4adc3db623b2066fff41b4dc1a
> ("KVM: PPC: Book3S HV: Reload HTM registers explicitly")
>
> Commit 17d381054 came in from the 4.4.80 updates and does what commit
> e47057151 does and more. Per comment #18, it sounds like it fixes this bug.
> It would be great if others affected by this bug could also test -proposed.
Sure. We will let you know if we hit this issue on kernel 4.4.0-96+.
------- Comment From <email address hidden> 2017-09-20 08:53 EDT------- adc3db623b2066f ff41b4dc1a
> @Breno, Commit e47057151 was not applied to Xenial. It did not apply
> cleanly because the following commit is already in Xenial as of 4.4.0-96(As
> Xenial SHA1 25e0720):
>
> 17d381054b1d6f4
> ("KVM: PPC: Book3S HV: Reload HTM registers explicitly")
>
> Commit 17d381054 came in from the 4.4.80 updates and does what commit
> e47057151 does and more. Per comment #18, it sounds like it fixes this bug.
> It would be great if others affected by this bug could also test -proposed.
Sure. We will let you know if we hit this issue on kernel 4.4.0-96+.
Thanks