|
X370 Taichi crashing on stock settings and C6 |
Post Reply 
|
Page <12 |
| Author | |
ricesteam 
Newbie 
Joined: 24 Apr 2018 Status: Offline Points: 13 |
 Post Options
 Thanks(0)
 Quote Reply
 Posted: 28 Apr 2018 at 4:50am |
 |
|
|
ricesteam
Newbie
Joined: 24 Apr 2018 Status: Offline Points: 13 |
Post Options
Thanks(0)
Quote Reply
Posted: 28 Apr 2018 at 6:41am |
|
FYI, the different C-States and what they mean: https://gist.github.com/wmealing/2dd2b543c4d3cff6cab7
tl;dr - basically, power saving features on the CPU.
|
|
|
|
|
ricesteam
Newbie
Joined: 24 Apr 2018 Status: Offline Points: 13 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 May 2018 at 9:00am |
|
Updated to the 4.64 beta bios.
Same problem as before if I have C-states on Auto (enabled). However I started to play with the Power Supply Control and switched it from Auto > Typical Current Idle. So far, my PC is stable. I guess my problem has been solved? Only time will tell... Edit: To be clear, C-states are on 'Auto' and Power Supply Control is on 'Typical Current Idle'. This resolved my issue.
Edited by ricesteam - 03 May 2018 at 2:15am |
|
|
|
|
Onox
Newbie
Joined: 27 Nov 2017 Status: Offline Points: 43 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 May 2018 at 2:05am |
|
Hi! So, you still have that wake up from sleep issue with this BIOS? I have never had the problem you describe, but I'm still on BIOS 3.2 (although Fedora sometimes throws a non-fatal error when waking up, which doesn't seem to have any serious consequence, as far as I can tell. It might not even be related) What I wonder is how much power savings I lose by keeping C6 disabled? My idle temps don't seem higher than before Edited by Onox - 03 May 2018 at 2:06am |
|
|
|
|
ricesteam
Newbie
Joined: 24 Apr 2018 Status: Offline Points: 13 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 May 2018 at 2:17am |
|
Sorry, my previous post wasn't clear. The issue is resolved by setting Power Supply Control to 'Typical Idle Current'. This setting allowed me to enable global C-states without any problems. Thus, when my computer sleeps I can now wake it up. Edited by ricesteam - 03 May 2018 at 2:17am |
|
|
|
|
shmerl
Groupie 
Joined: 23 Oct 2017 Status: Offline Points: 612 |
Post Options
Thanks(0)
Quote Reply
Posted: 18 May 2018 at 11:53am |
|
Sounds very similar to this bug: https://bugzilla.kernel.org/show_bug.cgi?id=196683 I thought it's fixed in Ryzen 2700X. My Ryzen 1700X was plagued by freezes on idle (on Linux) until I enabled "common current idle". I recently bought 2700X and it didn't have that bug anymore. Common current idle disables package C6 state (but keeps core C6 enabled).
|
|
|
|
|
Onox
Newbie
Joined: 27 Nov 2017 Status: Offline Points: 43 |
Post Options
Thanks(0)
Quote Reply
Posted: 14 Jun 2018 at 9:30pm |
Interesting, thank you! I just had a freeze + reboot today, still with BIOS 3.2 and C6
disabled. I hadn't had a crash for weeks. I don't really have the time to investigate now, but it could be that same bug
Found this in the logs : mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1528987490 SOCKET 0 APIC e microcode 8001129 mce: [Hardware Error]: TSC 0 IPID 300b000000000 mce: [Hardware Error]: CPU 14: Machine Check: 0 Bank 3: b2a00020003f0000 Strangely, the
indicated time for those three entries is also wrong (16:44 but it was 14:45,
as the next entries also tell). Those lines were displayed when the
computer rebooted too I'll try to upgrade the BIOS soon Edited by Onox - 14 Jun 2018 at 10:14pm |
|
|
|
|
Onox
Newbie
Joined: 27 Nov 2017 Status: Offline Points: 43 |
Post Options
Thanks(0)
Quote Reply
Posted: 15 Jun 2018 at 9:23pm |
|
Froze twice today on Fedora... if this is the same issue as before (I'm not sure, since I didn't use to have the same kind of error message (as shown in my previous post), and since I haven't had Windows crash again yet), that's a huge increase in the frequency of crashes =( The latest kernel updates might have changed something for the worse Edit : I have found out about the Ryzen "segfault bug", I tried the kill-ryzen test, and it seems that my processor is affected... RMA time is approaching I guess
Edited by Onox - 15 Jun 2018 at 10:45pm |
|
|
|
|
Post Reply
|
Page <12 |
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
ricesteam wrote: