Description of problem: fedora kernel still produce problem at kernel update 5.19.16 Version-Release number of selected component (if applicable): 5.19.16 How reproducible: use iris xe gpu, just after rebooting computer, screen flickers. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
screen package has nothing to do with graphical interface. Please, provide your window environment (X-window/wayland...) and reassign this report to proper component.
Created attachment 1920813 [details] No problem on grub2 screen
Created attachment 1920814 [details] Problem starts when log in intel i9-12900h iris xe fedora 36 kernel 5.19 and kernel 6.0
Created attachment 1920815 [details] No flickering problem in Microsoft Windows 11
Created attachment 1920816 [details] Problem does not disappear after adding panel self refresh=0
Created attachment 1920817 [details] Intel driver details shown in Microsoft window
I am using X-window.
Is this related to other users with iris xe too? I see this thread: https://bugzilla.redhat.com/show_bug.cgi?id=2027040 I have updated my kernel to 6.0 and 5.19, the problem is still here. Only the first installed kernel 5.18 is ok. Is there any way to solve the flickering screen problem. Thanks.
Hi I found a way, I copied the intel-gpu firmware bin and installed dkms through dnf; then dnf reduce my version to 6.0.5; then the whole screen does not flicker anymore. Thanks!
unfornately my problem reappear again. I saw from this webpage from intel,they said need to recompile kernel for intel i915 module. Maybe this is the problem for me, somehow kernel 6 doesnt have intel support for Iris Xe GPU: https://www.intel.com/content/www/us/en/develop/documentation/vtune-help/top/installation/set-up-system-for-gpu-analysis/rebuild-and-install-i915-module-centos.html
Hi, unfortunately the screen flickers again. After changing kernel version from 6.0.5 to 6.0.7, the flickering is the same. I compare 5.18.19 (the image distro) and 6.0.5 and found that guc firmware is using a different version. This could be the source of problem. Please see the dmesg | grep i915 output: [5.18.txt](https://github.com/intel-gpu/documentation/files/9976736/5.18.txt) [6.0.7.txt](https://github.com/intel-gpu/documentation/files/9976737/6.0.7.txt) kernel 6 is using GuC firmware i915/adlp_guc_70.1.1.bin version 70.1, and Finished loading DMC firmware i915/adlp_dmc_ver2_16.bin (v2.16), either one of it is causing the problem. ( i already checked [drm] Using Transparent Hugepages, this causes no difference)
Created attachment 1923463 [details] dmesg | grep i915 , kernel 5.18
Created attachment 1923464 [details] dmesg | grep i915 , kernel 6.0.7
Created attachment 1923469 [details] even after setting enable_guc=0, the problem of flickering remains. This is the dmesg of proof of disabling guc.
Created attachment 1923470 [details] This is the proof of screen flickering after 6.0.7 enable_guc=0 in kernel parameter.
Created attachment 1923472 [details] I have just updated to 6.1.0 and login the first time before any reboot. There is no problem right now But I can foresee after reboot, could have some screen flickering problem again.
Created attachment 1923485 [details] As expected the screen flicker on the fourth login. Now i upload the second login for reference.
Created attachment 1923486 [details] As expected the screen flicker on the fourth login. Now i upload the third login for reference.
Created attachment 1923487 [details] As expected the screen flicker on the fourth login. Now i upload the fourth login for reference. This is after i log in for the fourth login for a much longer time, and screen flicker again on reboot.
Created attachment 1925700 [details] upgraded to fedora 37, no luck. kernel 6.08 /sys/kernel/debug/dri/1/i915_gpu_info; you can see available engines: 41403. This is different from 5.18 available engines only: 417
Created attachment 1925701 [details] 5.18 sucessfuly i915_gpu_info in /sys/kernel/debug/dri/1/i915_gpu_info for comparison. I tried tuning many kernel parameters like firmware path. No luck.
Created attachment 1925702 [details] all kernel paramters used for tuning both in 6.0.8 to use 5.18 firmware. No luck.
You can see the dmesg that error does not have sufficient memory to lock given the iris xe gpu does not have memory space. Also, the number of engines are different for 5.18 versus 6.1.0. Is it because of the thread locking issue? I am not buying the intel K postfix processor. I simply do not have that money (next time I will be much more serious.) if I am going to install red hat or fedora image and wipe out my current image, will fedora install a safer back port and does not cause me screen flickering issue? Anyways, kernel 6.0 should provide intel kernel option to reduce the numbers of engines such that flickering screen should not happen due to no thread locking on the processor i9-12900h
Created attachment 1925794 [details] Please see summary highlight, kernel 6 has 40000+ engines. I want to switch back to 417 engines because my cpu has no thread lock (i9-12900h)
@airlied could you please reflect this to intel again. I found out why 5.18 works in intel iris xe (alder lake P) but kernel 5.19, 6.0.8 has violent screen flickering, my cpu is i9-12900h. This could be due to the number of engines in 5.18 is only 417 but the number of engines in 6.0.8 is 40000+. Could Intel please provide the option for me to switch back to 417 engines since my cpu do not have thread lock here.
Today I have tried intel solution first step: try a different port. Surprisingly it works well with hdmi. if i connect 6.0.8 kernel with hdmi, there is no flickering. I tried many times today, it works well. https://www.intel.com/content/www/us/en/support/articles/000026580/graphics.html Hopefully i do not need to buy a dummy hdmi screen after upgrade from mirror install kernel 5.18.16. because 5.18.16 works so well i thought there is never such a problem. Please find the attached photos and dmesg for this hdmi connection, no flickering after hdmi.
Created attachment 1929342 [details] after connecting to hdmi, kernel 6.0.10 fedora has no flickering. But if i disconnect, flickering happens again. It matches intels first step solution but either windows and 5.18.16 actually is ok.
Created attachment 1929343 [details] the dmesg log for hdmi connection, it works ok both for screen and hdmi tv. (stable voltage?)
still have flickering issue upgrading to kernel 6.0.11.....Seems i need to buy a dummy hdmi screen.
https://www.google.com/search?q=electrical+over+stress+on+linux&sxsrf=ALiCzsZZ09e38zab66ecJRKgqgEg0E7iTg:1670295739096&source=lnms&sa=X&ved=2ahUKEwimgcvBgOT7AhVtslYBHdaaCBsQ_AUoAHoECAoQAg&biw=1106&bih=663&dpr=2.25 I started to think this is Electrical Over Stress induced on the laptop monitor.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.