You are not logged in.

#1 2020-02-05 21:56:37

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

[Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

[EDIT!]  My only solution was to blacklist (install /bin/true) the i915 module as it was loading sometimes with the errors listed below even though I never use, nor have I ever used, the onboard graphics chip. [/edit]

..and similar. Just recently I've begun receiving error messages when booting up, not EVERY boot, but most of the time. And when I do receive these errors I notice a significant change in performance. I may be searching the internet for the wrong thing but in doing so i've not really come up with anything to help me clear them up. There are usually a lot more, this is just one chunk I copy/pasted.  Some times I can go 2 or three days without these messages but most of the time its every day.

These errors began happening around the introduction of the 5.4 kernel, currently on 5.5.2, but when running 5.4.15 it rarely if ever happened. I do not know if it matters but I do NOT use onboard graphics, but an nvidia 1070 GTX card.  Below is a snippet of the errors, for full dmesg see:  https://pastebin.com/Gzn9tDTc

kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* render: timed out waiting for forcewake ack to clear.
kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* blitter: timed out waiting for forcewake ack to clear.
kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* media: timed out waiting for forcewake ack to clear.
kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* bcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* vcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* vecs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* bcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* vcs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: [drm:gen8_reset_engines [i915]] *ERROR* vecs'0 reset request timed out: {request: 00000004, RESET_CTL: ffffffff}
kernel: kvm: disabled by bios
kernel: [drm:gen9_set_dc_state [i915]] *ERROR* DC state mismatch (0x0 -> 0x3)
kernel: [drm:gen9_set_dc_state [i915]] *ERROR* Writing dc state to 0xfffffffe failed, now 0xffffffff
kernel: [drm:gen9_set_dc_state [i915]] *ERROR* DC state mismatch (0x2 -> 0x3)
kernel: [drm:gen9_set_dc_state [i915]] *ERROR* Writing dc state to 0xfffffffc failed, now 0xffffffff

Last edited by Wamakaska (2020-02-13 00:30:03)

Offline

#2 2020-02-05 22:07:24

loqs
Member
Registered: 2014-03-06
Posts: 9,823

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

You have not included the kernel version or the full dmesg output which would include it or details of the GPU hardware.

Offline

#3 2020-02-05 22:08:31

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

loqs wrote:

You have not included the kernel version or the full dmesg output which would include it or details of the GPU hardware.

You're right, I'm sorry. I should have waited until I could get that from home. Will update in a couple hours. My apologies.

Offline

#4 2020-02-06 02:26:22

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

EDITED original post to include full dmesg, and kernel info.

Offline

#5 2020-02-06 12:45:56

loqs
Member
Registered: 2014-03-06
Posts: 9,823

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

The dmesg was still incomplete possibly it overflowed the ring buffer.  You can extract it from the journal journal or add the boot option log_buf_len=2M.
The warnings are coming from the i915 driver used by the integrated GPU which seems strange if it is not being used.

Offline

#6 2020-02-06 15:02:27

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

loqs wrote:

The dmesg was still incomplete possibly it overflowed the ring buffer.  You can extract it from the journal journal or add the boot option log_buf_len=2M.
The warnings are coming from the i915 driver used by the integrated GPU which seems strange if it is not being used.

Forgive the multiple pastes, but pastbin only allowed 500ish bytes per paste. I used journalctl --since to pull the entire dmesg from last night's boot when the errors occured. They are broken into three parts, and they are in order:


https://pastebin.com/MfTRT7XT


https://pastebin.com/Uwq6r4c8


https://pastebin.com/vjeFxtWN


This is a clean boot, no errors or issues, from this morning before work.

https://pastebin.com/6vgRhgeH

Hope this helps. Thanks again for your time and trouble, loqs

Offline

#7 2020-02-06 18:03:04

loqs
Member
Registered: 2014-03-06
Posts: 9,823

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

First warning in dmesg is

------------[ cut here ]------------
Missing case (val == 65535)
WARNING: CPU: 0 PID: 508 at drivers/gpu/drm/i915/i915_drv.c:675 skl_dram_get_dimm_info+0xf8/0x1a0 [i915]
Modules linked in: eeepc_wmi(+) asus_wmi battery iTCO_wdt mei_hdcp iTCO_vendor_support sparse_keymap pcc_cpufreq(-) fjes(-) nvidia(POE+) i915(+) iwlmvm(+) wmi_bmof mxm_wmi acpi_cpufreq(-) mac80211 snd_sof_pci snd_sof_intel_byt x86_pkg_temp_thermal snd_sof_intel_ipc intel_powerclamp coretemp kvm_intel snd_sof_xtensa_dsp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda nls_iso8859_1 snd_sof libarc4 kvm snd_hda_ext_core snd_soc_acpi_intel_match nls_cp437 snd_soc_acpi iwlwifi ledtrig_audio snd_soc_core vfat snd_compress i2c_algo_bit fat irqbypass ac97_bus snd_pcm_dmaengine cfg80211 drm_kms_helper snd_hda_intel crct10dif_pclmul snd_intel_dspcfg crc32_pclmul ghash_clmulni_intel snd_hda_codec drm snd_hda_core aesni_intel snd_hwdep snd_pcm crypto_simd cryptd ofpart glue_helper ipmi_devintf cmdlinepart ipmi_msghandler intel_gtt intel_cstate snd_timer intel_spi_pci intel_spi agpgart intel_uncore snd spi_nor mei_me syscopyarea sysfillrect sysimgblt e1000e intel_rapl_perf mtd
 pcspkr i2c_i801 mei soundcore fb_sys_fops rfkill ie31200_edac wmi acpi_tad evdev mac_hid vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid sr_mod cdrom sd_mod ahci libahci libata xhci_pci xhci_hcd scsi_mod crc32c_intel
CPU: 0 PID: 508 Comm: modprobe Tainted: P           OE     5.5.2-arch1-1 #1
Hardware name: System manufacturer System Product Name/ROG MAXIMUS XI HERO (WI-FI), BIOS 1105 06/06/2019
RIP: 0010:skl_dram_get_dimm_info+0xf8/0x1a0 [i915]
Code: e1 00 03 66 81 f9 00 02 0f 84 93 00 00 00 f6 c4 02 0f 84 8a 00 00 00 48 c7 c6 60 ce 9e c1 48 c7 c7 64 ce 9e c1 e8 6a 82 82 f1 <0f> 0b 31 c0 c1 fb 0a 45 0f b6 04 24 bf 01 00 00 00 41 88 44 24 01
RSP: 0018:ffff96698107f9a0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 000000000000ffff RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000096 RDI: 00000000ffffffff
RBP: 000000000000004c R08: 00000000000003b6 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: ffff96698107fa28
R13: 0000000000000000 R14: ffff919301bc0000 R15: 0000000000000000
FS:  00007f7ad44cc740(0000) GS:ffff91931da00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f995560c780 CR3: 000000045b204003 CR4: 00000000003606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 skl_dram_get_channel_info+0x25/0x150 [i915]
 i915_driver_probe+0xeab/0x13d0 [i915]
 ? __kernfs_new_node+0x18b/0x1f0
 i915_pci_probe+0x54/0x150 [i915]
 ? _raw_spin_unlock_irqrestore+0x20/0x40
 local_pci_probe+0x42/0x80
 ? pci_match_device+0xd7/0x100
 pci_device_probe+0x104/0x1a0
 really_probe+0x147/0x3c0
 driver_probe_device+0xb6/0x100
 device_driver_attach+0x53/0x60
 __driver_attach+0x8a/0x150
 ? device_driver_attach+0x60/0x60
 ? device_driver_attach+0x60/0x60
 bus_for_each_dev+0x89/0xd0
 bus_add_driver+0x14d/0x1f0
 driver_register+0x6c/0xc0
 ? 0xffffffffc1abf000
 do_one_initcall+0x59/0x240
 do_init_module+0x5c/0x230
 load_module+0x2729/0x29e0
 ? __do_sys_init_module+0x169/0x190
 __do_sys_init_module+0x169/0x190
 do_syscall_64+0x4e/0x150
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f7ad45f7d2e
Code: 48 8b 0d 55 01 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 22 01 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffdb51e1498 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
RAX: ffffffffffffffda RBX: 00005622050b0d50 RCX: 00007f7ad45f7d2e
RDX: 0000562203b8a358 RSI: 0000000000493a29 RDI: 00005622058c43b0
RBP: 00005622058c43b0 R08: 00005622050b001a R09: 0000000000000000
R10: 00005622050b0010 R11: 0000000000000246 R12: 0000562203b8a358
R13: 0000000000000000 R14: 00005622050b0e60 R15: 00005622050b0d50
---[ end trace d8022c497553e076 ]---

Edit:
As the integrated GPU is not being used what if you blacklist the i915 module?
Normally I would suggest reporting the issue upstream but as the system uses the nvidia driver it is classed as tainted and not support by upstream.

Last edited by loqs (2020-02-06 19:37:07)

Offline

#8 2020-02-07 12:58:59

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

loqs wrote:

Edit:
As the integrated GPU is not being used what if you blacklist the i915 module?
Normally I would suggest reporting the issue upstream but as the system uses the nvidia driver it is classed as tainted and not support by upstream.

Good morning. I saw your post last night, before the "EDIT" and I thought maybe disabling the onboard gpu and setting "primary display" in "bios" to PCIe might fix it. Well, it worked fine last night but got the errors again this morning as I type this. I came back to this thread initially to ask if there was a way to blacklist the module i915 without it breaking anything else.

That being said, thank you for the suggestion and I'll give that a try when I get to work and see how that goes. Thank you again for your time.

Offline

#9 2020-02-12 22:34:58

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

Well, I blacklisted (install /bin/true that is because it was loading anyway from dependency I suppose) and obviously no more error. Is that ONLY use of that i915 module for onboard graphics?  If so I'll update this thread as [solved] and move on with my life. lol

Offline

#10 2020-02-12 22:42:49

loqs
Member
Registered: 2014-03-06
Posts: 9,823

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

Yes the i915 is solely for the integrated Intel GPU.

Offline

#11 2020-02-13 00:27:59

Wamakaska
Member
Registered: 2019-04-24
Posts: 11

Re: [Solved] kernel: [drm:gen9_set_dc_state [i915]] *ERROR*

loqs wrote:

Yes the i915 is solely for the integrated Intel GPU.

Thanks again for your help and time spent with my odd bug.  I'll mark this as Solved with an edit to the original post. Thank you!

Offline

Board footer

Powered by FluxBB