xtrap225 Posted September 23, 2019 Share Posted September 23, 2019 (edited) so ever since i added the following to my /boot/config/go file to enable hardware transcoding to plex. #Setup drivers for hardware transcoding in Plex modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri here is the lines im seeing in the syslog Sep 22 23:25:22 WORK-PC kernel: [drm] GPU HANG: ecode 7:6:0xacdfbffe, reason: hang on vecs0, action: reset Sep 22 23:25:22 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 ... Sep 23 01:14:03 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:11 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:19 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:27 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:35 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:43 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:51 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:14:59 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 Sep 23 01:15:07 WORK-PC kernel: i915 0000:00:02.0: Resetting chip for hang on vecs0 ... Sep 23 01:45:27 WORK-PC kernel: Plex Media Scan[28422]: segfault at b0 ip 000014cfbfe01097 sp 000014cfb19fe000 error 4 in libcrypto.so.1.0.0[14cfbfcf0000+204000] Sep 23 01:45:27 WORK-PC kernel: Code: 8b 4f 1c 31 d2 4c 89 e0 48 f7 f1 49 8b 07 48 63 ca 4c 8b 2c c8 4d 85 ed 74 37 49 8b 6f 08 48 8d 1c c8 90 49 ff 87 a0 00 00 00 <4d> 39 65 10 75 11 49 ff 47 68 49 8b 7d 00 4c 89 f6 ff d5 85 c0 74 when googling the error i found some people said that if you add some parameters to the kernel you can fix the issue. https://forum.manjaro.org/t/i915-gpu-hang-solved/37200/13 Solved! Adding these parameters to the kernel is fixed: i915.modeset=1 i915.enable_rc6=1 i915.enable_fbc=1 i915.enable_guc_loading=1 i915.enable_guc_submission=1 i915.enable_huc=1 i915.enable_psr=1 i915.disable_power_well=0 i915.semaphores=1 It works in version 4.14 and 4.15 on the other hand hoopster said in this thread that the Intel i5-9500 is not supported in kernel 4.19, but mine is an older cpu. Linux WORK-PC 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz GenuineIntel GNU/Linux Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz here is some more info if anyone thinks its relevant root@WORK-PC:~# systool -m i915 -av Module = "i915" Attributes: coresize = "1261568" initsize = "0" initstate = "live" refcnt = "0" taint = "" uevent = <store method only> Parameters: alpha_support = "N" disable_display = "N" disable_power_well = "1" dmc_firmware_path = "(null)" edp_vswing = "0" enable_dc = "-1" enable_dp_mst = "Y" enable_dpcd_backlight= "N" enable_fbc = "0" enable_guc = "0" enable_gvt = "N" enable_hangcheck = "Y" enable_ips = "1" enable_ppgtt = "1" enable_psr = "-1" error_capture = "Y" fastboot = "N" force_reset_modeset_test= "N" guc_firmware_path = "(null)" guc_log_level = "0" huc_firmware_path = "(null)" invert_brightness = "0" load_detect_test = "N" lvds_channel_mode = "0" mmio_debug = "0" modeset = "-1" nuclear_pageflip = "N" panel_use_ssc = "-1" prefault_disable = "N" reset = "2" vbt_firmware = "(null)" vbt_sdvo_panel_type = "-1" verbose_state_checks= "Y" Sections: .altinstr_aux = "0xffffffffa07a5b83" .altinstr_replacement= "0xffffffffa07a5638" .altinstructions = "0xffffffffa07db727" .bss = "0xffffffffa080ddc0" .data..read_mostly = "0xffffffffa080da40" .data.once = "0xffffffffa080d9d0" .data = "0xffffffffa0809020" .exit.text = "0xffffffffa07a5bdd" .fixup = "0xffffffffa07a5bf4" .gnu.linkonce.this_module= "0xffffffffa080dac0" .init.text = "0xffffffffa082f000" .note.Linux = "0xffffffffa07a6024" .note.gnu.build-id = "0xffffffffa07a6000" .orc_unwind = "0xffffffffa07edebc" .orc_unwind_ip = "0xffffffffa07dd1dc" .parainstructions = "0xffffffffa07dc260" .rodata = "0xffffffffa07a6080" .rodata.str1.1 = "0xffffffffa07bc59c" .smp_locks = "0xffffffffa07dbc98" .strtab = "0xffffffffa084c758" .symtab = "0xffffffffa0830000" .text..refcount = "0xffffffffa07a57d1" .text = "0xffffffffa06fa000" .text.unlikely = "0xffffffffa07a5c71" __bug_table = "0xffffffffa080ad90" __ex_table = "0xffffffffa080720c" __jump_table = "0xffffffffa0809000" __ksymtab_gpl = "0xffffffffa07a6040" __ksymtab_strings = "0xffffffffa0807fd8" __param = "0xffffffffa0807ab0" work-pc-diagnostics-20190923-0557.zip Edited September 23, 2019 by xtrap225 Quote Link to comment
bulzipke Posted October 9, 2019 Share Posted October 9, 2019 I have the same problem. I added modprobe i915 and caused a kernel panic like below. Quote Oct 8 18:00:02 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:02 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678a000 [fault reason 23] Unknown Oct 8 18:00:02 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:02 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678c000 [fault reason 23] Unknown Oct 8 18:00:02 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:02 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678d000 [fault reason 23] Unknown Oct 8 18:00:02 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:07 myNAS kernel: [drm] GPU HANG: ecode 8:2:0x4f0e74dd, reason: hang on vcs0, action: reset Oct 8 18:00:07 myNAS kernel: i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 Oct 8 18:00:07 myNAS kernel: dmar_fault: 365 callbacks suppressed Oct 8 18:00:07 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:07 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6851000 [fault reason 23] Unknown Oct 8 18:00:07 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:07 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6856000 [fault reason 23] Unknown Oct 8 18:00:07 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6857000 [fault reason 23] Unknown Oct 8 18:00:07 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:07 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6858000 [fault reason 23] Unknown Oct 8 18:00:07 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6859000 [fault reason 23] Unknown Oct 8 18:00:13 myNAS kernel: i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 Oct 8 18:00:13 myNAS kernel: dmar_fault: 349 callbacks suppressed Oct 8 18:00:13 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 8 18:00:13 myNAS kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr 678a000 [fault reason 05] PTE Write access is not set Oct 8 18:00:21 myNAS kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Oct 8 18:00:21 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 8 18:00:21 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678a000 [fault reason 23] Unknown Oct 8 18:00:21 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:21 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678e000 [fault reason 23] Unknown Oct 8 18:00:21 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:21 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6790000 [fault reason 23] Unknown Oct 8 18:00:21 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:27 myNAS kernel: i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 Oct 8 18:00:27 myNAS kernel: dmar_fault: 333 callbacks suppressed Oct 8 18:00:27 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 8 18:00:27 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 673f000 [fault reason 23] Unknown Oct 8 18:00:27 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 8 18:00:27 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6000 [fault reason 23] Unknown Oct 8 18:00:27 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:27 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 207000 [fault reason 23] Unknown Oct 8 18:00:27 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 8 18:00:29 myNAS kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Oct 8 18:00:37 myNAS kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Oct 8 18:00:37 myNAS kernel: dmar_fault: 901 callbacks suppressed Oct 8 18:00:37 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:37 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678a000 [fault reason 23] Unknown Oct 8 18:00:37 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:37 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678e000 [fault reason 23] Unknown Oct 8 18:00:37 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 678f000 [fault reason 23] Unknown Oct 8 18:00:37 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6790000 [fault reason 23] Unknown Oct 8 18:00:37 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 6791000 [fault reason 23] Unknown Oct 8 18:00:37 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 8 18:00:43 myNAS kernel: i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 Oct 8 18:00:45 myNAS kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Oct 8 18:00:45 myNAS kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0 Oct 8 18:00:46 myNAS kernel: i915 0000:00:02.0: Failed to reset chip Oct 8 18:01:23 myNAS kernel: ------------[ cut here ]------------ Oct 8 18:01:23 myNAS kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Oct 8 18:01:23 myNAS kernel: WARNING: CPU: 1 PID: 4088 at net/sched/sch_generic.c:461 dev_watchdog+0x15f/0x1b7 Oct 8 18:01:23 myNAS kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod i915 i2c_algo_bit iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm btusb btrtl btbcm btintel crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mxm_wmi bluetooth r8169 cryptd intel_cstate intel_uncore i2c_i801 ahci libahci intel_rapl_perf i2c_core video realtek ecdh_generic wmi backlight fan thermal button acpi_pad pcc_cpufreq Oct 8 18:01:23 myNAS kernel: CPU: 1 PID: 4088 Comm: dockerd Tainted: G W 4.19.56-Unraid #1 Oct 8 18:01:23 myNAS kernel: Hardware name: MICRO-STAR INTERNATIONAL CO., LTD MS-B09611/MS-B0961, BIOS EB096IMS V1.5 05/23/2016 Oct 8 18:01:23 myNAS kernel: RIP: 0010:dev_watchdog+0x15f/0x1b7 Oct 8 18:01:23 myNAS kernel: Code: 0b 06 97 00 00 75 36 4c 89 ef c6 05 ff 05 97 00 01 e8 8f b3 fd ff 89 e9 4c 89 ee 48 c7 c7 3e df d8 81 48 89 c2 e8 48 cd b1 ff <0f> 0b eb 0f ff c5 48 81 c2 40 01 00 00 39 cd 75 98 eb 13 48 8b 83 Oct 8 18:01:23 myNAS kernel: RSP: 0000:ffff88840f303ea0 EFLAGS: 00010286 Oct 8 18:01:23 myNAS kernel: RAX: 0000000000000000 RBX: ffff888409728438 RCX: 0000000000000007 Oct 8 18:01:23 myNAS kernel: RDX: 000000000000041b RSI: 0000000000000002 RDI: ffff88840f3164f0 Oct 8 18:01:23 myNAS kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000020300 Oct 8 18:01:23 myNAS kernel: R10: 000000000000041a R11: 00000000000130a0 R12: ffff88840972841c Oct 8 18:01:23 myNAS kernel: R13: ffff888409728000 R14: ffff8883eca55c80 R15: 0000000000000001 Oct 8 18:01:23 myNAS kernel: FS: 00000000032f7880(0000) GS:ffff88840f300000(0000) knlGS:0000000000000000 Oct 8 18:01:23 myNAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 8 18:01:23 myNAS kernel: CR2: 0000150267b95000 CR3: 00000003d7482005 CR4: 00000000000606e0 Oct 8 18:01:23 myNAS kernel: Call Trace: Oct 8 18:01:23 myNAS kernel: <IRQ> Oct 8 18:01:23 myNAS kernel: call_timer_fn+0x18/0x7b Oct 8 18:01:23 myNAS kernel: ? qdisc_reset+0xc0/0xc0 Oct 8 18:01:23 myNAS kernel: expire_timers+0x7f/0x8e Oct 8 18:01:23 myNAS kernel: run_timer_softirq+0x72/0x120 Oct 8 18:01:23 myNAS kernel: ? enqueue_hrtimer.isra.3+0x23/0x27 Oct 8 18:01:23 myNAS kernel: ? __hrtimer_run_queues+0xd7/0x105 Oct 8 18:01:23 myNAS kernel: ? recalibrate_cpu_khz+0x1/0x1 Oct 8 18:01:23 myNAS kernel: ? ktime_get+0x3a/0x8d Oct 8 18:01:23 myNAS kernel: __do_softirq+0xce/0x1e2 Oct 8 18:01:23 myNAS kernel: irq_exit+0x5e/0x9d Oct 8 18:01:23 myNAS kernel: smp_apic_timer_interrupt+0x7e/0x91 Oct 8 18:01:23 myNAS kernel: apic_timer_interrupt+0xf/0x20 Oct 8 18:01:23 myNAS kernel: </IRQ> Oct 8 18:01:23 myNAS kernel: RIP: 0033:0x4b6570 Oct 8 18:01:23 myNAS kernel: Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 Oct 8 18:01:23 myNAS kernel: RSP: 002b:000000c42135cca0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13 Oct 8 18:01:23 myNAS kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000004b6570 Oct 8 18:01:23 myNAS kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000005a Oct 8 18:01:23 myNAS kernel: RBP: 000000c42135cce8 R08: 0000000000000000 R09: 0000000000000000 Oct 8 18:01:23 myNAS kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 Oct 8 18:01:23 myNAS kernel: R13: 00000000000000f1 R14: 0000000000000011 R15: 0000000000000001 Oct 8 18:01:23 myNAS kernel: ---[ end trace 8fe1bb8cead5a396 ]--- Oct 8 18:01:46 myNAS kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Oct 8 18:01:46 myNAS kernel: rcu: 0-...0: (1 ticks this GP) idle=69a/1/0x4000000000000002 softirq=57541631/57541631 fqs=14977 Oct 8 18:01:46 myNAS kernel: rcu: (detected by 1, t=60002 jiffies, g=90598521, q=4813690) Oct 8 18:01:46 myNAS kernel: Sending NMI from CPU 1 to CPUs 0: Oct 8 18:01:46 myNAS kernel: NMI backtrace for cpu 0 Oct 8 18:01:46 myNAS kernel: CPU: 0 PID: 16303 Comm: sh Tainted: G W 4.19.56-Unraid #1 Oct 8 18:01:46 myNAS kernel: Hardware name: MICRO-STAR INTERNATIONAL CO., LTD MS-B09611/MS-B0961, BIOS EB096IMS V1.5 05/23/2016 Oct 8 18:01:46 myNAS kernel: RIP: 0010:qi_submit_sync+0x154/0x2db Oct 8 18:01:46 myNAS kernel: Code: 02 0f 84 43 01 00 00 4d 8b 8f b0 00 00 00 49 8b 41 10 42 83 3c 10 03 75 0b 41 bc f5 ff ff ff e9 29 01 00 00 49 8b 07 8b 78 34 <40> f6 c7 10 74 68 49 8b 07 8b 80 80 00 00 00 c1 f8 04 41 39 c3 75 Oct 8 18:01:46 myNAS kernel: RSP: 0018:ffff88840f203dd0 EFLAGS: 00000093 Oct 8 18:01:46 myNAS kernel: RAX: ffffc90000019000 RBX: 0000000000000100 RCX: 0000000200000025 Oct 8 18:01:46 myNAS kernel: RDX: 0000000000000001 RSI: ffffc90000019000 RDI: 0000000000000000 Oct 8 18:01:46 myNAS kernel: RBP: ffff88840f203e28 R08: 0000000000000020 R09: ffff88840ec0ebc0 Oct 8 18:01:46 myNAS kernel: R10: 0000000000000334 R11: 00000000000000cc R12: 0000000000000cd0 Oct 8 18:01:46 myNAS kernel: R13: ffff88840ec0ebc0 R14: 00000000000000cc R15: ffff88840ec19400 Oct 8 18:01:46 myNAS kernel: FS: 0000000000000000(0000) GS:ffff88840f200000(0000) knlGS:0000000000000000 Oct 8 18:01:46 myNAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 8 18:01:46 myNAS kernel: CR2: 00007fff69f7db69 CR3: 00000001712fe006 CR4: 00000000000606f0 Oct 8 18:01:46 myNAS kernel: Call Trace: Oct 8 18:01:46 myNAS kernel: <IRQ> Oct 8 18:01:46 myNAS kernel: qi_flush_iotlb+0x66/0x80 Oct 8 18:01:46 myNAS kernel: iommu_flush_iova+0x5a/0x9e Oct 8 18:01:46 myNAS kernel: iova_domain_flush+0x18/0x22 Oct 8 18:01:46 myNAS kernel: fq_flush_timeout+0x2e/0x90 Oct 8 18:01:46 myNAS kernel: call_timer_fn+0x18/0x7b Oct 8 18:01:46 myNAS kernel: ? fq_ring_free+0x96/0x96 Oct 8 18:01:46 myNAS kernel: expire_timers+0x7f/0x8e Oct 8 18:01:46 myNAS kernel: run_timer_softirq+0x72/0x120 Oct 8 18:01:46 myNAS kernel: ? enqueue_hrtimer.isra.3+0x23/0x27 Oct 8 18:01:46 myNAS kernel: ? __hrtimer_run_queues+0xd7/0x105 Oct 8 18:01:46 myNAS kernel: ? recalibrate_cpu_khz+0x1/0x1 Oct 8 18:01:46 myNAS kernel: ? ktime_get+0x3a/0x8d Oct 8 18:01:46 myNAS kernel: __do_softirq+0xce/0x1e2 Oct 8 18:01:46 myNAS kernel: irq_exit+0x5e/0x9d Oct 8 18:01:46 myNAS kernel: smp_apic_timer_interrupt+0x7e/0x91 Oct 8 18:01:46 myNAS kernel: apic_timer_interrupt+0xf/0x20 Oct 8 18:01:46 myNAS kernel: </IRQ> Oct 8 18:01:46 myNAS kernel: RIP: 0010:_raw_spin_unlock_irqrestore+0xc/0x12 Oct 8 18:01:46 myNAS kernel: Code: 5b c3 8b 07 85 c0 74 03 31 c0 c3 ba 01 00 00 00 f0 0f b1 17 85 c0 75 f0 b8 01 00 00 00 c3 c6 07 00 0f 1f 40 00 48 89 f7 57 9d <0f> 1f 44 00 00 c3 8b 07 a9 ff 01 00 00 75 1d ba 00 02 00 00 f0 0f Oct 8 18:01:46 myNAS kernel: RSP: 0018:ffffc90003fdfdb8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Oct 8 18:01:46 myNAS kernel: RAX: 0000000000000000 RBX: ffff8881752332c0 RCX: ffff8881752332c8 Oct 8 18:01:46 myNAS kernel: RDX: ffff8881752332c8 RSI: 0000000000000246 RDI: 0000000000000246 Oct 8 18:01:46 myNAS kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffc90003fdfdc8 Oct 8 18:01:46 myNAS kernel: R10: 00000000000010da R11: ffff88840f320b80 R12: 0000000000000001 Oct 8 18:01:46 myNAS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000246 Oct 8 18:01:46 myNAS kernel: __wake_up_common_lock+0x86/0xcb Oct 8 18:01:46 myNAS kernel: sock_def_wakeup+0x2d/0x2e Oct 8 18:01:46 myNAS kernel: unix_release_sock+0x16a/0x252 Oct 8 18:01:46 myNAS kernel: unix_release+0x14/0x20 Oct 8 18:01:46 myNAS kernel: __sock_release+0x38/0xa0 Oct 8 18:01:46 myNAS kernel: sock_close+0xc/0xf Oct 8 18:01:46 myNAS kernel: __fput+0xe5/0x183 Oct 8 18:01:46 myNAS kernel: task_work_run+0x77/0x8b Oct 8 18:01:46 myNAS kernel: exit_to_usermode_loop+0x46/0x9b Oct 8 18:01:46 myNAS kernel: do_syscall_64+0xdf/0xf2 Oct 8 18:01:46 myNAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 8 18:01:46 myNAS kernel: RIP: 0033:0x15477fe52c30 Oct 8 18:01:46 myNAS kernel: Code: Bad RIP value. Oct 8 18:01:46 myNAS kernel: RSP: 002b:00007fff69f7d970 EFLAGS: 00000200 ORIG_RAX: 000000000000003b Oct 8 18:01:46 myNAS kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Oct 8 18:01:46 myNAS kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Oct 8 18:01:46 myNAS kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Oct 8 18:01:46 myNAS kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Oct 8 18:01:46 myNAS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Quote Oct 9 13:45:26 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 9 13:45:26 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 3cda000 [fault reason 23] Unknown Oct 9 13:45:26 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:26 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 3cdf000 [fault reason 23] Unknown Oct 9 13:45:26 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:26 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 3ce2000 [fault reason 23] Unknown Oct 9 13:45:26 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:41 myNAS kernel: [drm] GPU HANG: ecode 8:0:0xe757fefe, reason: no progress on rcs0, action: reset Oct 9 13:45:41 myNAS kernel: i915 0000:00:02.0: Resetting rcs0 for no progress on rcs0 Oct 9 13:45:41 myNAS kernel: dmar_fault: 320 callbacks suppressed Oct 9 13:45:41 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:41 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7df000 [fault reason 23] Unknown Oct 9 13:45:41 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:41 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e3000 [fault reason 23] Unknown Oct 9 13:45:41 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e4000 [fault reason 23] Unknown Oct 9 13:45:41 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:41 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e5000 [fault reason 23] Unknown Oct 9 13:45:41 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e6000 [fault reason 23] Unknown Oct 9 13:45:49 myNAS kernel: i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 Oct 9 13:45:49 myNAS kernel: dmar_fault: 355 callbacks suppressed Oct 9 13:45:49 myNAS kernel: DMAR: DRHD: handling fault status reg 3 Oct 9 13:45:49 myNAS kernel: DMAR: [DMA Read] Request device [00:02.0] fault addr d7df000 [fault reason 05] PTE Write access is not set Oct 9 13:45:57 myNAS kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Oct 9 13:45:57 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:57 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7df000 [fault reason 23] Unknown Oct 9 13:45:57 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:57 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e3000 [fault reason 23] Unknown Oct 9 13:45:57 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e4000 [fault reason 23] Unknown Oct 9 13:45:57 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e5000 [fault reason 23] Unknown Oct 9 13:45:57 myNAS kernel: DMAR: DRHD: handling fault status reg 2 Oct 9 13:45:57 myNAS kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr d7e6000 [fault reason 23] Unknown Oct 9 13:50:24 myNAS kernel: docker0: port 8(veth56c5b3f) entered disabled state Oct 9 13:50:24 myNAS kernel: device veth56c5b3f entered promiscuous mode Oct 9 13:50:24 myNAS kernel: IPv6: ADDRCONF(NETDEV_UP): veth56c5b3f: link is not ready Oct 9 13:50:24 myNAS kernel: docker0: port 8(veth56c5b3f) entered blocking state Oct 9 13:50:24 myNAS kernel: docker0: port 8(veth56c5b3f) entered forwarding state Oct 9 13:50:24 myNAS kernel: docker0: port 8(veth56c5b3f) entered disabled state Oct 9 13:50:32 myNAS kernel: eth0: renamed from veth8a78954 Oct 9 13:50:32 myNAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth56c5b3f: link becomes ready Oct 9 13:50:32 myNAS kernel: docker0: port 8(veth56c5b3f) entered blocking state Oct 9 13:50:32 myNAS kernel: docker0: port 8(veth56c5b3f) entered forwarding state Quote Link to comment
Scorpionhl Posted December 28, 2019 Share Posted December 28, 2019 Has anyone found a solution to this issue, or did those kernel parameters fix your problem? I've only been running unraid for 2 months now, on the 6.7 RC code (and now 6.8), and have come across this twice. In each case, the server itself had been up for almost two weeks with plex running as a docker using the igpu the whole time (baring a restart of the docker for the occasional update). As an additional symptom of this issue, the whole Unraid box freezes (can't login to directly attached console or anything) and for some reason (that I cannot explain) it wipes out my whole wired network (I even replaced the attached switch when this happened the last time, rebooted router, wireless ran fine), but unless I unplugged the unraid box I got no network connectivity on other machines. Machine specs: i7-6700 Asus Z170-A on latest firmware 3 PCIe cards (additional network, graphics, LSI -Sas to Sata) From the Syslog (remote): 2019-12-2716:59:39 Error kern kernel [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout 2019-12-2716:59:39 Error kern kernel i915 0000:00:02.0: Failed to reset chip 2019-12-2716:59:38 Error kern kernel [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout 2019-12-2716:59:38 Error kern kernel [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout 2019-12-2716:59:38 Error kern kernel [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout 2019-12-2716:59:38 Notice kern kernel i915 0000:00:02.0: Resetting chip for hang on rcs0 2019-12-2716:59:38 Error kern kernel [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout 2019-12-2716:59:38 Notice kern kernel i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 2019-12-2716:59:38 Information kern kernel [drm] GPU HANG: ecode 9:0:0x96d1ccef, in Plex Transcoder [14234], reason: hang on rcs0, action: reset Quote Link to comment
Recommended Posts
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.