ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - New Asrock X470 Taichi UEFI 1.50
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

New Asrock X470 Taichi UEFI 1.50

 Post Reply Post Reply Page  12>
Author
Message
LowerBavarian View Drop Down
Newbie
Newbie


Joined: 19 Jul 2018
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote LowerBavarian Quote  Post ReplyReply Direct Link To This Post Topic: New Asrock X470 Taichi UEFI 1.50
    Posted: 19 Jul 2018 at 3:49am
Hi *,

after getting my new Taichi Board and installing my new System I made a upgrade to the newest UEFI 1.50 I discovered following issues:
WIth WIndows 10 Pro the PC will start and run normally BUT
If I try to boot into my Fedora 28 or try to reinstall Fedora 28 the system freezes during booting with following messages:

sp5100-tco sp5100-tco: Watchdog hardware is disabled



seq 3191 '/devices/pci0000:00/0000:00:07.1/0000:2f:00.2' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3334 '/devices/system/cpu/cpu2' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3333 '/devices/system/cpu/cpu15' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3336 '/devices/system/cpu/cpu4' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3326 '/devices/system/cpu/cpu0' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3340 '/devices/system/cpu/cpu8' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3338 '/devices/system/cpu/cpu6' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3341 '/devices/system/cpu/cpu9' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3339 '/devices/system/cpu/cpu7' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3337 '/devices/system/cpu/cpu5' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3335 '/devices/system/cpu/cpu3' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3327 '/devices/system/cpu/cpu1' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3331 '/devices/system/cpu/cpu13' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3330 '/devices/system/cpu/cpu12' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3329 '/devices/system/cpu/cpu11' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3332 '/devices/system/cpu/cpu14' is taking a long time
Jul 09 18:22:41 earthling.universe systemd-udevd[745]: seq 3328 '/devices/system/cpu/cpu10' is taking a long time
Jul 09 18:23:10 earthling.universe systemd[1]: dev-mapper-fedora\x2dhome.device: Job dev-mapper-fedora\x2dhome.device/start timed out.
Jul 09 18:23:10 earthling.universe systemd[1]: Timed out waiting for device dev-mapper-fedora\x2dhome.device.


Failed to start udev Wait for Complete Device Initialization.
-- Subject: Unit systemd-udev-settle.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-udev-settle.service has failed.



seq 3191 '/devices/pci0000:00/0000:00:07.1/0000:2f:00.2' killed



seq 3340 '/devices/system/cpu/cpu8' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3339 '/devices/system/cpu/cpu7' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3341 '/devices/system/cpu/cpu9' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3327 '/devices/system/cpu/cpu1' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3337 '/devices/system/cpu/cpu5' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3334 '/devices/system/cpu/cpu2' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3333 '/devices/system/cpu/cpu15' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3335 '/devices/system/cpu/cpu3' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3338 '/devices/system/cpu/cpu6' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3336 '/devices/system/cpu/cpu4' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3326 '/devices/system/cpu/cpu0' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3332 '/devices/system/cpu/cpu14' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3329 '/devices/system/cpu/cpu11' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3330 '/devices/system/cpu/cpu12' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3331 '/devices/system/cpu/cpu13' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: seq 3328 '/devices/system/cpu/cpu10' killed
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [776] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [776] failed while handling '/devices/system/cpu/cpu9'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [759] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [759] failed while handling '/devices/system/cpu/cpu3'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [749] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [749] failed while handling '/devices/system/cpu/cpu1'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [750] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [750] failed while handling '/devices/system/cpu/cpu15'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [755] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [755] failed while handling '/devices/system/cpu/cpu6'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [756] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [756] failed while handling '/devices/system/cpu/cpu7'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [758] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [758] failed while handling '/devices/system/cpu/cpu14'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [763] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [763] failed while handling '/devices/system/cpu/cpu0'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [766] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [766] failed while handling '/devices/system/cpu/cpu13'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [752] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [752] failed while handling '/devices/system/cpu/cpu10'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [768] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [768] failed while handling '/devices/system/cpu/cpu12'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [777] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [777] failed while handling '/devices/system/cpu/cpu5'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [779] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [779] failed while handling '/devices/system/cpu/cpu8'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [780] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [780] failed while handling '/devices/system/cpu/cpu11'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [782] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [782] failed while handling '/devices/system/cpu/cpu4'
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [784] terminated by signal 9 (KILL)
Jul 09 18:24:41 earthling.universe systemd-udevd[745]: worker [784] failed while handling '/devices/system/cpu/cpu2'

After downgrading to Stock Bios/UEFI v1.1 everything runs fine.

Is there any support how to use the new Bios/UEFI and use Linux?

Greetings

Tobi
ASROCK X470 Taichi
AMD Ryzen 7 2700X
GSKILL Flare X 3200
Palit GTX 1070 TI JetStream
Back to Top
datonyb View Drop Down
Senior Member
Senior Member


Joined: 11 Apr 2017
Location: London U.K.
Status: Offline
Points: 1728
Post Options Post Options   Thanks (1) Thanks(1)   Quote datonyb Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jul 2018 at 4:41am
the bad news = i know very very little about linux

the good news = level1techs (on you tube and a forum i think) seem to know a very very lot about linux and wendell the you tube presenter seems to favour asrock boards

it may well help you faster if you ask over there while waiting for answer here
i know he uses a x370 taichi ,i dont know if he has a x470 yet though

r7 1700 powercolor reddevil vega64 gskill tridentz3866 taichi x370 evga 750watt gold
Back to Top
LowerBavarian View Drop Down
Newbie
Newbie


Joined: 19 Jul 2018
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote LowerBavarian Quote  Post ReplyReply Direct Link To This Post Posted: 20 Jul 2018 at 4:17am
Thx for your reply. I will head over to the forums you mentioned and see if someone can help me...

Greetings from Lower Bavaria

Tobi
ASROCK X470 Taichi
AMD Ryzen 7 2700X
GSKILL Flare X 3200
Palit GTX 1070 TI JetStream
Back to Top
sonix View Drop Down
Newbie
Newbie


Joined: 05 Aug 2018
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote sonix Quote  Post ReplyReply Direct Link To This Post Posted: 05 Aug 2018 at 5:32pm
I'm having the same issue with arch linux, kernel 4.17.11, Bios 1.50 taichi ultimate.
The system takes very long time to shut down and hardware acceleration for virtualization (KVM) is not working for me after the bios update. It is definitely turned on on the bios (SVM, SR-IOV, IOMMU), running virtual machines is unfortunately the main reason I purchased this computer in the first place.
I've tried many UEFI settings (also clear cmos) without any success, I'm very certain that this bug was introduced with the new UEFI 1.5 version. Angry
I'm not sure if this is relevant but I did not overclock anything.

@asrock can you confirm this behavior? This is one of the most expensive AM4 motherboards on the market, I would hope to see this resolved in the near future. btw where can I find the changelog of a bios version? 

Back to Top
pmo View Drop Down
Newbie
Newbie


Joined: 06 Aug 2018
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote pmo Quote  Post ReplyReply Direct Link To This Post Posted: 06 Aug 2018 at 1:34am
I'm having the same issue on my MSI X470 Gaming Pro board.
Old BIOS 7B79v13 works fine. Latest BIOS 7B79v14 fails exactly the same way.

Back to Top
Hector244 View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Aug 2018
Location: Warsaw, PL
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Hector244 Quote  Post ReplyReply Direct Link To This Post Posted: 07 Aug 2018 at 4:31am
Im having exacly the same issue - Fedora 28 Live can't boot with udevd errors.

I can't find anything in BIOS that can prevent this from happening. My system is stable, no manually overclocked. I'm able to boot Ubuntu 18.01, but I need to run Fedora and I'm very disappointed.

ASRock X470 Taichi. R7 2700X, 32GB RAM (2933MHz), Radeon RX 570.
BIOS 1.50

It happens every time.


Edited by Hector244 - 07 Aug 2018 at 4:34am
Back to Top
equeim View Drop Down
Newbie
Newbie


Joined: 08 Aug 2018
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote equeim Quote  Post ReplyReply Direct Link To This Post Posted: 08 Aug 2018 at 5:33am
I have the same issue on my AB350 Pro4 with Ryzen 5 2600 after updating BIOS from 4.70 to 5.00 version. It doesn't reproduce on Arch Linux, only on Fedora.

EDIT: BIOS 4.90 is working fine, so the issue is in the latest 5.00 version. Interesting, that this BIOS and 1.50 for X470 both have AGESA PinnaclePI-AM4_1.0.0.4. Maybe this is the reason.


Edited by equeim - 08 Aug 2018 at 6:17am
Back to Top
Hector244 View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Aug 2018
Location: Warsaw, PL
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Hector244 Quote  Post ReplyReply Direct Link To This Post Posted: 09 Aug 2018 at 2:57pm
Shocked ASRock X470 Taichi - had to downgrade BIOS to (beta) 1.35 and Fedora 28 boots normally.

@ASRock - please Investigate it with AMD - this is really annoying!
Back to Top
Ilazki View Drop Down
Newbie
Newbie


Joined: 09 Aug 2018
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote Ilazki Quote  Post ReplyReply Direct Link To This Post Posted: 09 Aug 2018 at 3:33pm
I hope it's not against any rules or anything to talk about other vendors here, because I don't have an ASRock board but I'm having the same problem and this is the only hit I've gotten for the symptoms when searching online.  I updated the bios of my MSI board (x370 SLI PLUS) today to one that mentions "Update AGESA Code 1.0.0.4C" in its patch notes, and immediately started seeing a long hang during bootup with the same sort of messages as the OP.  It eventually boots on its own (or ctrl-C to move on early), but udev is a broken mess when doing so, spawning 30+ processes and frequently causing spam in dmesg about systemd-udevd hanging for over 120 seconds.

Unfortunately I'm not able to downgrade the bios back to a usable version because the BIOS-based flash won't allow downgrading, but I did discover a workaround that might also be relevant to figuring out what's happening.  I have a habit of not removing old kernels after updating, so I was able to experiment with a few and found that 4.14.13 has no issues, but 4.16.12 and 4.17.8 both exhibit the broken behaviour.  I don't know if it's an AGESA problem or a kernel bug, but somewhere between 4.14.13 and 4.16.12 something changed in the kernel that is making something break horribly.

Also, I don't know if the OP ever tried getting help on the L1techs forum, but I searched there myself and saw that a few of them noticed something I also did:  the hardware device at the beginning of those errors is listed as AMD's "Encryption Controller", managed by driver "ccp".  It's used for hardware encryption but apparently is also related to AMD's Platform Security Processor (PSP).  Kernel 4.14 is when they first started adding support for the PSP part, so maybe incomplete support for it is why that one works okay for me.  Anyway, one person claims the problem went away when using a kernel compiled with CONFIG_CRYPTO_DEV_SP_PSP=n.  They didn't mention virtualisation or any negative effects, so YMMV there.  

For now, I'm just going to keep using the old 4.14 kernel I have and watch for a fix.  I got lucky by still having that kernel around, because it's in a sweet spot of being barely new enough to have the nested page table (NPT) bug fix (which is a big deal for GPU passthrough to a VM, which I use heavily), but is old enough to not be affected by whatever is breaking things.  

Neither option (disabling the feature in a kernel compile and hoping it doesn't affect anything important, or using a 4.14 kernel) is a good solution, but I'm mentioning everything I've found on the problem so far in case it helps anyone else with finding a workaround or reporting the problem.  This situation sucks, but hopefully it gets noticed and fixed soon.


Edited by Ilazki - 09 Aug 2018 at 3:34pm
Back to Top
Hector244 View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Aug 2018
Location: Warsaw, PL
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote Hector244 Quote  Post ReplyReply Direct Link To This Post Posted: 09 Aug 2018 at 4:32pm
Thanks for information. I'm trying to get AMD attention on Twitter with this topic.
Back to Top
 Post Reply Post Reply Page  12>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.06
Copyright ©2001-2018 Web Wiz Ltd.

This page was generated in 0.047 seconds.