Comme=
nt # 48
on bug 10232=
2
from dwagner
(In reply to Andrey Grodzovsky from comment #47)
> Created attac=
hment 141174 [details] [review] [re=
view]
> add_debug_info.patch
>=20
> A am attaching a basic debug patch, please try to apply it.
Done.
> It should give a
> bit more info in dmesg whe VM fault happens.
Hmm - I could not see any additional output resulting from it.
> Reproduce again like before with the cmd-trace l=
ike before and once the
> fault happens if possible try quickly run=20
>=20
> sudo umr -O halt_waves -wa
>=20
> and only if you still have running system after that do the=20
> sudo umr -O verbose -R gfx[.]
>=20
> The driver should be loaded amdgpu.vm_fault_stop=3D2 from grub
Did that - will attach the script "gpu_debug3.sh" and its output =
- this time,
dmesg and trace output are in the same file, if you want to look only at the
dmesg part, "grep '^\[' gpu_debug_3.txt" will get it.=20
I reproduced the bug 4 times, on 2 occasions no error wa=
s emitted before
crashing, the 2 other times both umr commands could still run - since the e=
rror
message looked the same, I'll attach the shorter file, where the crash occu=
rred
more quickly.
> Also check if adding amdgpu.vm_debug=3D1 makes t=
he issue reproduce more quickly
I used that setting, but it did not seem to make a difference for how quick=
ly
the crash occurred - still "some seconds to some minutes".