abw

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About abw

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Alright, this did nothing, been running that for two days now.. kernel /bzimage append pcie_aspm=off initrd=/bzroot Any other suggestions?
  2. Thanks I will try and play around with this. thanks
  3. Yes, it's set at non OC value, and not enabled XMP/DOCP. Having 16BG of this kit running stock: https://www.gskill.com/product/165/170/1535961634/F4-3200C14D-16GFX-Overview
  4. Latest Bios, c-states disabled, Ryzen 3600, "Power Supply Idle Control" set to "typical current idle", XMP (DOCP) disabled.
  5. I run Shinobi Docker, and that might put some strain on the server, but still the log states this as it dies... Also added a full Diagnostics down below. Feb 2 22:24:53 Vidrock kernel: ------------[ cut here ]------------ Feb 2 22:24:53 Vidrock kernel: WARNING: CPU: 11 PID: 0 at kernel/rcu/tree.c:2684 rcu_core+0x48/0x19a Feb 2 22:24:53 Vidrock kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs md_mod n
  6. I also have the latest Bios... Seems Unraid should not let dockers spend so much resources is cripples the server...
  7. I have Shinobi Video running in docker, However 16GB of ram should be sufficient for 4 streams. But maybe some inner workings in Shinobi is to blame.
  8. Ok I've now disabled D.O.C.P. and C-states and set "Power Supply Idle Control" to "typical current idle". Still it crashes every few days. Anything more I can do? See attached diagnostics, and a persistent syslog from before the crash aswell. vidrock-diagnostics-20210128-0831.zip persistant_syslog.txt
  9. Thanks @ChatNoir, I will read up and try to see if changing any of the settings mentioned fixes my issue.
  10. Please see attached diag and persistent Syslog from a few days back. Greetings. persistant_syslog_from_USB vidrock-diagnostics-20210119-2204.zip
  11. Here are my diagnostics: vidrock-diagnostics-20210117-1225.zip
  12. I experienced a crash tonight again... Rebooted the server at 10:22. Here is the log: I will try to give a diagnostic also: Jan 17 00:24:09 Vidrock rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="16171" x-info="https://www.rsyslog.com"] start Jan 17 00:28:33 Vidrock ool www[17388]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Jan 17 00:28:35 Vidrock rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="17625" x-info="https://www.rsyslog.com"] start Jan 17 00:29:04 Vidrock emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/pl
  13. Hi! I have also today turned on syslog and "Mirror syslog to flash", so will see in a short week, but I have kept crashing once every 2-6 days for all the 3 releases I've tried: 6.9 b35, rc1 and rc2. I will post logs here in a few days, to help shed some light on this. Thanks!