The ccp(4) driver immediately hangs if I try to use it on a freshly installed 13.3-BETA3 system. I can load the driver, but it immediately hangs the first time I try to use it, which is by creating a geli device.
> sudo kldload ccp
> sudo mdconfig -a -t swap -s 64m
> sudo geli onetime -e aes-xts -l 256 -s 4096 /dev/md0
In another terminal, dmesg shows that it ccp is indeed being used:
ccp0: <AMD CCP-5a> mem 0xfc000000-0xfc0fffff,0xfc1cc000-0xfc1cdfff irq 54 at device 0.2 on pci12
random: registering fast source AMD CCP TRNG
GEOM_ELI: Device md0.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI: Crypto: hardware
> uname -a
FreeBSD XXX.YYY 13.0-BETA3 FreeBSD 13.0-BETA3 #0 releng/13.0-n244525-150b4388d3b: Fri Feb 19 04:04:34 UTC 2021 email@example.com:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
> sysctl hw.model
hw.model: AMD Ryzen 3 3200G with Radeon Vega Graphics
I think there is an earlier ccp/geli bug you can dupe this to. I suggest not loading ccp.ko.
I found an earlier bug about a panic; I didn't find any about a hang. Should we disable ccp from the GENERIC build?
Sure, let’s disable it.
I can also add that on my Ryzen 3 3200U with Radeon Vega Mobile the hardware looked like it worked but it never generated an interrupt (or, at least, it was never received). Tested with both our ccp and on Linux (5.6).
Just ran into this on my NAS box which has an AMD Ryzen 3 2200G CPU, running 13.0-RELEASE-p6. If this hardware didn't generate an interrupt under both FreeBSD and Linux, is it a hardware bug of some kind?
(In reply to Joshua Kinard from comment #5)
Who knows... there is no public documentation for it.