(In reply to Ashesh Ambasta from comment #680)
> I've been facing the same issue since I've bought this machine and setting
> my BIOS power settings to "Typical current idle" has only partially fixed
> things (the system still crashes every 1-2 weeks during idle: I leave my
> desk, screensaver fires up, then screens go to sleep, and by the time I get
> back to my desk, the system no longer responds to any input and the only
> option is a hard reset.).
> 
> At the time of writing, I can't tell if the AGESA version has made it into
> my motherboard: https://www.asrock.com/mb/AMD/X399M%20Taichi/index.asp#BIOS 

[I have an MSI board, but checked the firmware update files for you.]

The description for version 3.60 includes:

> Update AMD AGESA ThreadRipperPI-SP3r2 1.1.0.2

Reading the ASRock forum thread *What happened to Fatality X399 Bios
1.60?* [1], it’s enough to run the firmware update file through a
hexeditor. I searched for *GES* and was lucky for version 3.80.

    $ hexdump -C X399MT3.80 | less
    […]
    00e34ce0  00 00 00 00 00 00 00 00  00 00 00 00 be 2c 63 17  
|.............,c.|
    00e34cf0  80 6c b6 49 82 07 12 b5  3d 9b 25 70 41 47 45 53  
|.l.I....=.%pAGES|
    00e34d00  41 21 56 39 00 54 68 72  65 61 64 52 69 70 70 65  
|A!V9.ThreadRippe|
    00e34d10  72 50 49 2d 53 50 33 72  32 2d 31 2e 31 2e 30 2e  
|rPI-SP3r2-1.1.0.|
    00e34d20  32 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  
|2...............|
[…]
```

So, it still has AGESA version 1.1.0.2.

[…]


[1]: 
http://forum.asrock.com/forum_posts.asp?TID=6165&PN=4&title=what-happened-to-fatality-x399-bios-160

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to