[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-22 Thread Daniel van Vugt
I noticed the same bug in mutter 40, then tried to bisect it and found the same in mutter 3.36. So yeah this appears to be a new kernel (or Mesa) bug. It doesn't seem to happen much if at all if you run gnome- shell. Only in mutter for me. ** Bug watch added:

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-20 Thread Julian Andres Klode
Oh, drmtip exists too, I thought you said drmnext which was stuck on 09-18 (and I tested 09-15 which was more stable but not perfect). I'm currently just running the 5.9.1 mainline kernel for testing purposes, which so far (2 days in seems stable), but might just break later today, who knows. --

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-11 Thread Kai-Heng Feng
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ If the issue is not fixed upstream, please file an upstream bug at intel graphics: https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs -- You received this bug notification

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-08 Thread Daniel van Vugt
Thanks for the video. Corruption of that type is usually a kernel problem only. I can't imagine any way in which mutter can cause that one... Please try some older/newer kernels. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-08 Thread Julian Andres Klode
Corrupt lines, red flashing across the top bar: https://photos.app.goo.gl/TgYxkVHRnsrV5wCR9 I use Xorg, and almost exclusively see it on my external monitor. After locking the screen and having it locked for a while. Saw it once on the internal one in a week, but like daily on external. -- You

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-08 Thread Daniel van Vugt
... so if mutter 3.38.1 does not resolve the problem, I would be interested to see the corruption in action. Probably with a video. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896091

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-08 Thread Daniel van Vugt
Blocks/lines around areas of the screen that are changing may just be bug 1898080. ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-10-08 Thread Julian Andres Klode
Also adding a gnome-shell task. This happens on 5.8.0-21-generic from proposed too, and restarting gnome-shell stops the corruptions, so it's possible this is a gnome issue. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-09-22 Thread Julian Andres Klode
The corruption also happens in build 5.9.0-050900rc4drmintelnext20200915-generic but the error in dmesg does not, and it's less, it only happens on window management actions (switch window Surprisingly with that, restarting gnome-shell actually fixes the issue (it did not with normal kernel). --

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-09-17 Thread Julian Andres Klode
Attached dmesg from journalctl. To the best of my knowledge, this is all that's missing, as apport now has no raw dmesg access anymore and missed to upload the dmesg. ** Attachment added: "kernel.log"

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-09-17 Thread Julian Andres Klode
Attached dmesg from journalctl. To the best of my knowledge, this is all that's missing, as apport now has no raw dmesg access anymore and missed to upload the dmesg. ** Attachment added: "kernel.log"

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-09-17 Thread Julian Andres Klode
apport information ** Tags added: apport-collected ** Description changed: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when

[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

2020-09-17 Thread Julian Andres Klode
That said, hmm, it took an hour or so after the backtrace for it to cause visual distortion or I misremember, or it gets worse over time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.