Created attachment 1804637 [details] kernel log from 5.11.16 1. Please describe the problem: i915 kernel driver emits a WARNING about dotclock mismatch when an integrated GPU (Intel IvyBridge Gen7/Intel HD Graphics 4000) is connected via HDMI to a 3440x1440 monitor. The GPU is capable of displaying that resolution only at 30Hz, while the monitor advertises vertical refresh of 60-100 only, but actually works when driven at 30Hz. I'm using this Modeline in Xorg: # 3440x1440 29.95 Hz (CVT) hsync: 43.96 kHz; pclk: 196.25 MHz Modeline "3440x1440" 196.25 3440 3600 3952 4464 1440 1443 1453 1468 -hsync +vsync The WARNING appears during boot, triggered by udev: Apr 28 00:00:53 kernel: i915 0000:00:02.0: FDI dotclock and encoder dotclock mismatch, fdi: 319749, encoder: 160000 Apr 28 00:00:53 kernel: WARNING: CPU: 2 PID: 353 at drivers/gpu/drm/i915/display/intel_display.c:14448 intel_pipe_config_sanity_check.part.0+0xb2/0xc0 [i915] or, with latest kernel-5.13.4: Jul 22 15:29:07 kernel: i915 0000:00:02.0: FDI dotclock and encoder dotclock mismatch, fdi: 319749, encoder: 160000 Jul 22 15:29:07 kernel: WARNING: CPU: 0 PID: 394 at drivers/gpu/drm/i915/display/intel_display.c:8371 intel_pipe_config_sanity_check.part.0+0xb2/0xc0 [i915] 2. What is the Version-Release number of the kernel: 5.11.16-300.fc34.x86_64 ... 5.13.4-200.fc34.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Unknown. I only started seeing this after I got a new 3440x1440 resolution monitor. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes. Connect a 3440x1440 display via HDMI to integrated Intel HD 4000 GPU. Boot. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Yes. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Attached.
Created attachment 1804638 [details] kernel log from 5.13.4
Still reproducible with 5.13.19: [ 2.567849] i915 0000:00:02.0: FDI dotclock and encoder dotclock mismatch, fdi: 319749, encoder: 160000 [ 2.567862] WARNING: CPU: 0 PID: 390 at drivers/gpu/drm/i915/display/intel_display.c:8385 intel_pipe_config_sanity_check.part.0+0xb2/0xc0 [i915]
Still occurring with 5.14.14 on F35: [ 2.782129] i915 0000:00:02.0: FDI dotclock and encoder dotclock mismatch, fdi: 319749, encoder: 160000 [ 2.782144] WARNING: CPU: 0 PID: 395 at drivers/gpu/drm/i915/display/intel_display.c:8749 intel_pipe_config_sanity_check.part.0+0xb2/0xc0 [i915]
Reported upstream.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 '35'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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.
For the record, this is no longer occurring with kernel 6.0.x.