hibernate random memory corruption, workaround i915.modeset=0
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi Stanislaw!
Quoted 28 lines · Stanislaw Gruszka
Quoted 7 lines · Keith Packard
<#part sign=pgpmime>
Quoted 1 line · Stanislaw Gruszka
Keith, is there a chance that this bug can be fixed by i915 team?
Yes, I'm working on figuring out how to actually reproduce this and then work on a few work-arounds.
This must be hardware dependent then, yesterday and today I tried to reproduce on Lenovo T60 with:
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
and there is no sign of corruption, I double checked if slab poisoning is enabled.
Quoted 6 lines
Quoted 2 lines
If not, can we disable hibernate on i915 with modeset=1 and add module option, which enable it for those who want to risk?
I'd love to know if disabling modeset on just the booting kernel helps; leaving the resuming kernel with modeset=1. I haven't been able to reproduce this locally yet to test this theory though.
On Lenovo T500 with:
00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
Quoted 8 lines
that is the case. Script attached on previous email trigger corruption with modeset=1 (on various older and newer kernels) in less then 20 iterations. There is no corruption after 100 iterations if i915.modeset=0 parameter is used. Some users on RH bugzilla confirmed that workaround as well.
If you want list of more i915 adapters where the problem happens, I can check in our bugzilla and provide it.
It happens too with a MSI CR620 notebook (Intel Core I5 M460):
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
I can confirm that modeset=0 during resume doesn't activate the error. But this is nothing new as I already wrote here[1], that the error doesn't come up as long as kms is disabled.
Regards,
Andreas