Commen=
t # 9
on bug 10706=
5
from Andrey Grodzovsky
(In reply to Andrey Grodzovsky from comment #8)
> (In reply to dwagner from comment #7)
> > (In reply to Andrey Grodzovsky from comment #6)
> > > So with Arch Linux kernel it happens only during S3 but with
> > > amd-staging-drm-next it happens once you start X ?
> >=20
> > Yes. I know it sounds strange, but it's currently 100% reproducib=
le to me:
> >=20
> > Booting linux-4.17.2-ARCH with amdgpu.vm_update_mode=3D0:
> > X11 starts fine, but system crashes after minutes of firefox bro=
wsing
> >=20
> > Booting linux-4.17.2-ARCH with amdgpu.vm_update_mode=3D3:
> > X11 starts fine, system does not crash (for at least hours of us=
e)
> > but crashes as above if resumed from S3 sleep
> >=20
> > Booting linux compiled from amd-staging-drm-next, as of commit
> > 527d6e839a0e52b744fd092453544e4f58977334 from yesterday, with
> > amdgpu.vm_update_mode=3D0:
> > X11 starts fine, but system crashes after minutes of firefox bro=
wsing
> >=20
> > Booting linux compiled from amd-staging-drm-next, as of commit
> > 527d6e839a0e52b744fd092453544e4f58977334 from yesterday, with
> > amdgpu.vm_update_mode=3D3:
> > X11 does not start, crashes immediately with the same above past=
ed kernel
> > BUG message and backtrace
> >=20
> >=20
> > So something with CPU-based vm_update_mode is broken, but in a di=
fferent way
> > than the SDMA-based method.
> >=20
> > I will change the subject of this report to reflect that this cra=
sh is not
> > necessarily S3-resume-related.
>=20
> I am going to try and reproduce the crash with CPU update mode here, p=
lease
> describe exactly what ASIC are you using ?
Got it already.