[Bug 111790] [hsw iommu] i915 0000:00:02.0: GPU HANG: ecode 7:0:0x00000000, hang on rcs0

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=111790

--- Comment #8 from JPT <j-p-t at gmx.net> ---
Hi, 

I've got the problem that whenever I do disk traffic, after a few minutes the
GUI becomes laggy. Soon it locks completely. 
Sometimes the GUI simply locks, without any background work done.
I once got the mentioned GPU HANG message but I didn't fetch the error log. 
So I am still trying to produce this error message again. error log still is
empty.

I know of the problems with Linux and swap, but this is just far worse and
doesn't happen at all on my laptop with very similar setup 

how to reproduce: 
- just read or write a lot of data, let's say 100 GB via DD, CP, GUI... as you
like
- linux cache size increases until it starts swapping
- SWAPOUT is around 10 to 100 thousend pages (per atop cycle I believe)
- after a few minutes the GUI is locked. 
- when the job is finished the gui suddenly is ok again. and this completely
without the usual lagging known from a swapping system.

my environment
- Kubuntu 19.10
- Kernel 5.3.0-19
- Intel i5-9600K

I already tried, without success: 
- fresh installation of Kubuntu on a new disk
- new mouse
- vm.swappiness = 10 and vm.vfs_cache_pressure=50
- uninstalling xorg-intel driver

BTW, as alex wrote, I believe this problem disappeared with kernel 4.15.0
another remark. I usually don't have any swap, because of the bad behavior of
Linux when swapping. I only do have swap now, because else in the exact same
circumstances as above kswapd went amok instead, making the system even more
unstable/unusable.

Alex, could you just try what happens with your GUI when you produce much disk
traffic?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191104/b853fbae/attachment.html>