You are not logged in.

#1 2018-09-25 08:34:08

smonsays
Member
Registered: 2016-09-02
Posts: 22

[Solved] systemd-udevd blocked with recent AMD motherboards

I recently built a new desktop PC with an AMD Ryzen 2700 CPU. Unfortunately, I have trouble using the current kernel (lts-kernel works fine):

I have to wait a long time during the boot process while "triggering uevents". After a while the boot process continues and  I can successfully boot. Afterwards, the logs show the following message:

INFO: task systemd-udevd:254 blocked for more than 120 seconds.
Not tainted 4.18.9-arch1-1-ARCH #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

systemd-udevd   D    0   254      1 0x80000004
Call Trace:
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f1ae6b0f40d
Code: Bad RIP value.
RSP: 002b:00007ffe5bd1d438 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
RAX: ffffffffffffffda RBX: 0000564991d7d7c0 RCX: 00007f1ae6b0f40d
RDX: 0000000000000000 RSI: 00007f1ae65abecd RDI: 000000000000000c
RBP: 00007f1ae65abecd R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000000c R11: 0000000000000246 R12: 0000000000000000
R13: 0000564991d91de0 R14: 0000000000020000 R15: 0000564991d7d7c0

I am not really sure what I am dealing with and how to further investigate this problem. If you need further information to identify the problem, please let me know!

Last edited by smonsays (2018-10-01 14:14:37)

Offline

#2 2018-09-25 10:42:53

Slithery
Forum Moderator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 2,960

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

Try updrading (or downgrading) your motherboard firmware. My 2700X system has the same issues with the latest revision, but is fine with the previous one.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2018-09-25 17:28:31

piratebill
Member
From: Sol System
Registered: 2011-10-20
Posts: 97

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

I have the exact same issue with my recently built threadripper. Motherboard is an Asus running the latest firmware (would post the version, but I'm not currently at home).

Offline

#4 2018-09-25 21:39:32

smonsays
Member
Registered: 2016-09-02
Posts: 22

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

I have the Asrock Fatal1ty B450 Gaming-ITX/ac motherboard with UEFI version 1.20 (Changelog: Keep the XMP setting after system resuming from S5 or G3 state.).

Slithery wrote:

Try updrading (or downgrading) your motherboard firmware. My 2700X system has the same issues with the latest revision, but is fine with the previous one.

Unfortunately, there is no upgrade and I would rather not downgrade the UEFI if possible. The fact that the LTS kernel is working without problems led me to think that this is actually a bug in the current kernel 4.18.9 (which was probably introduced before that version, but as I just built the system I am not sure when).

Offline

#5 2018-09-26 20:20:05

Omar007
Member
Registered: 2015-04-09
Posts: 265

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

The problem is with the AGESA version in the latest firmware releases. The system is hanging on the ccp.ko module.
You can work around this for now by recompiling the kernel with:

CONFIG_CRYPTO_DEV_SP_PSP=n

Offline

#6 2018-09-26 20:52:19

loqs
Member
Registered: 2014-03-06
Posts: 6,210

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

From 4.18.10 perhaps this might help

commit 52b7326483715cce64474aab0367e0428a59ae90
Author: Brijesh Singh <brijesh.singh@amd.com>
Date:   Wed Aug 15 16:11:25 2018 -0500

    crypto: ccp - add timeout support in the SEV command
    
    commit 3702a0585e64d70d5bf73bf3e943b8d6005b72c1 upstream.
    
    Currently, the CCP driver assumes that the SEV command issued to the PSP
    will always return (i.e. it will never hang).  But recently, firmware bugs
    have shown that a command can hang.  Since of the SEV commands are used
    in probe routines, this can cause boot hangs and/or loss of virtualization
    capabilities.
    
    To protect against firmware bugs, add a timeout in the SEV command
    execution flow.  If a command does not complete within the specified
    timeout then return -ETIMEOUT and stop the driver from executing any
    further commands since the state of the SEV firmware is unknown.
    
    Cc: Tom Lendacky <thomas.lendacky@amd.com>
    Cc: Gary Hook <Gary.Hook@amd.com>
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    [Brijesh: Backported to 4.18..4.19 - offset change in few hunks]
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Offline

#7 2018-09-26 21:23:40

piratebill
Member
From: Sol System
Registered: 2011-10-20
Posts: 97

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

Good catch Omar007. More info on this bug here https://bugzilla.redhat.com/show_bug.cgi?id=1608242

Last edited by piratebill (2018-09-26 21:31:49)

Offline

#8 2018-09-26 21:36:42

smonsays
Member
Registered: 2016-09-02
Posts: 22

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

Yes, looks like it should be fixed in linux 4.19 then (https://lwn.net/Articles/766425/).

Brijesh Singh (3):
      crypto: ccp - add timeout support in the SEV command
      x86/mm: Add .bss..decrypted section to hold shared variables
      x86/kvm: Use __bss_decrypted attribute in shared variables

Thanks everyone!

Offline

#9 2018-09-26 22:55:55

loqs
Member
Registered: 2014-03-06
Posts: 6,210

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

What about linux 4.18.10.arch1-1 in testing?

Offline

#10 2018-09-27 20:11:48

smonsays
Member
Registered: 2016-09-02
Posts: 22

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

loqs wrote:

What about linux 4.18.10.arch1-1 in testing?

Ah true, your posts suggests that the change is backported to 4.18.

Last edited by smonsays (2018-09-27 22:01:40)

Offline

#11 2018-09-28 14:37:01

piratebill
Member
From: Sol System
Registered: 2011-10-20
Posts: 97

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

4.18.10 came out this morning. Looks fixed to me.

Offline

#12 2018-09-30 01:52:55

peteb
Member
Registered: 2018-09-22
Posts: 2

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

Upgraded to 4.18.10 this morning.  I have a B350 MSI Tomahawk motherboard with the latest AGESA 1.0.0.4C bios.  Boot hangs indefinitely with the following error message. 

8.157104] ccp 0000:21:00.2: sev command 0x4 timed out, disabling PSP
8.157162] ccp 0000:21:00.2: SEV: failed to get status.  Error: 0x0
8.167621] kvm: disabled by bios 

Offline

#13 2018-09-30 22:16:06

smonsays
Member
Registered: 2016-09-02
Posts: 22

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

I just upgraded as well. It looks fixed to me as well.

peteb wrote:

Upgraded to 4.18.10 this morning.  I have a B350 MSI Tomahawk motherboard with the latest AGESA 1.0.0.4C bios.  Boot hangs indefinitely with the following error message. 

8.157104] ccp 0000:21:00.2: sev command 0x4 timed out, disabling PSP
8.157162] ccp 0000:21:00.2: SEV: failed to get status.  Error: 0x0
8.167621] kvm: disabled by bios 

I also get the "timed out" message, I think this is part of the fix because the actual bug lies within the firmware as far as I have understood. However, for me the boot process resumes afterward.

Offline

#14 2018-10-16 18:53:43

ismet
Member
Registered: 2018-10-16
Posts: 1

Re: [Solved] systemd-udevd blocked with recent AMD motherboards

Upgraded to 4.18.14 just now.

I keep getting exactly the same error.

I have got an ASRock X370 mobo with AGESA 1.0.0.4 bios.

Offline

Board footer

Powered by FluxBB