Originally posted by angrypie
View Post
Announcement
Collapse
No announcement yet.
Some FreeBSD Users Are Still Running Into Random Lock-Ups With Ryzen
Collapse
X
-
Originally posted by JPFSanders View Post
Please, can you check how you did that and let me know please?
I have the idling problem, what I do to prevent the computer from freezing is to run a session of an emulator on the background to keep the computer busy, that way it never crashes. (I'm using Kernel 4.14.14 ATM)
Comment
-
Originally posted by angrypie View Post
No, it's not.
Don't get your feelings hurt, son, it's just a piece of sand.
It's good that using the rcu_nocb actually fixed the idle crash on mine as disabling C6 is a noop (Living in Mexico, i'm like less than 5 KWH from DAC tariff (electricity_bill *= 4).
Comment
-
@slacka:
the segmentation fault issue [0], which was talked about here last august and which has been admitted by amd [1] seemed to only affected the first ryzens cpus. BUT this issue here is a different one! See [2] and for the ubuntu bug report [3]. I don't know of any official response to this issue. Even a threadripper cpu seemed to be affected (last report in [3]).
I haven't found any info about epyc but epyc is also another stepping (B2) than threadripper and normal ryzen (B1).
I am interested in buying a ryzen cpu but this issue is holding me back. Hopefully this issue will be fixed in the next ryzen cpus, which are about to be released in next months.
[0] https://bugzilla.kernel.org/show_bug.cgi?id=196481
[1] https://www.phoronix.com/scan.php?pa...-Segv-Response
[2] https://bugzilla.kernel.org/show_bug.cgi?id=196683
[3] https://bugs.launchpad.net/linux/+bug/1690085
Comment
-
@slacka:
the segmentation fault issue [0], which was talked about here last august and which has been admitted by amd [1] seemed to only affected the first ryzens cpus. BUT this issue here however is a different one! See [2] and for the ubuntu bug report [3]. I don't know of any official response to this issue. Even a threadripper cpu seemed to be affected (last report in [3]). I haven't found any info about epyc but epyc is also another stepping (B2) than Threadripper and normal ryzen (B1).
I am interested in buying a ryzen cpu but this issue is holding me back. Hopefully this issue will be fixed in the next ryzen cpus, which are about to be released in next months.
[0] https://bugzilla.kernel.org/show_bug.cgi?id=196481
[1] https://www.phoronix.com/scan.php?pa...-Segv-Response
[2] https://bugzilla.kernel.org/show_bug.cgi?id=196683
[3] https://bugs.launchpad.net/linux/+bug/1690085
Comment
-
Forcing off the C6 states (https://github.com/r4m0n/ZenStates-Linux) with a script in /etc/rc.local has changed my setup from having an average uptime of 1 - 1.5 days into 50+ days (generally I've rebooted for other reasons so haven't gone beyond that number). Every other attempted fix (RCU, randomizing VA space, etc) had nearly zero effect.
- Likes 1
Comment
-
Originally posted by RavFX View Post
From what I know, Only CPU returned by RMA (Binned/checked by AMD), don't have the segfault bug for sure. [...]
I'm not sure if well-binned Ryzens (i.e. EPYC and Threadripper) are any better than the run-of-the-mill dies, since the efficiency curve is a characteristic of the 14LPP node they use. At most you'd get +100 or so MHz over the best binned 1800Xs (that mostly do 4.1), hopefully with less insane voltages.
Comment
-
Originally posted by Chewi View PostYes, Linux is certainly not free of this issue or any OS for that matter because this is a hardware issue. I half joked that you wouldn't see it on Windows because it's never idle for long enough. Turns out AMD have privately said exactly the same thing. So yes, they are aware of the issue but it doesn't seem like they're going to admit it publicly. They told me directly that it would be fixed in a BIOS update but I'm not holding my breath. For now, I am using the CONFIG_RCU_NOCB_CPU workaround (which I discovered, you're welcome ) and I have seen maybe two freezes in the months since. I can't swear they weren't caused by something else but I don't believe the workaround is 100% effective.
Comment
Comment