(In reply to comment #3)
> Not sure of this is an oversight, or deliberate since this bug is still being
> worked on, but judging from the kernel spec changelog , this patch has not been
> added to F-16, I guess we want it there too?
I'm having a feeling upstream is working on a different, more complicated fix for this. So, maybe that will go into F-16 when upstream finalises it?
Anyway, as I said before, even with the fix, I'm losing processes on resume, so things are still not as good as on .38.
(In reply to comment #3)
> Not sure of this is an oversight, or deliberate since this bug is still being
> worked on, but judging from the kernel spec changelog , this patch has not been
> added to F-16, I guess we want it there too?
I'm having a feeling upstream is working on a different, more complicated fix for this. So, maybe that will go into F-16 when upstream finalises it?
Anyway, as I said before, even with the fix, I'm losing processes on resume, so things are still not as good as on .38.