On 07/12/2017 05:03 PM, Samuel Sieb wrote: > On 07/12/2017 04:48 PM, Cole Robinson wrote: >> There's a bug about this issue with that's lingered in a lot of forms >> for a while: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1380893 >> >> But with my testing, kernel > 4.9 inside the VM fixes the issue. So >> supported >> fedora releases in the VM aren't affected anymore. You can work around >> it by >> disabling kvmclock for the VM, but I'm not sure what other side >> effects that >> will have > > The other option would be to try upgrading the kernel in the VM to > something 4.9 or higher.
I seem to recall an issue with kernels <4.9 and resume operations--VMs or bare metal. IIRC there were two issues. One was in the i915 driver and the second was something about a boffed internal state in one of the timers that caused the slab code to run away or something like that. I sure could be wrong about that. I rarely hibernate/resume my machines so it never bit me. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ri...@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - When you don't know what to do, walk fast and look worried. - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
