(In reply to Michel D=C3=A4nzer from comment #2)
> Created attachment 140905 [details] [review] [review]
> Use kvmalloc in amdgpu_uvd_suspend
>=20
> Does this patch help by any chance?
>=20
> If not, can you bisect between 4.18-rc1 and -rc6? Note that from your
> description, you'll need to test for at least one day before declaring=
 a
> commit good (if you hit a failure, you can immediately declare that co=
mmit
> bad).

Hi Michel,

Thank you for the patch.  I've rebuilt the kernel with the changes in your
patch and am currently going to test it out over the next several days.

I've noticed that the problem seems to occur when there is a large amount of
memory pressure (e.g. I'm running a VM where I've allocated lots of memory),
and almost always after I've just opened a new application windows.  Perhap=
s a
web browser, text editor, etc.

Today I had a scenario (running the vanilla 4.18-rc7) where I simply ran ou=
t of
memory *BUT* this occurred in the absence of opening up a new application
window, and the system was able to recover gracefully.

I do have 16GB of RAM in my system, but I can easily hit the limit by runni=
ng a
VM and opening several applications.

Should I conduct tests with memory pressure applied to see if your patch
addresses the issue?  Are we trying to simulate the same scenario as before?

I'll report back my results.

P.S. I've attached another dmesg.log from the out of memory problems I ran =
into
today (again running on vanilla 4.18-rc7 and not using your patch) so you c=
an
compare the two scenarios.  This scenario did not result in a complete syst=
em
lockup, so something different must have occurred.

Thanks!