SyberWraith

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

 Content Type 

Everything posted by SyberWraith

  1. SyberWraith
    Yes, i can't remember why i had the array on stop (was doing something) and had to reboot, made sure i set the array to not start automatically, and when that happened i noticed i had 2 cores at 100%, currently it's at 1 core, and if i do reboot, it chooses a different core on reboot.
  2. SyberWraith
    i'm experiencing this as well, since i'm running a ryzen i made sure to add the lines to the go file, and i did try a couple things suggested about finding the interrupt that has high usage, but none showed up. Also tried setting the "CPU Scaling Governor" to On demand, haven't tried performance yet, but so far nothing seems to help. it's making reboots/shutdowns difficult as it seems to hang on properly shutting down the array. i've attached my diag file in case it has something that might help titan-fs-diagnostics-20210505-1516.zip
  3. SyberWraith
    well, i don't exactly have another set of MB/CPU i can switch it with, and this only started happening with 6.9.0. I could go into the bios and disable USB, but i'm not sure that'd cure the problem, and obviously i'd have to be careful which ones i disable, might make it so i can't boot up.
  4. SyberWraith
    i'm running into a similar problem, it's just 1 core at the moment being used by kworker. This is causing problems when i have to reboot as it's preventing proper shutdown/reboots of the array. I have added /usr/local/sbin/zenstates --c6-disable to the go file since i'm running a ryzen 1600AF. Attached my diags. titan-fs-diagnostics-20210505-1516.zip