Chromium based browsers flickering on kernel 5.15 #97
Comments
|
What hardware are you using? What graphics card, processor, motherboard, storage, and RAM? |
|
|
Same here. Both Brave and Slack flicker randomly after updating to 5.15. Reverting to 5.13 resolves it. |
|
Is this issue occurring across other distros? What could be causing it? Is there any more info i should provide? |
|
I believe I am seeing this issue too, with a PowerColor 6800 XT running PopOS 21.04 in a custom rig. I see random flickering on both monitors with kernel 5.15, while booting with backup kernel 5.13 has no issue. Flickering affects whole display (including desktop background), not just specific apps/windows, but seems like it happens more frequently when using Chrome (I have full Google Chrome 96.0.4664.93 -- don't judge). The GPU has worked flawlessly up until a few days ago when I first booted with 5.15. Showing the flickering issue: 5.15.5-76051505-generic: Not showing the flickering issue: 5.13.0-7620-generic: I have two custom .deb repos, but neither affect kernel: |
|
Also happens on my bone stock lemp9. However I am not using Chrome, I use FireFox. I opened a support ticket through their portal, I apologize if this comment is unnecessary |
I hope someone has an explanation for why this is happening, it seems i'm not the only one who's affected, i wonder why Pop 20.04 LTS upgraded the kernel so soon, did Ubuntu upgrade the kernel too? |
|
Attaching dmesg output from a 5.13 (no flickering) and a 5.15 (flickering) boot. |
|
I have this issue on a fresh install lemp10 laptop. |
Please run inxi -F in the terminal and post the output here, the developers need as much info as you can provide. Open terminal --> type inxi -F then press Enter --> select the whole output then copy it with Ctrl Shift C --> start a new comment here, press Ctrl E to insert code then paste the terminal output. |
|
@guyvdbroeck Please include the OS version you did a clean install with, as well as the packages you installed after installing the OS. If I can recreate this on my lemp10 it would be immensely helpful for troubleshooting. |
|
|
I was able to stop the flickering by adding |
Could you write a step by step instruction on how to modify kernel parameters? It would make things much easier for less experienced users, i often find the Arch Wiki too complicated, it never tells me how to do things and which commands i need to use. |
|
You can use kernelstub as follows: This will add that kernel parameter to As you can see the kernel parameter we wanted to add is now on the Once you have added this parameter, you will need to reboot your machine for it to take effect. If for whatever reason you want remove it (e.g. this problem is fixed properly, or this doesn't fix your flickering issue), then you can do the following to remove the option: I hope that helps. Note, this is not a proper fix... it is more of a workaround that I discovered from the Intel-IOMMU kernel documentation:
|
|
Just to confirm, is anyone else seeing this on |
|
|
|
Same problem here, running Pop!_OS 20.04 on a Dell e7470. Seems to be a horizontal flickering of maximized windows. I have seen it on Firefox 95, Slack desktop client (4.22.0), and VS Code (1.63). It is perhaps triggered by scrolling vertically, but can persist for some seconds even when I stop scrolling. |
|
Pop OS has just updated the kernel from 5.15.5 to 5.15.8, the flickering is still occurring but less often than before, i think it might be fixed soon. |
|
I have not had this issue recently either. 🤞 |
|
On 5.15.8 it is very much reduced but not completely gone here. |
I'm doing a little better than that. Only a couple of times since I updated to 5.15.8. But not completely gone. |
|
I am using a Lemur Pro 9 with a fresh install of Pop OS 21.10. All updates have been applied. I'm also experiencing this issue. I don't think it's related to Chromium as I have Firefox installed. The issue happens infrequently, but it's still disconcerting. I think I've seen it happen while on a fullscreen terminal window. Sorry for what mostly amounts to a "me, too" post. I'm mostly just happy this is a known software issue and there's not a problem with my hardware. 😌 EDIT: |
|
I'm not sure if this ticket is even the right place for this issue. Is anyone here working on this? |
|
Update: disabling hardware acceleration provides a workaround for me. |
|
I just experienced it again in VSCode (Chromium-based...) while scrolling in the built-in terminal really fast. First time I've experienced it in days. |
|
For me it was better, not gone but better, for a while, since the 5.15.8 update. But in the past 1-2 days it has been bad, specifically Slack desktop client and VSCode. I have not rebooted since the update. Could that be having an effect. |
|
I experience it in the Brave Browser mostly, however, not limited to that alone. Last few messages for tail syslog |
|
Has this been fixed? the radio silence for the last two months makes me assume so, but in case it hasn't: had similar issues after running Ubuntu 20.04 with kernel 5.15.x. I could solve the problem by updating mesa to the latest 22.0 build (which is still in RC phase as of now), or more specifically, just updating libgl1-mesa-dri was enough. |
|
Purely anecdotal, but I haven't noticed it happening to me in about a month. |
|
Same here. No problems for a while. |
|
Good to hear. I'll close this issue for now. We can reopen if the bug returns. |
commit ba3beec upstream. Fix a crash that happens if an Rx only socket is created first, then a second socket is created that is Tx only and bound to the same umem as the first socket and also the same netdev and queue_id together with the XDP_SHARED_UMEM flag. In this specific case, the tx_descs array page pool was not created by the first socket as it was an Rx only socket. When the second socket is bound it needs this tx_descs array of this shared page pool as it has a Tx component, but unfortunately it was never allocated, leading to a crash. Note that this array is only used for zero-copy drivers using the batched Tx APIs, currently only ice and i40e. [ 5511.150360] BUG: kernel NULL pointer dereference, address: 0000000000000008 [ 5511.158419] #PF: supervisor write access in kernel mode [ 5511.164472] #PF: error_code(0x0002) - not-present page [ 5511.170416] PGD 0 P4D 0 [ 5511.173347] Oops: 0002 [#1] PREEMPT SMP PTI [ 5511.178186] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G E 5.18.0-rc1+ #97 [ 5511.187245] Hardware name: Intel Corp. GRANTLEY/GRANTLEY, BIOS GRRFCRB1.86B.0276.D07.1605190235 05/19/2016 [ 5511.198418] RIP: 0010:xsk_tx_peek_release_desc_batch+0x198/0x310 [ 5511.205375] Code: c0 83 c6 01 84 c2 74 6d 8d 46 ff 23 07 44 89 e1 48 83 c0 14 48 c1 e1 04 48 c1 e0 04 48 03 47 10 4c 01 c1 48 8b 50 08 48 8b 00 <48> 89 51 08 48 89 01 41 80 bd d7 00 00 00 00 75 82 48 8b 19 49 8b [ 5511.227091] RSP: 0018:ffffc90000003dd0 EFLAGS: 00010246 [ 5511.233135] RAX: 0000000000000000 RBX: ffff88810c8da600 RCX: 0000000000000000 [ 5511.241384] RDX: 000000000000003c RSI: 0000000000000001 RDI: ffff888115f555c0 [ 5511.249634] RBP: ffffc90000003e08 R08: 0000000000000000 R09: ffff889092296b48 [ 5511.257886] R10: 0000ffffffffffff R11: ffff889092296800 R12: 0000000000000000 [ 5511.266138] R13: ffff88810c8db500 R14: 0000000000000040 R15: 0000000000000100 [ 5511.274387] FS: 0000000000000000(0000) GS:ffff88903f800000(0000) knlGS:0000000000000000 [ 5511.283746] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5511.290389] CR2: 0000000000000008 CR3: 00000001046e2001 CR4: 00000000003706f0 [ 5511.298640] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 5511.306892] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 5511.315142] Call Trace: [ 5511.317972] <IRQ> [ 5511.320301] ice_xmit_zc+0x68/0x2f0 [ice] [ 5511.324977] ? ktime_get+0x38/0xa0 [ 5511.328913] ice_napi_poll+0x7a/0x6a0 [ice] [ 5511.333784] __napi_poll+0x2c/0x160 [ 5511.337821] net_rx_action+0xdd/0x200 [ 5511.342058] __do_softirq+0xe6/0x2dd [ 5511.346198] irq_exit_rcu+0xb5/0x100 [ 5511.350339] common_interrupt+0xa4/0xc0 [ 5511.354777] </IRQ> [ 5511.357201] <TASK> [ 5511.359625] asm_common_interrupt+0x1e/0x40 [ 5511.364466] RIP: 0010:cpuidle_enter_state+0xd2/0x360 [ 5511.370211] Code: 49 89 c5 0f 1f 44 00 00 31 ff e8 e9 00 7b ff 45 84 ff 74 12 9c 58 f6 c4 02 0f 85 72 02 00 00 31 ff e8 02 0c 80 ff fb 45 85 f6 <0f> 88 11 01 00 00 49 63 c6 4c 2b 2c 24 48 8d 14 40 48 8d 14 90 49 [ 5511.391921] RSP: 0018:ffffffff82a03e60 EFLAGS: 00000202 [ 5511.397962] RAX: ffff88903f800000 RBX: 0000000000000001 RCX: 000000000000001f [ 5511.406214] RDX: 0000000000000000 RSI: ffffffff823400b9 RDI: ffffffff8234c046 [ 5511.424646] RBP: ffff88810a384800 R08: 000005032a28c046 R09: 0000000000000008 [ 5511.443233] R10: 000000000000000b R11: 0000000000000006 R12: ffffffff82bcf700 [ 5511.461922] R13: 000005032a28c046 R14: 0000000000000001 R15: 0000000000000000 [ 5511.480300] cpuidle_enter+0x29/0x40 [ 5511.494329] do_idle+0x1c7/0x250 [ 5511.507610] cpu_startup_entry+0x19/0x20 [ 5511.521394] start_kernel+0x649/0x66e [ 5511.534626] secondary_startup_64_no_verify+0xc3/0xcb [ 5511.549230] </TASK> Detect such case during bind() and allocate this memory region via newly introduced xp_alloc_tx_descs(). Also, use kvcalloc instead of kcalloc as for other buffer pool allocations, so that it matches the kvfree() from xp_destroy(). Fixes: d1bc532 ("i40e: xsk: Move tmp desc array from driver to pool") Signed-off-by: Maciej Fijalkowski <[email protected]> Signed-off-by: Daniel Borkmann <[email protected]> Acked-by: Magnus Karlsson <[email protected]> Link: https://lore.kernel.org/bpf/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Distribution
Pop OS! 20.04 LTS
Related Application and/or Package Version
Issue/Bug Description:
The pages randomly flicker as if they were flashing
the issue occurs in the following situations:
The following applications display this issue:
Occurs in the following kernel:
Steps to reproduce
Expected behavior:
The page will not flicker
Other Notes:
sometimes the whole page flickers, sometimes only the bottom
does not occur in full screen videos
i wasn't able to record or screenshot the flickering unfortunately
the issue might be present in Chromium or other derivatives that i haven't tested (Vivaldi, Opera, Ungoogled Chromium, Chrome).
The text was updated successfully, but these errors were encountered: