Opensuse 15.2 LXDE Desktop is installed on a Gigabyte B460D3H Board with Intel I3-10100 CPU, 16Gb Ram, 1 TB M3 SSD
Monitor is BENQ PD2705Q with Displayport Cable
when screensaver was active and desktop is unlocked, the system sometimes becomes very slow,
cpu load is constant high, desktop processes like firefox, konsole, scan tools become unusable slow.
cpu frequency is constanly at maximum for all 8 cores
I found that the i915 module processes a very high load of interrupts, more than 1 million/s
The list contains the data of /proc/cpuinfo and /proc/interrupts:
echo "$(date +%F-%T) $(awk '/MHz/ {printf "%9s ",$4}' /proc/cpuinfo) $(grep 'i915' /proc/interrupts)"
[FONT=monospace]2020-10-21-10:18:16 800.366 800.039 800.166 800.314 800.210 800.277 800.543 800.484 137: 0 0 0 0 398 579716 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:19:16 800.483 800.089 800.235 800.176 800.365 800.634 800.478 800.434 137: 0 0 0 0 398 579954 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:20:16 800.417 800.057 800.351 800.307 800.258 800.696 800.149 800.307 137: 0 0 0 0 398 580184 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:21:16 800.000 800.054 800.122 800.438 800.207 800.500 800.412 800.553 137: 0 0 0 0 398 580422 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:22:16 800.040 800.039 800.204 800.437 800.182 800.733 800.030 800.366 137: 0 0 0 0 398 580656 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:23:16 800.130 800.076 800.049 800.102 800.056 800.049 801.574 800.045 137: 0 0 0 0 398 580894 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:24:16 800.239 800.067 800.153 800.863 800.214 800.250 800.239 800.181 137: 0 0 0 0 398 581126 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:25:16 800.166 800.068 800.354 800.147 800.188 801.551 799.825 800.372 137: 0 0 0 0 398 581374 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:26:16 912.917 943.642 1032.277 1040.279 924.123 1073.795 1032.261 1046.515 137: 0 0 0 0 398 581604 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:27:16 800.492 800.037 800.241 800.177 800.207 800.768 800.117 800.369 137: 0 0 0 0 398 581858 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:28:16 800.186 800.092 800.300 800.676 800.167 801.066 800.409 800.305 137: 0 0 0 0 398 582098 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:29:16 800.574 800.083 800.188 800.157 800.150 800.502 800.118 800.843 137: 0 0 0 0 398 582354 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:30:16 800.489 800.069 800.123 800.187 800.129 800.916 800.355 800.619 137: 0 0 0 0 398 582590 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:31:16 800.134 800.050 800.418 800.300 800.152 800.492 800.493 800.120 137: 0 0 0 0 398 582824 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:32:16 800.130 800.081 800.420 800.305 800.235 801.640 800.285 800.178 137: 0 0 0 0 398 583074 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:33:16 800.370 800.081 800.473 800.184 800.268 800.304 800.174 800.171 137: 0 0 0 0 398 583318 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:34:16 4101.882 4143.658 4158.173 4175.679 4103.206 4173.128 4193.338 4178.095 137: 0 0 0 0 398 22968983 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:35:16 4101.608 4171.530 4116.046 4111.620 4102.600 4115.540 4100.012 4161.906 137: 0 0 0 0 398 92163509 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:36:16 4162.518 4196.653 4189.447 4128.979 4100.741 4198.077 4121.748 4198.920 137: 0 0 0 0 398 161017075 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:37:17 4100.185 4160.768 4141.846 4128.278 4102.020 4198.942 4158.041 4199.759 137: 0 0 0 0 398 230349384 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:38:17 4149.537 4200.992 4196.918 4190.235 4194.739 4292.502 4191.578 4189.890 137: 0 0 0 0 398 299853727 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:39:17 4100.082 4109.592 4187.675 4195.079 4111.271 4198.567 4200.532 4197.400 137: 0 0 0 0 398 369033143 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:40:17 4181.502 4202.592 4101.565 4197.114 4198.752 4198.995 4109.488 4146.100 137: 0 0 0 0 398 438413044 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:41:17 4111.629 4288.351 4174.000 4150.836 4106.992 4294.253 4195.982 4184.487 137: 0 0 0 0 398 506942368 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:42:17 4142.981 4180.061 4163.958 4191.408 4202.323 4199.040 4140.562 4190.925 137: 0 0 0 0 398 575963769 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:43:17 4201.473 4174.444 4130.858 4183.289 4190.457 4199.119 4103.876 4149.327 137: 0 0 0 0 398 645341514 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:44:17 4166.612 4145.298 4100.223 4137.215 4114.631 4172.002 4100.049 4162.034 137: 0 0 0 0 398 714088056 0 0 IR-PCI-MSI 32768-edge i915
2020-10-21-10:45:17 4176.863 4172.167 4108.465 4167.500 4195.920 4198.512 4136.155 4133.937 137: 0 0 0 0 398 783047127 0 0 IR-PCI-MSI 32768-edge i915
[/FONT]
At 10:34 I reactivated the desktop, switched on the Monitor and unlocked the screensaver
The interrupt storm can be stopped only by reboot.
Is there a fix for this problem?
All updates are installed
@highlander34 :
Is the ‘i915’ kernel module properly installed? – “lsmod | grep -i ‘i915’”
Is all the “i915” firmware properly installed?
Does the content of “/lib/firmware/i915/” verify against the content of the “kernel-firmware” RPM package?
You may have to forcibly re-install the Kernel firmware package: “zypper install --force kernel-firmware” …
dcurtisfra:
@highlander34 :
Is the ‘i915’ kernel module properly installed? – “lsmod | grep -i ‘i915’”
Is all the “i915” firmware properly installed?
Does the content of “/lib/firmware/i915/” verify against the content of the “kernel-firmware” RPM package?
You may have to forcibly re-install the Kernel firmware package: “zypper install --force kernel-firmware” …
the i915 module is loaded:
** #** lsmod | grep -i ‘i915’
i915 2371584 5
i2c_algo_bit 16384 1 i915
drm_kms_helper 229376 1 i915
drm 544768 6 drm_kms_helper,i915
video 53248 1 i915
and verify of the firmware package shows no error:
# rpm -v --verify kernel-firmware-20200107-lp152.1.1.noarch
......... /lib/firmware/i6050-fw-usb-1.5.sbcf
......... /lib/firmware/i915
......... /lib/firmware/i915/bxt_dmc_ver1.bin
......... /lib/firmware/i915/bxt_dmc_ver1_07.bin
......... /lib/firmware/i915/bxt_guc_32.0.3.bin
......... /lib/firmware/i915/bxt_guc_33.0.0.bin
......... /lib/firmware/i915/bxt_guc_ver8_7.bin
......... /lib/firmware/i915/bxt_guc_ver9_29.bin
......... /lib/firmware/i915/bxt_huc_2.0.0.bin
......... /lib/firmware/i915/bxt_huc_ver01_07_1398.bin
......... /lib/firmware/i915/bxt_huc_ver01_8_2893.bin
......... /lib/firmware/i915/cml_guc_33.0.0.bin
......... /lib/firmware/i915/cml_huc_4.0.0.bin
......... /lib/firmware/i915/cnl_dmc_ver1_06.bin
......... /lib/firmware/i915/cnl_dmc_ver1_07.bin
......... /lib/firmware/i915/ehl_guc_33.0.4.bin
......... /lib/firmware/i915/ehl_huc_9.0.0.bin
......... /lib/firmware/i915/glk_dmc_ver1_04.bin
......... /lib/firmware/i915/glk_guc_32.0.3.bin
......... /lib/firmware/i915/glk_guc_33.0.0.bin
......... /lib/firmware/i915/glk_huc_4.0.0.bin
......... /lib/firmware/i915/glk_huc_ver03_01_2893.bin
......... /lib/firmware/i915/icl_dmc_ver1_07.bin
......... /lib/firmware/i915/icl_dmc_ver1_09.bin
......... /lib/firmware/i915/icl_guc_32.0.3.bin
......... /lib/firmware/i915/icl_guc_33.0.0.bin
......... /lib/firmware/i915/icl_huc_9.0.0.bin
......... /lib/firmware/i915/icl_huc_ver8_4_3238.bin
......... /lib/firmware/i915/kbl_dmc_ver1.bin
......... /lib/firmware/i915/kbl_dmc_ver1_01.bin
......... /lib/firmware/i915/kbl_dmc_ver1_04.bin
......... /lib/firmware/i915/kbl_guc_32.0.3.bin
......... /lib/firmware/i915/kbl_guc_33.0.0.bin
......... /lib/firmware/i915/kbl_guc_ver9_14.bin
......... /lib/firmware/i915/kbl_guc_ver9_39.bin
......... /lib/firmware/i915/kbl_huc_4.0.0.bin
......... /lib/firmware/i915/kbl_huc_ver02_00_1810.bin
......... /lib/firmware/i915/skl_dmc_ver1.bin
......... /lib/firmware/i915/skl_dmc_ver1_23.bin
......... /lib/firmware/i915/skl_dmc_ver1_26.bin
......... /lib/firmware/i915/skl_dmc_ver1_27.bin
......... /lib/firmware/i915/skl_guc_32.0.3.bin
......... /lib/firmware/i915/skl_guc_33.0.0.bin
......... /lib/firmware/i915/skl_guc_ver1.bin
......... /lib/firmware/i915/skl_guc_ver4.bin
......... /lib/firmware/i915/skl_guc_ver6.bin
......... /lib/firmware/i915/skl_guc_ver6_1.bin
......... /lib/firmware/i915/skl_guc_ver9_33.bin
......... /lib/firmware/i915/skl_huc_2.0.0.bin
......... /lib/firmware/i915/skl_huc_ver01_07_1398.bin
......... /lib/firmware/i915/tgl_dmc_ver2_04.bin
......... /lib/firmware/i915/tgl_guc_35.2.0.bin
......... /lib/firmware/i915/tgl_huc_7.0.3.bin
......... /lib/firmware/imx
The system was reinstalled ar least 2 times and the problem showed up from the first install and with all kernel updates
I tried also some kernel boot i915.parameters like
i915.enable_dc=0 i915.enable_fbc=0 i915.reset=1 i915.disable_power_well=1 i915.verbose_state_checks=1 i915.enable_guc=2
in almost all combinations and values
with disabled display powersave mode the problem occurs less often, rest of system is never in powersave mode and running 24/7
mrmazda
October 23, 2020, 7:12am
#4
If you are using the Intel DDX driver, try the (default) modesetting DDX driver; or vice versa. Some guidance on what this means, and how to implement a switch, can be found in this primer thread .
mrmazda
October 23, 2020, 7:17am
#5
I3-10100 is Comet Lake (10th gen). Doesn’t it require i965 or an even newer intel kernel module for proper support? Maybe 15.2’s standard kernel isn’t new enough or hasn’t enough backports to support it properly.
“/usr/lib64/dri/i965_dri.so” is part of the “Mesa-dri” RPM package … – this ArchLinux thread: <https://bbs.archlinux.org/viewtopic.php?id=193563 >.
Maybe, the X11 or Wayland environment needs to be checked to see if, the graphics are picking up the i965 driver …
I tested also the 5.4.71 kernel with same result, but I think it was also startet before the I3-10100 was released(?)
There is no “i965” in both kernels module dirs
highlander34:
the i915 module is loaded:
…
The system was reinstalled ar least 2 times and the problem showed up from the first install and with all kernel updates
I tried also some kernel boot i915.parameters like
[FONT=monospace]i915.enable_dc=0 i915.enable_fbc=0 i915.reset=1 i915.disable_power_well=1 i915.verbose_state_checks=1 i915.enable_guc=2
in almost all combinations and values
with disabled display powersave mode the problem occurs less often, rest of system is never in powersave mode and running 24/7
openSUSE goofed with amdgpu while Fedora and Manjaro were fine: https://bugzilla.opensuse.org/show_bug.cgi?id=1177428 You may try to get a second opinion from these.
mrmazda:
If you are using the Intel DDX driver, try the (default) modesetting DDX driver; or vice versa. Some guidance on what this means, and how to implement a switch, can be found in this primer thread .
The problem seems to be related to graphics powersave mode when monitor is turned off.
If monitor is turned on after gpu/video output is reactivated from powersave (by mouse or keyboard) the interrupt storm occurs very often.
I can try to change the DDX driver, but currently I am busy with other development and I thought hacking in the linux system is not required anymore today…
mrmazda
October 26, 2020, 10:26pm
#10
I don’t consider reverting to the default DDX driver to be hacking. It’s newer technology than the drivers provided by xf86-video-* (yet more than 7 years old), which to me implies it should be enjoying more developer devotion. The reason the default doesn’t get used much has to do with maintaining support for antique and non-AMD/Intel/NVidia graphics, which the Modesetting DDX driver mostly doesn’t support. AFAICT, choosing the optimal DDX driver for antiques is too complicated for the Xorg automagic system.
mrmazda:
I don’t consider reverting to the default DDX driver to be hacking. It’s newer technology than the drivers provided by xf86-video-* (yet more than 7 years old), which to me implies it should be enjoying more developer devotion. The reason the default doesn’t get used much has to do with maintaining support for antique and non-AMD/Intel/NVidia graphics, which the Modesetting DDX driver mostly doesn’t support. AFAICT, choosing the optimal DDX driver for antiques is too complicated for the Xorg automagic system.
All powersave and screensaver/lock was disabled, monitor was never turned off automaticaly and nothing was locked,
but I turned it off by power button yesterday evening and when i turned it on this morning the high interrupt load startet.
highlander34:
All powersave and screensaver/lock was disabled, monitor was never turned off automaticaly and nothing was locked,
but I turned it off by power button yesterday evening and when i turned it on this morning the high interrupt load startet.
Bought a LG 24EB23PM-B back in 2014 and never experienced problems with the i3-4130 or the i7-6700K since then:
erlangen:~ # inxi -G
Graphics: Device-1: Intel HD Graphics 530 driver: **i915** v: kernel
Display: server: X.Org 1.20.9 driver: **intel** unloaded: fbdev,modesetting,vesa resolution: 1920x1200~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.2.1
erlangen:~ #
Packages installed:
erlangen:~ # zypper se -is intel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-----------------------+---------+--------------------------------+--------+---------------------------
i+ | intel-hybrid-driver | package | 1.0.2-5.3 | x86_64 | openSUSE-20191106-0
i | intel-media-driver | package | 20.3.0-1.1 | x86_64 | openSUSE-20191106-0
i | intel-vaapi-driver | package | 2.4.1-2.1 | x86_64 | openSUSE-20191106-0
i | kernel-firmware-intel | package | 20201005-3.1 | noarch | openSUSE-Tumbleweed-Update
i | libdrm_intel1 | package | 2.4.102-2.1 | x86_64 | openSUSE-20191106-0
i+ | libvulkan_intel | package | 20.2.1-265.1 | x86_64 | openSUSE-20191106-0
i | ucode-intel | package | 20200616-1.2 | x86_64 | openSUSE-20191106-0
i+ | xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-5.4 | x86_64 | openSUSE-20191106-0
erlangen:~ #
I switched the DDX driver by uninstalling the xorg-x11-driver-video and xf86-video-* packages as described in
https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-graphics-driver-primer
The problem did not change, but I found an easy way to reproduce the interrupt storm immediately:
while true; do echo "$(date +%T) $(cat /proc/interrupts | grep "i915")"; sleep 1; done
11:02:46 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:47 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:48 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:49 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:50 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
monitor is turned off (still with electrical power)
11:02:51 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:52 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:53 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:54 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:55 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:56 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:57 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:58 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:02:59 137: 0 0 0 0 394 64 0 0 IR-PCI-MSI 32768-edge i915
11:03:00 137: 0 0 0 0 394 68 0 0 IR-PCI-MSI 32768-edge i915
11:03:01 137: 0 0 0 0 394 68 0 0 IR-PCI-MSI 32768-edge i915
monitor is turned on
11:03:02 137: 0 0 0 0 394 690164 0 0 IR-PCI-MSI 32768-edge i915
11:03:03 137: 0 0 0 0 394 1868443 0 0 IR-PCI-MSI 32768-edge i915
11:03:04 137: 0 0 0 0 394 3106460 0 0 IR-PCI-MSI 32768-edge i915
11:03:05 137: 0 0 0 0 394 4354082 0 0 IR-PCI-MSI 32768-edge i915
11:03:07 137: 0 0 0 0 394 5492762 0 0 IR-PCI-MSI 32768-edge i915
No powersave, no screensaver, no mouse move or anything else.
Tested with BENQ PD2705 and Lenovo 24" Thinkvision, both connected with Displayport cable
I think the i915 module is broken and does not handle the new Intel 10100 CPU correctly, or maybe Gigabyte B460D3H board
highlander34:
No powersave, no screensaver, no mouse move or anything else.
Tested with BENQ PD2705 and Lenovo 24" Thinkvision, both connected with Displayport cable
I think the i915 module is broken and does not handle the new Intel 10100 CPU correctly, or maybe Gigabyte B460D3H board
Guessing does not solve problems. Did you ever test with a live stick or another distribution?
BTW: The HP Laptop 15-da0xxx suspends/resumes without any issues even when an old fashioned LG TV is attached. But it chokes when NetworkManager is enabled.
karlmistelberger:
Guessing does not solve problems. Did you ever test with a live stick or another distribution?
BTW: The HP Laptop 15-da0xxx suspends/resumes without any issues even when an old fashioned LG TV is attached. But it chokes when NetworkManager is enabled.
I tested with Suse 42.3 on a USB disk:
lsmod | grep -i i915
i915 1339392 0
drm_kms_helper 155648 1 i915
drm 393216 2 i915,drm_kms_helper
i2c_algo_bit 16384 1 i915
video 45056 1 i915
button 16384 1 i915
in the /proc/interrupts there is no “i915” interrupt assigned
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 32 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer
1: 14 0 0 0 1619 0 0 0 IR-IO-APIC 1-edge i8042
5: 0 0 0 0 0 0 0 0 IR-IO-APIC 5-edge parport0
8: 0 0 0 0 1 0 0 0 IR-IO-APIC 8-edge rtc0
9: 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi
120: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0
121: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1
122: 0 0 0 0 0 0 0 0 IR-PCI-MSI 442368-edge aerdrv
123: 0 0 0 0 0 0 0 0 IR-PCI-MSI 475136-edge aerdrv
124: 12 0 0 27 65 245 0 0 IR-PCI-MSI 376832-edge ahci[0000:00:17.0]
125: 25 0 0 0 0 0 0 0 IR-PCI-MSI 2621440-edge nvme0q0, nvme0q1
126: 15879 0 0 0 54579 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd
127: 0 35 0 0 0 0 0 0 IR-PCI-MSI 2621441-edge nvme0q2
128: 0 0 27 0 0 0 0 0 IR-PCI-MSI 2621442-edge nvme0q3
129: 0 0 0 90 0 0 0 0 IR-PCI-MSI 2621443-edge nvme0q4
130: 0 0 0 0 126 0 0 0 IR-PCI-MSI 2621444-edge nvme0q5
131: 0 0 0 0 0 160 0 0 IR-PCI-MSI 2621445-edge nvme0q6
132: 0 0 0 0 0 0 38 0 IR-PCI-MSI 2621446-edge nvme0q7
133: 0 0 0 0 0 0 0 542 IR-PCI-MSI 2621447-edge nvme0q8
134: 321 0 0 0 1338 0 0 0 IR-PCI-MSI 514048-edge snd_hda_intel
NMI: 0 0 0 0 0 0 0 0 Non-maskable interrupts
LOC: 11583 13083 11632 12737 13101 12511 9613 11004 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 0 0 0 0 Performance monitoring interrupts
IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts
RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries
RES: 1252 606 371 284 495 275 235 254 Rescheduling interrupts
CAL: 2477 2429 2623 2711 2179 3395 2478 2287 Function call interrupts
TLB: 1505 1461 1712 1725 1137 2376 1574 1319 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 3 3 3 3 3 3 3 3 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event
PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event
I could not reproduce the interrupt problem on opensuse 42.3
at least not in the same way with monitor off/on as on 15.2
Suse 15.2 has also much more firmware for i915 than suse 42.3:
ls -l /lib/firmware/i915/ /mnt/c/lib/firmware/i915/
/lib/firmware/i915/:
total 8352
lrwxrwxrwx 1 root root 19 Mar 1 2020 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin
-rw-r--r-- 1 root root 8380 Mar 1 2020 bxt_dmc_ver1_07.bin
-rw-r--r-- 1 root root 176256 Mar 1 2020 bxt_guc_32.0.3.bin
-rw-r--r-- 1 root root 181888 Mar 1 2020 bxt_guc_33.0.0.bin
-rw-r--r-- 1 root root 140928 Mar 1 2020 bxt_guc_ver8_7.bin
-rw-r--r-- 1 root root 146432 Mar 1 2020 bxt_guc_ver9_29.bin
-rw-r--r-- 1 root root 149824 Mar 1 2020 bxt_huc_2.0.0.bin
-rw-r--r-- 1 root root 154432 Mar 1 2020 bxt_huc_ver01_07_1398.bin
-rw-r--r-- 1 root root 146880 Mar 1 2020 bxt_huc_ver01_8_2893.bin
-rw-r--r-- 1 root root 182912 Mar 1 2020 cml_guc_33.0.0.bin
-rw-r--r-- 1 root root 226048 Mar 1 2020 cml_huc_4.0.0.bin
-rw-r--r-- 1 root root 11224 Mar 1 2020 cnl_dmc_ver1_06.bin
-rw-r--r-- 1 root root 11268 Mar 1 2020 cnl_dmc_ver1_07.bin
-rw-r--r-- 1 root root 396288 Mar 1 2020 ehl_guc_33.0.4.bin
-rw-r--r-- 1 root root 498880 Mar 1 2020 ehl_huc_9.0.0.bin
-rw-r--r-- 1 root root 8800 Mar 1 2020 glk_dmc_ver1_04.bin
-rw-r--r-- 1 root root 176640 Mar 1 2020 glk_guc_32.0.3.bin
-rw-r--r-- 1 root root 182336 Mar 1 2020 glk_guc_33.0.0.bin
-rw-r--r-- 1 root root 226048 Mar 1 2020 glk_huc_4.0.0.bin
-rw-r--r-- 1 root root 222080 Mar 1 2020 glk_huc_ver03_01_2893.bin
-rw-r--r-- 1 root root 25716 Mar 1 2020 icl_dmc_ver1_07.bin
-rw-r--r-- 1 root root 25952 Mar 1 2020 icl_dmc_ver1_09.bin
-rw-r--r-- 1 root root 380096 Mar 1 2020 icl_guc_32.0.3.bin
-rw-r--r-- 1 root root 385280 Mar 1 2020 icl_guc_33.0.0.bin
-rw-r--r-- 1 root root 498880 Mar 1 2020 icl_huc_9.0.0.bin
-rw-r--r-- 1 root root 488960 Mar 1 2020 icl_huc_ver8_4_3238.bin
lrwxrwxrwx 1 root root 19 Mar 1 2020 kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 8616 Mar 1 2020 kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 8840 Mar 1 2020 kbl_dmc_ver1_04.bin
-rw-r--r-- 1 root root 176448 Mar 1 2020 kbl_guc_32.0.3.bin
-rw-r--r-- 1 root root 182912 Mar 1 2020 kbl_guc_33.0.0.bin
-rw-r--r-- 1 root root 142656 Mar 1 2020 kbl_guc_ver9_14.bin
-rw-r--r-- 1 root root 147776 Mar 1 2020 kbl_guc_ver9_39.bin
-rw-r--r-- 1 root root 226048 Mar 1 2020 kbl_huc_4.0.0.bin
-rw-r--r-- 1 root root 218688 Mar 1 2020 kbl_huc_ver02_00_1810.bin
lrwxrwxrwx 1 root root 19 Mar 1 2020 skl_dmc_ver1.bin -> skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 8824 Mar 1 2020 skl_dmc_ver1_23.bin
-rw-r--r-- 1 root root 8928 Mar 1 2020 skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 8928 Mar 1 2020 skl_dmc_ver1_27.bin
-rw-r--r-- 1 root root 175552 Mar 1 2020 skl_guc_32.0.3.bin
-rw-r--r-- 1 root root 182080 Mar 1 2020 skl_guc_33.0.0.bin
-rw-r--r-- 1 root root 109636 Mar 1 2020 skl_guc_ver1.bin
-rw-r--r-- 1 root root 128320 Mar 1 2020 skl_guc_ver4.bin
lrwxrwxrwx 1 root root 18 Mar 1 2020 skl_guc_ver6.bin -> skl_guc_ver6_1.bin
-rw-r--r-- 1 root root 129024 Mar 1 2020 skl_guc_ver6_1.bin
-rw-r--r-- 1 root root 147520 Mar 1 2020 skl_guc_ver9_33.bin
-rw-r--r-- 1 root root 136320 Mar 1 2020 skl_huc_2.0.0.bin
-rw-r--r-- 1 root root 140992 Mar 1 2020 skl_huc_ver01_07_1398.bin
-rw-r--r-- 1 root root 18436 Mar 1 2020 tgl_dmc_ver2_04.bin
-rw-r--r-- 1 root root 417728 Mar 1 2020 tgl_guc_35.2.0.bin
-rw-r--r-- 1 root root 521408 Mar 1 2020 tgl_huc_7.0.3.bin
/mnt/c/lib/firmware/i915/:
total 1232
lrwxrwxrwx 1 root root 19 Mar 7 2019 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin
-rw-r--r-- 1 root root 8380 May 30 2017 bxt_dmc_ver1_07.bin
-rw-r--r-- 1 root root 140928 May 30 2017 bxt_guc_ver8_7.bin
-rw-r--r-- 1 root root 154432 May 30 2017 bxt_huc_ver01_07_1398.bin
lrwxrwxrwx 1 root root 19 Mar 7 2019 kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 8616 May 30 2017 kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 142656 May 30 2017 kbl_guc_ver9_14.bin
-rw-r--r-- 1 root root 218688 May 30 2017 kbl_huc_ver02_00_1810.bin
lrwxrwxrwx 1 root root 19 Mar 7 2019 skl_dmc_ver1.bin -> skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 8824 May 30 2017 skl_dmc_ver1_23.bin
-rw-r--r-- 1 root root 8928 May 30 2017 skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 109636 May 30 2017 skl_guc_ver1.bin
-rw-r--r-- 1 root root 128320 May 30 2017 skl_guc_ver4.bin
lrwxrwxrwx 1 root root 18 Mar 7 2019 skl_guc_ver6.bin -> skl_guc_ver6_1.bin
-rw-r--r-- 1 root root 129024 May 30 2017 skl_guc_ver6_1.bin
-rw-r--r-- 1 root root 140992 May 30 2017 skl_huc_ver01_07_1398.bin
This is the boot.msg of suse 15.2 for i915
6> 3.028247] i915 0000:00:02.0: vgaarb: deactivate vga console
<6> 3.029735] Console: switching to colour dummy device 80x25
<6> 3.031764] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
<6> 3.031772] [drm] Driver supports precise vblank timestamp query.
<6> 3.032462] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
<6> 3.032824] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
<6> 3.046195] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0
<6> 3.048070] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
<6> 3.048334] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input1
<7> 3.064656] sr 1:0:0:0: Attached scsi CD-ROM sr0
<6> 3.079815] fbcon: i915drmfb (fb0) is primary device
<6> 3.127662] Console: switching to colour frame buffer device 160x45
<6> 3.166826] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
i
This is the boot.msg of suse 15.2 for i915
6> 3.028247] i915 0000:00:02.0: vgaarb: deactivate vga console
<6> 3.029735] Console: switching to colour dummy device 80x25
<6> 3.031764] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
<6> 3.031772] [drm] Driver supports precise vblank timestamp query.
<6> 3.032462] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
<6> 3.032824] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
<6> 3.046195] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0
<6> 3.048070] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
<6> 3.048334] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input1
<7> 3.064656] sr 1:0:0:0: Attached scsi CD-ROM sr0
<6> 3.079815] fbcon: i915drmfb (fb0) is primary device
<6> 3.127662] Console: switching to colour frame buffer device 160x45
<6> 3.166826] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
I removed the i915/kbl_dmc_ver1_04.bin file from the initrd and loading failed on boot,
but this changed nothing on the interrupt problem
Downgrade to kernel 4.4.240 or kick suse15.2 and return to 42.3?
When I encountered problems with i915 I moved forward to Tumbleweed: https://forums.opensuse.org/showthread.php/519529-Konsole-With-quot-su-quot-Freezing-The-System?highlight=i915 Backporting is slow and complicated. You may be better off using Tumbleweed. I never experienced trouble with i915 since 2016.
…or perhaps submit a bug report?
I have filed a bug report https://gitlab.freedesktop.org/drm/intel/-/issues/2609
should I create it here too?
Svyatko
November 5, 2020, 7:12pm
#20
Yes.
And try to use new kernel + new firmware from Kernel:stable repo.