• 6.12-rc3 crashes in ~half hour after boot (i915 related?)

    vojtagrec

    By vojtagrec

      • Urgent

    After I updated from rc2 to rc3, the server crashes on me usually within half an hour after booting. The system freezes, web UI unresponsive, sometimes I manage to log in via SSH but in the end I have to hard-reset the server (more specifically, I have to power off the server with a long press and then start again – pressing reset or short-pressing power button does nothing, as does running "reboot" in SSH console).

     

    Because of the crash causing web UI to stop responding, I was unable to get diagnostics at that moment – the attached diagnostics are right after a boot with rc3 (before the crash). One time I managed to be logged in via SSH when it crashed and got the "dmesg" output (attached). Seems to be related to "i915" and the symptoms in general seem to be similar to this old issue.

     

    I did the upgrade in the middle of the night, so even though I have a few Docker containers set to autostart, nobody was really using the server (= no transcoding in Plex etc.), it was just idling and still crashed nevertheless.

     

    I did change some BIOS settings (enabled some power optimizations and set fan curves) before booting into rc3 but now that I reverted back to rc2 everything seems to run fine with the same BIOS setup (running for 20h without a crash now), so I don't think my BIOS changes play a role in this issue.

     

    Please let me know if you need me to run some more tests.

     

    nibbler-diagnostics-20230416-0122.zip dmesg.txt

    Go to reports Prereleases

    User Feedback

    Recommended Comments



    Craig Dennis

    @ich777 I followed your guide above (still on rc-6) and the system crashed at the usual time. I will try with other DC values on rc-6 before upgrading to rc-7 (although I might skip it if the fix has a regression as reported above).

    Can someone confirm this working on rc-7?

    Link to comment
    ich777
    12 hours ago, Craig Dennis said:

    @ich777 I followed your guide above (still on rc-6) and the system crashed at the usual time. I will try with other DC values on rc-6 before upgrading to rc-7 (although I might skip it if the fix has a regression as reported above).

    Your issue seems to be different since power well is something completely differnt, have you yet tried to disable power well?

     

    You can do that by adding this to your syslinux.config 

    i915.disable_power_well=1

     

    If the options do nothing for you (as you've previously mentioned the option enable_dc=0 in your case), you can always blacklist the module so that Unraid doesn't load it automatically on boot and enabling it in the go file like mentioned in my previous post with the line: 

    modprobe i915 disable_power_well=1

    or: 

    modprobe i915 disable_power_well=1 enable_dc=0

     

     

    Attention: If you have my Intel GPU TOP plugin installed it will also activate the iGPU so I would recommend that you uninstall it first before trying these options.

    Link to comment
    Craig Dennis
    31 minutes ago, ich777 said:

    Attention: If you have my Intel GPU TOP plugin installed it will also activate the iGPU so I would recommend that you uninstall it first before trying these options.


    @ich777 Awesome. Thanks. Maybe a silly question, will I be able to use the Intel GPU TOP plugin after I have changed these settings?

    Link to comment
    ich777
    1 minute ago, Craig Dennis said:

    @ich777 Awesome. Thanks. Maybe a silly question, will I be able to use the Intel GPU TOP plugin after I have changed these settings?

    Intel GPU Top should append the arguments that you've added to the sysllinux.config but you have to try.

    I can always modify the plugin so that you can append things there.

    Link to comment
    Craig Dennis
    1 hour ago, ich777 said:

    You can do that by adding this to your syslinux.config 

    i915.disable_power_well=1

     

    If the options do nothing for you (as you've previously mentioned the option enable_dc=0 in your case), you can always blacklist the module so that Unraid doesn't load it automatically on boot and enabling it in the go file like mentioned in my previous post with the line: 

    modprobe i915 disable_power_well=1

    or: 

    modprobe i915 disable_power_well=1 enable_dc=0


    syslinux,config changes did not have any effect.
    I tried both modprobe commands and rebooted between; server still crashes at the 20-30 min mark.

    I will try updating to rc-7 next

     

    Link to comment
    JorgeB
    On 6/6/2023 at 6:56 PM, vojtagrec said:

    I just upgraded to rc7 and got a crash too. It looks like there is some regression, I had the enable_dc=0 applied via /boot/config/modprobe.d/i915.conf and it worked perfectly fine with rc6 but it seems to not work with rc7

    This should be fixed in rc8, please re-test.

    Link to comment
    Craig Dennis

    For what it's worth, when I installed a discrete GPU and still used the iGPU (both enabled in bios - GPU passed through to a VM) the system stopped crashing (was running rc-7).

    Link to comment
    vojtagrec
    10 hours ago, JorgeB said:

    This should be fixed in rc8, please re-test.

     

    Removed the i915 option from kernel cmdline in Syslinux Config, kept the option in modprobe.d, updated to rc8 and so far everything looks fine, cat /sys/module/i915/parameters/enable_dc returns 0 and there are no crashes.

    • Like 2
    Link to comment
    Craig Dennis

    Running rc8 and for whatever reason I am unable to make `enable_dc=0` stick.

    @ich777 I must be doing something wrong. It resets to -1 every reboot.

    When I run through the commands again (remove/rescan etc.) I get the following error: 

    libkmod: kmod_config_parse: /etc/modprobe.d/i915.conf line 1: ignoring bad line starting with 'enable_dc=0'



    I have it applied via `/boot/config/modprobe.d/i915.conf`

    1442642589_Terminal2023-06-21at14_10.49@2x.thumb.jpg.458f95add9942d8563ca6f7129266703.jpg

     

    I have it in the `syslinux.config` in the flash page

    1100539883_Arc2023-06-21at14_09.49@2x.thumb.jpg.e7d46a2a3ba89cdcab96d649e40e2f86.jpg

     

    But whenever I reboot and `cat /sys/module/i915/parameters/enable_dc` I get `-1`

     

    798541919_Arc2023-06-21at14_29.21@2x.thumb.jpg.38261f72eccea0b2e5f4608440352dd2.jpg

    Edited by Craig Dennis
    Link to comment
    ich777
    1 hour ago, Craig Dennis said:

    I have it applied via `/boot/config/modprobe.d/i915.conf`

    It seems that you are trying to applying it in multiple places and hope that one is working which is definitely not the way to do it.

     

    1 hour ago, Craig Dennis said:

     

    1442642589_Terminal2023-06-21at14_10.49@2x.thumb.jpg.458f95add9942d8563ca6f7129266703.jpg

    Please remove the line with the modprobe or comment it since this won't do anything because the module is already load at that stage.

     

    1 hour ago, Craig Dennis said:

    I have it in the `syslinux.config` in the flash page

    Also remove these lines for the i915 module because this is not how you would append that.

     

    1 hour ago, Craig Dennis said: 
    libkmod: kmod_config_parse: /etc/modprobe.d/i915.conf line 1: ignoring bad line starting with 'enable_dc=0'

    Where are the contents from this file? They should be: 

    options i915 enable_dc=0

    (please note that if you are using the default editor from OSX it will destroy the formatting and Linux can't read it)

     

    1 hour ago, Craig Dennis said:

    Running rc8 and for whatever reason I am unable to make `enable_dc=0` stick.

    Why are you not on 6.12.1 since it is now stable and try it there?

    Link to comment
    Craig Dennis
    Quote

    It seems that you are trying to applying it in multiple places and hope that one is working which is definitely not the way to do it.

    Fair. I'm just trying to follow instructions from the thread.

     

    38 minutes ago, ich777 said:

    Why are you not on 6.12.1 since it is now stable and try it there?

    Sorry, I am mistaken. I am on 6.12.0 (I forgot I updated when it became available).

     

    38 minutes ago, ich777 said:
    1 hour ago, Craig Dennis said: 
    libkmod: kmod_config_parse: /etc/modprobe.d/i915.conf line 1: ignoring bad line starting with 'enable_dc=0'

    Where are the contents from this file? They should be: 

    options i915 enable_dc=0

    (please note that if you are using the default editor from OSX it will destroy the formatting and Linux can't read it)

     

    The contents have only ever shown `enable_dc=0` but the OSX formatting makes sense (as the error never occurred until today when I ssh'd in)

    Edited by Craig Dennis
    Link to comment
    Craig Dennis

    @ich777 I appreciate your help.

    So what are the steps I actually need to perform?
    The issue is still happening on 6.12.1. I removed everything I entered previously (I think) and then I went back through the steps you mentioned earlier:     

    libkmod: kmod_config_parse: /etc/modprobe.d/i915.conf line 1: ignoring bad line starting with 'enable_dc=0'


    Attached is diagnostics from just after the reboot. I have set up a syslog server and mirrored it to flash; also attached. I don't see any other errors though (like power_well).

    sakaar-diagnostics-20230622-2129.zip syslog (1)

    Edited by Craig Dennis
    Link to comment
    vojtagrec
    3 hours ago, Craig Dennis said:

    @ich777 I appreciate your help.

    So what are the steps I actually need to perform?
    The issue is still happening on 6.12.1. I removed everything I entered previously (I think) and then I went back through the steps you mentioned earlier:     

    libkmod: kmod_config_parse: /etc/modprobe.d/i915.conf line 1: ignoring bad line starting with 'enable_dc=0'


    Attached is diagnostics from just after the reboot. I have set up a syslog server and mirrored it to flash; also attached. I don't see any other errors though (like power_well).

    sakaar-diagnostics-20230622-2129.zip syslog (1)


    The error message sounds like you got the contents of i915.conf still wrong (“line starting with ‘enable_dc=0’”). Are you sure the line in that file really is  

    options i915 enable_dc=0

    ?

    Link to comment
    ich777
    11 hours ago, Craig Dennis said: 
    libkmod: kmod_config_parse: /etc/modprobe.d/i915.conf line 1: ignoring bad line starting with 'enable_dc=0'

    Exactly that is the case what @vojtagrec said, the contents of your file /boot/config/modprobe.d/i915.conf are: 

    enable_dc=0

    whereas it should be: 

    options i915 enable_dc=0

     

    The path from the file that you have to change is: 

    /boot/config/modprobe.d/i915.conf

     

    After you've changed that you have to reboot!

    • Like 1
    Link to comment
    Mainfrezzer

    Having a look at my log in 6.12.3 lets me guess that this issue didnt get fixed after all?

      

    Jul 27 08:41:08 unraid-box kernel: ------------[ cut here ]------------
Jul 27 08:41:08 unraid-box kernel: i915 0000:00:02.0: Unexpected DBuf power power state (0x00000000, expected 0x00000001)
Jul 27 08:41:08 unraid-box kernel: WARNING: CPU: 1 PID: 9864 at drivers/gpu/drm/i915/display/intel_display_power_well.c:950 gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:08 unraid-box kernel: Modules linked in: xt_connmark xt_mark iptable_mangle xt_comment iptable_raw xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter veth xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_nat iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_pclmul drm_kms_helper crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel processor_thermal_device_pci_legacy processor_thermal_device crypto_simd drm cryptd processor_thermal_rfim processor_thermal_mbox rapl
Jul 27 08:41:08 unraid-box kernel: mei_pxp mei_hdcp intel_rapl_msr processor_thermal_rapl intel_cstate i2c_i801 intel_gtt agpgart intel_rapl_common syscopyarea i2c_smbus sysfillrect intel_soc_dts_iosf r8169 i2c_core ahci mei_me sysimgblt realtek libahci fb_sys_fops iosf_mbi thermal mei button int3406_thermal video wmi backlight dptf_power fan int3403_thermal int340x_thermal_zone intel_pmc_core int3400_thermal acpi_thermal_rel unix
Jul 27 08:41:08 unraid-box kernel: CPU: 1 PID: 9864 Comm: kworker/1:1 Tainted: P           O       6.1.38-Unraid #2
Jul 27 08:41:08 unraid-box kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J4125-ITX, BIOS P1.70 08/13/2021
Jul 27 08:41:08 unraid-box kernel: Workqueue: events console_callback
Jul 27 08:41:08 unraid-box kernel: RIP: 0010:gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:08 unraid-box kernel: Code: 85 e4 75 03 4c 8b 27 44 89 44 24 04 e8 c9 7a e7 e0 44 8b 44 24 04 89 e9 4c 89 e2 48 89 c6 48 c7 c7 e1 58 7f a0 e8 c7 07 95 e0 <0f> 0b f7 83 58 1b 00 00 00 00 00 14 74 7b 48 89 df be 02 00 00 00
Jul 27 08:41:08 unraid-box kernel: RSP: 0018:ffffc90007217710 EFLAGS: 00010286
Jul 27 08:41:08 unraid-box kernel: RAX: 0000000000000000 RBX: ffff888103848000 RCX: 0000000000000027
Jul 27 08:41:08 unraid-box kernel: RDX: 0000000000000002 RSI: ffffffff82090ebc RDI: 00000000ffffffff
Jul 27 08:41:08 unraid-box kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000031
Jul 27 08:41:08 unraid-box kernel: R10: 0000000000045008 R11: ffffffff8295dda5 R12: ffff8881012da3e0
Jul 27 08:41:08 unraid-box kernel: R13: 000000000000002f R14: ffff888103848b18 R15: ffff888103848958
Jul 27 08:41:08 unraid-box kernel: FS:  0000000000000000(0000) GS:ffff888860080000(0000) knlGS:0000000000000000
Jul 27 08:41:08 unraid-box kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 27 08:41:08 unraid-box kernel: CR2: 000014d39b633000 CR3: 000000021a61c000 CR4: 0000000000350ee0
Jul 27 08:41:08 unraid-box kernel: Call Trace:
Jul 27 08:41:08 unraid-box kernel: <TASK>
Jul 27 08:41:08 unraid-box kernel: ? __warn+0xab/0x122
Jul 27 08:41:08 unraid-box kernel: ? report_bug+0x109/0x17e
Jul 27 08:41:08 unraid-box kernel: ? gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:08 unraid-box kernel: ? handle_bug+0x41/0x6f
Jul 27 08:41:08 unraid-box kernel: ? exc_invalid_op+0x13/0x60
Jul 27 08:41:08 unraid-box kernel: ? asm_exc_invalid_op+0x16/0x20
Jul 27 08:41:08 unraid-box kernel: ? gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:08 unraid-box kernel: intel_power_well_enable+0x49/0x57 [i915]
Jul 27 08:41:08 unraid-box kernel: __intel_display_power_get_domain+0xdb/0x129 [i915]
Jul 27 08:41:08 unraid-box kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
Jul 27 08:41:08 unraid-box kernel: ? assert_rpm_wakelock_held+0xe/0x37 [i915]
Jul 27 08:41:08 unraid-box kernel: intel_display_power_get+0x3a/0x4e [i915]
Jul 27 08:41:08 unraid-box kernel: intel_dp_aux_xfer+0xe0/0x5d3 [i915]
Jul 27 08:41:08 unraid-box kernel: ? hrtimer_start_range_ns+0x1d4/0x23e
Jul 27 08:41:08 unraid-box kernel: ? hrtimer_cancel+0x11/0x1f
Jul 27 08:41:08 unraid-box kernel: intel_dp_aux_transfer+0x175/0x258 [i915]
Jul 27 08:41:08 unraid-box kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
Jul 27 08:41:08 unraid-box kernel: ? fwtable_read32+0xa6/0xb8 [i915]
Jul 27 08:41:08 unraid-box kernel: drm_dp_dpcd_access+0x82/0x110 [drm_display_helper]
Jul 27 08:41:08 unraid-box kernel: drm_dp_dpcd_write+0x37/0x61 [drm_display_helper]
Jul 27 08:41:08 unraid-box kernel: drm_dp_dpcd_writeb+0x14/0x1a [i915]
Jul 27 08:41:08 unraid-box kernel: intel_dp_set_power+0x45/0x113 [i915]
Jul 27 08:41:08 unraid-box kernel: intel_ddi_post_disable+0x270/0x349 [i915]
Jul 27 08:41:08 unraid-box kernel: intel_encoders_post_disable+0x5d/0x6f [i915]
Jul 27 08:41:08 unraid-box kernel: intel_old_crtc_state_disables+0x38/0x87 [i915]
Jul 27 08:41:08 unraid-box kernel: intel_atomic_commit_tail+0x3a2/0xabf [i915]
Jul 27 08:41:08 unraid-box kernel: intel_atomic_commit+0x280/0x292 [i915]
Jul 27 08:41:08 unraid-box kernel: drm_atomic_commit+0xa8/0xcb [drm]
Jul 27 08:41:08 unraid-box kernel: ? __SCT__tp_func_drm_vblank_event_delivered+0x8/0x8 [drm]
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 27 08:41:08 unraid-box kernel: drm_client_modeset_commit_atomic+0x154/0x1e7 [drm]
Jul 27 08:41:08 unraid-box kernel: drm_client_modeset_dpms+0x74/0x196 [drm]
Jul 27 08:41:08 unraid-box kernel: ? bit_cursor+0x400/0x437
Jul 27 08:41:08 unraid-box kernel: drm_fb_helper_dpms.isra.0+0x2b/0x37 [drm_kms_helper]
Jul 27 08:41:08 unraid-box kernel: drm_fb_helper_blank+0x63/0x72 [drm_kms_helper]
Jul 27 08:41:08 unraid-box kernel: intel_fbdev_blank+0x13/0x32 [i915]
Jul 27 08:41:08 unraid-box kernel: fb_blank+0x58/0x91
Jul 27 08:41:08 unraid-box kernel: fbcon_blank+0x11a/0x1dd
Jul 27 08:41:08 unraid-box kernel: ? bit_cursor+0x400/0x437
Jul 27 08:41:08 unraid-box kernel: ? preempt_latency_start+0x2b/0x46
Jul 27 08:41:08 unraid-box kernel: ? _raw_spin_lock_irqsave+0x2c/0x37
Jul 27 08:41:08 unraid-box kernel: ? lock_timer_base+0x38/0x5f
Jul 27 08:41:08 unraid-box kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a
Jul 27 08:41:08 unraid-box kernel: ? try_to_del_timer_sync+0x58/0x7c
Jul 27 08:41:08 unraid-box kernel: do_blank_screen+0x137/0x1c4
Jul 27 08:41:08 unraid-box kernel: console_callback+0xd2/0xf7
Jul 27 08:41:08 unraid-box kernel: process_one_work+0x1a8/0x295
Jul 27 08:41:08 unraid-box kernel: worker_thread+0x18b/0x244
Jul 27 08:41:08 unraid-box kernel: ? rescuer_thread+0x281/0x281
Jul 27 08:41:08 unraid-box kernel: kthread+0xe4/0xef
Jul 27 08:41:08 unraid-box kernel: ? kthread_complete_and_exit+0x1b/0x1b
Jul 27 08:41:08 unraid-box kernel: ret_from_fork+0x1f/0x30
Jul 27 08:41:08 unraid-box kernel: </TASK>
Jul 27 08:41:08 unraid-box kernel: ---[ end trace 0000000000000000 ]---
Jul 27 08:41:20 unraid-box kernel: ------------[ cut here ]------------
Jul 27 08:41:20 unraid-box kernel: i915 0000:00:02.0: Unexpected DBuf power power state (0x00000000, expected 0x00000001)
Jul 27 08:41:20 unraid-box kernel: WARNING: CPU: 1 PID: 9864 at drivers/gpu/drm/i915/display/intel_display_power_well.c:950 gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:20 unraid-box kernel: Modules linked in: xt_connmark xt_mark iptable_mangle xt_comment iptable_raw xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter veth xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_nat iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_pclmul drm_kms_helper crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel processor_thermal_device_pci_legacy processor_thermal_device crypto_simd drm cryptd processor_thermal_rfim processor_thermal_mbox rapl
Jul 27 08:41:20 unraid-box kernel: mei_pxp mei_hdcp intel_rapl_msr processor_thermal_rapl intel_cstate i2c_i801 intel_gtt agpgart intel_rapl_common syscopyarea i2c_smbus sysfillrect intel_soc_dts_iosf r8169 i2c_core ahci mei_me sysimgblt realtek libahci fb_sys_fops iosf_mbi thermal mei button int3406_thermal video wmi backlight dptf_power fan int3403_thermal int340x_thermal_zone intel_pmc_core int3400_thermal acpi_thermal_rel unix
Jul 27 08:41:20 unraid-box kernel: CPU: 1 PID: 9864 Comm: kworker/1:1 Tainted: P        W  O       6.1.38-Unraid #2
Jul 27 08:41:20 unraid-box kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J4125-ITX, BIOS P1.70 08/13/2021
Jul 27 08:41:20 unraid-box kernel: Workqueue: pm pm_runtime_work
Jul 27 08:41:20 unraid-box kernel: RIP: 0010:gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:20 unraid-box kernel: Code: 85 e4 75 03 4c 8b 27 44 89 44 24 04 e8 c9 7a e7 e0 44 8b 44 24 04 89 e9 4c 89 e2 48 89 c6 48 c7 c7 e1 58 7f a0 e8 c7 07 95 e0 <0f> 0b f7 83 58 1b 00 00 00 00 00 14 74 7b 48 89 df be 02 00 00 00
Jul 27 08:41:20 unraid-box kernel: RSP: 0018:ffffc90007217cf8 EFLAGS: 00010282
Jul 27 08:41:20 unraid-box kernel: RAX: 0000000000000000 RBX: ffff888103848000 RCX: 0000000000000027
Jul 27 08:41:20 unraid-box kernel: RDX: 0000000000000002 RSI: ffffffff82090ebc RDI: 00000000ffffffff
Jul 27 08:41:20 unraid-box kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff82245ed0
Jul 27 08:41:20 unraid-box kernel: R10: 00007fffffffffff R11: ffffffff8295f3b5 R12: ffff8881012da3e0
Jul 27 08:41:20 unraid-box kernel: R13: ffff888103848000 R14: ffff888103849c20 R15: 0000000000000000
Jul 27 08:41:20 unraid-box kernel: FS:  0000000000000000(0000) GS:ffff888860080000(0000) knlGS:0000000000000000
Jul 27 08:41:20 unraid-box kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 27 08:41:20 unraid-box kernel: CR2: 000015351cdf3840 CR3: 000000000420a000 CR4: 0000000000350ee0
Jul 27 08:41:20 unraid-box kernel: Call Trace:
Jul 27 08:41:20 unraid-box kernel: <TASK>
Jul 27 08:41:20 unraid-box kernel: ? __warn+0xab/0x122
Jul 27 08:41:20 unraid-box kernel: ? report_bug+0x109/0x17e
Jul 27 08:41:20 unraid-box kernel: ? gen9_disable_dc_states+0x151/0x20d [i915]
Jul 27 08:41:20 unraid-box kernel: ? handle_bug+0x41/0x6f
Jul 27 08:41:20 unraid-box kernel: ? exc_invalid_op+0x13/0x60
Jul 27 08:41:20 unraid-box kernel: ? asm_exc_invalid_op+0x16/0x20
Jul 27 08:41:20 unraid-box kernel: ? gen9_disable_dc_states+0x151/0x20d [i915]
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 27 08:41:20 unraid-box kernel: bxt_display_core_uninit.part.0+0xf/0x66 [i915]
Jul 27 08:41:20 unraid-box kernel: intel_display_power_suspend+0x44/0x59 [i915]
Jul 27 08:41:20 unraid-box kernel: intel_runtime_suspend+0xf3/0x1e7 [i915]
Jul 27 08:41:20 unraid-box kernel: ? pci_pm_default_resume+0x23/0x23
Jul 27 08:41:20 unraid-box kernel: pci_pm_runtime_suspend+0x6a/0x155
Jul 27 08:41:20 unraid-box kernel: ? pci_pm_default_resume+0x23/0x23
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 27 08:41:20 unraid-box kernel: __rpm_callback+0xcb/0x13a
Jul 27 08:41:20 unraid-box kernel: ? pci_pm_default_resume+0x23/0x23
Jul 27 08:41:20 unraid-box kernel: rpm_callback+0x4b/0x64
Jul 27 08:41:20 unraid-box kernel: ? pci_pm_default_resume+0x23/0x23
Jul 27 08:41:20 unraid-box kernel: rpm_suspend+0x2b6/0x4a4
Jul 27 08:41:20 unraid-box kernel: ? raw_spin_rq_unlock_irq+0x5/0x10
Jul 27 08:41:20 unraid-box kernel: ? finish_task_switch.isra.0+0x140/0x218
Jul 27 08:41:20 unraid-box kernel: pm_runtime_work+0x75/0x7f
Jul 27 08:41:20 unraid-box kernel: process_one_work+0x1a8/0x295
Jul 27 08:41:20 unraid-box kernel: worker_thread+0x18b/0x244
Jul 27 08:41:20 unraid-box kernel: ? rescuer_thread+0x281/0x281
Jul 27 08:41:20 unraid-box kernel: kthread+0xe4/0xef
Jul 27 08:41:20 unraid-box kernel: ? kthread_complete_and_exit+0x1b/0x1b
Jul 27 08:41:20 unraid-box kernel: ret_from_fork+0x1f/0x30
Jul 27 08:41:20 unraid-box kernel: </TASK>
Jul 27 08:41:20 unraid-box kernel: ---[ end trace 0000000000000000 ]---
Jul 27 08:50:18 unraid-box kernel: Bluetooth: Core ver 2.22
Jul 27 08:50:18 unraid-box kernel: NET: Registered PF_BLUETOOTH protocol family
Jul 27 08:50:18 unraid-box kernel: Bluetooth: HCI device and connection manager initialized
Jul 27 08:50:18 unraid-box kernel: Bluetooth: HCI socket layer initialized
Jul 27 08:50:18 unraid-box kernel: Bluetooth: L2CAP socket layer initialized
Jul 27 08:50:18 unraid-box kernel: Bluetooth: SCO socket layer initialized

     

    Edited by Mainfrezzer
    fixed version number
    Link to comment
    JorgeB
    On 7/27/2023 at 8:09 AM, Mainfrezzer said:

    Having a look at my log in 6.12.3 lets me guess that this issue didnt get fixed after all?

    There's no fix for now, it's a kernel/driver issue, there's the workaround.

    Link to comment
    JorgeB

    Can anyone confirm if this is still an issue with Unraid v6.12.6? That is, do you still need to use "enable_dc=0" with a Rocket Lake CPU?

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.