@Jonathan-458 Thanks for the update - I had a very similar experience with QNAP… just passing the blame to Plex.
If you guys can update once @ChuckPa has had a look at the diagnostic data, that would be much appreciated!
Thanks
@Jonathan-458 Thanks for the update - I had a very similar experience with QNAP… just passing the blame to Plex.
If you guys can update once @ChuckPa has had a look at the diagnostic data, that would be much appreciated!
Thanks
We went through the diagnostic data (kernel panic logs)
Evidence of kernel bug
2565 [2278285.059722] Call Trace:
2566 [2278285.062348] i915_gem_reset+0x36/0xb0
2567 [2278285.066175] i915_reset+0x103/0x1c0
2568 [2278285.069833] i915_reset_device+0x1eb/0x200
2569 [2278285.074096] ? gen8_gt_irq_ack+0x160/0x160
2570 [2278285.078381] ? execute_in_process_context+0x60/0x60
2571 [2278285.083434] i915_handle_error+0x257/0x3d0
2572 [2278285.087706] ? scnprintf+0x3a/0x70
2573 [2278285.091275] hangcheck_declare_hang+0xc6/0xe0
2574 [2278285.095798] ? fwtable_read32+0x71/0x130
2575 [2278285.099901] i915_hangcheck_elapsed+0x280/0x300
2576 [2278285.104594] process_one_work+0x127/0x2a0
2577 [2278285.108779] worker_thread+0x5d/0x3d0
2578 [2278285.112607] ? max_active_store+0x50/0x50
2579 [2278285.116778] kthread+0x10a/0x140
2580 [2278285.120174] ? __kthread_parkme+0x70/0x70
2581 [2278285.124353] ret_from_fork+0x35/0x40
2582 [2278285.128092] Code: 89 ed eb 89 45 31 c9 eb 95 66 90 48 85 f6 41 55 41 54 55 48 89 fd 53 48 89 f3 0f 84 e3 00 00 00 4 8 8b bf a0 02 00 00 48 83 e7 fc <48> 8b 47 70 48 39 46 70 74 29 48 85 ff 74 0b f0 ff 0f 0f 88 45
2583 [2278285.147091] RIP: reset_common_ring+0x20/0x140 RSP: ffffc9000aa97b60
Pfff they are really fighting me on this, i asked them to share exact data that supports their claim.
@DonCaliOni,
When you generate diagnostics via QNAP Helpdesk a zip file is downloaded to your computer, open it and navigate to [filename]\sys\fs\pstore and there should be a file named “console-ramoops-0” can you please check if you find similarities.
Yep, I have got something very similar:
[1047204.929936] Call Trace:
[1047204.932574] i915_gem_reset+0x36/0xb0
[1047204.936434] i915_reset+0x103/0x1c0
[1047204.940108] i915_reset_device+0x1eb/0x200
[1047204.944392] ? gen8_gt_irq_ack+0x160/0x160
[1047204.948676] ? execute_in_process_context+0x60/0x60
[1047204.953738] i915_handle_error+0x257/0x3d0
[1047204.958022] ? scnprintf+0x3a/0x70
[1047204.961609] hangcheck_declare_hang+0xc6/0xe0
[1047204.966146] ? fwtable_read32+0x71/0x130
[1047204.970250] i915_hangcheck_elapsed+0x280/0x300
[1047204.974963] process_one_work+0x127/0x2a0
[1047204.979161] worker_thread+0x5d/0x3d0
[1047204.983012] ? __schedule+0x1e8/0x5f0
[1047204.986863] ? max_active_store+0x50/0x50
[1047204.991056] kthread+0x10a/0x140
[1047204.994470] ? __kthread_parkme+0x70/0x70
[1047204.998680] ret_from_fork+0x35/0x40
[1047205.002447] Code: 89 ed eb 89 45 31 c9 eb 95 66 90 48 85 f6 41 55 41 54 55 48 89 fd 53 48 89 f3 0f 84 e3 00 00 00 48 8b bf a0 02 00 00 48 83 e7 fc <48> 8b 47 70 48 39 46 70 74 29 48 85 ff 74 0b f0 ff 0f 0f 88 95
[1047205.021515] RIP: reset_common_ring+0x20/0x140 RSP: ffffc900019a3b60
For me it ultimately turned out to be a memory issue. I RMA’d my 8GB to Crucial and they sent over a new pair. It has not crashed or rebooted since replacing the memory. Memtest86 did not report any faults with it, but sent it in anyway.
@UncleBabyBilly I actually got a new unit TS-453D but it still crashed once. However, it’s been fine for a month or two.
I reckon a Plex update must have solved the issue, which coincided with you changing the RAM, as I tried switching to original QNAP RAM, and a whole new unit, with both cases still resulting in a crash.
Small update, i updated to 4.5.4.1723 build 20210708 and experienced no unexpected shutdowns with the Crucial Ram for now.
Since QNAP only want’s to change the unit if the issue occurs with QNAP RAM, i’ve switched back to QNAP/ADATA RAM and back to the waiting game.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.