Bug 199953 - [crypto][ccp] boot lockup on 2x EPYC system
Summary: [crypto][ccp] boot lockup on 2x EPYC system
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-06 21:00 UTC by Markus Hetzmannseder
Modified: 2018-06-20 21:28 UTC (History)
0 users

See Also:
Kernel Version: 4.16.x and 4.17.x
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Photo of lockup during boot (4.50 MB, image/jpeg)
2018-06-06 21:00 UTC, Markus Hetzmannseder
Details

Description Markus Hetzmannseder 2018-06-06 21:00:58 UTC
Created attachment 276353 [details]
Photo of lockup during boot

Hardware: 2x AMD Epyc 7501 on a ASUS Server RS700A-E9-RS12, 380GB RAM, 2x NVMe M.2 SSDs 

With compiled in crypto/ccp support, the kernel will lock up during boottime. Last messages are something like ccp enabled and fans starting to spin up to full speed. Exact messages see attached picture. (The exact numbers in the line differ from one lock up to the next on.)

This happens on all tested 4.14.* up 4.17 kernels with compiled in ccp module. On older kernels ccp was not included and this kernels are booting without problems (tested on stock debian kernel 4.9.* ans self compiled kernels 4.9.106 and 4.13.x)

New kernels with disabled ccp are booting as well. (tested with 4.17)



diff of working kernel .config to the not working on:

#################################
8461c8461,8464
< # CONFIG_CRYPTO_DEV_CCP_DD is not set
---
> CONFIG_CRYPTO_DEV_CCP_DD=m
> CONFIG_CRYPTO_DEV_SP_CCP=y
> CONFIG_CRYPTO_DEV_CCP_CRYPTO=m
> CONFIG_CRYPTO_DEV_SP_PSP=y
8507a8511
> CONFIG_KVM_AMD_SEV=y
#################################
Comment 1 Markus Hetzmannseder 2018-06-14 21:18:27 UTC
I have pinpointed the problem a bit closer. I get only boot lockups on that server with enabled CONFIG_CRYPTO_DEV_SP_PSP option. The other parts of the crypto/ccp code is working. This options is only available at 4.16.* and 4.17.* kernels and so only this kernels are getting the boot lockup and not the 4.15.* and below.

Note You need to log in before you can comment on or make changes to this bug.