3 ms·

Why do you want to upgrade the 1700X? What does the 2000 line bring other than a 15% (being very optimistic) performance gain?

shmerl 9y ago
Personally, because my CPU has a hardware bug[1], which is now worked around by disabling package C6 state, and I already went through RMA for the segfault bug, so I'd rather now get a newer CPU to begin with. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=196683 https://bugzilla.kernel.org/show_bug.cgi?id=196683
- IronBacon 9y ago
  I think I've read locks/hangs' reports even with newer APUs, and at this moment I'm not sure if disabling C6 state on package (or was it core?) is an effective workaround. Or the suggestion to slightly increase voltage or a light overclock. I wanted to upgrade to Ryzen but I don't want to spend time to troubleshoot the HW. Seems like it's only triggered on a BSD/Linux system, don't know if they were joking when they said that Windos is never that idle...
  - shmerl 9y ago
    > I think I've read locks/hangs' reports even with newer APUs, and at this moment I'm not sure if disabling C6 state on package (or was it core?) is an effective workaround. For me it is. It's triggered by the firmware setting: Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control = "Common current idle" (instead of auto) That disables package C6 state for me (checked with zenstates.py), and freezes and random reboots disappear after that: C6 State - Package - Disabled C6 State - Core - Enabled On auto setting for the above, I get: C6 State - Package - Enabled C6 State - Core - Enabled And it highly annoyingly randomly freezes and reboots in such case. Another workaround is in the linked thread, to compile the kernel with special rcu options, I tried that, and it works, but it's not really a good method. > don't know if they were joking when they said that Windows is never that idle... I don't think they are joking.
    - IronBacon 9y ago
      I've read of people that experienced hangs even with the RCU workaround. About the C6 state is good to know, but the lack of some kind of official confirmation from AMD is kinda disturbing as it looks like the change to the BIOS came from them. I'm really torn... Edit: disturbing is not the right word, disappointing is better
      - shmerl 9y ago
        Yeah, lack of communication on these bugs from AMD is really annoying, especially since there is no way to know whether they are fixed in newer CPUs already or not.

shmerl 9y ago

Personally, because my CPU has a hardware bug[1], which is now worked around by disabling package C6 state, and I already went through RMA for the segfault bug, so I'd rather now get a newer CPU to begin with. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=196683 https://bugzilla.kernel.org/show_bug.cgi?id=196683

IronBacon 9y ago
I think I've read locks/hangs' reports even with newer APUs, and at this moment I'm not sure if disabling C6 state on package (or was it core?) is an effective workaround. Or the suggestion to slightly increase voltage or a light overclock. I wanted to upgrade to Ryzen but I don't want to spend time to troubleshoot the HW. Seems like it's only triggered on a BSD/Linux system, don't know if they were joking when they said that Windos is never that idle...
- shmerl 9y ago
  > I think I've read locks/hangs' reports even with newer APUs, and at this moment I'm not sure if disabling C6 state on package (or was it core?) is an effective workaround. For me it is. It's triggered by the firmware setting: Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control = "Common current idle" (instead of auto) That disables package C6 state for me (checked with zenstates.py), and freezes and random reboots disappear after that: C6 State - Package - Disabled C6 State - Core - Enabled On auto setting for the above, I get: C6 State - Package - Enabled C6 State - Core - Enabled And it highly annoyingly randomly freezes and reboots in such case. Another workaround is in the linked thread, to compile the kernel with special rcu options, I tried that, and it works, but it's not really a good method. > don't know if they were joking when they said that Windows is never that idle... I don't think they are joking.
  - IronBacon 9y ago
    I've read of people that experienced hangs even with the RCU workaround. About the C6 state is good to know, but the lack of some kind of official confirmation from AMD is kinda disturbing as it looks like the change to the BIOS came from them. I'm really torn... Edit: disturbing is not the right word, disappointing is better
    - shmerl 9y ago
      Yeah, lack of communication on these bugs from AMD is really annoying, especially since there is no way to know whether they are fixed in newer CPUs already or not.