FS#66759 - [cryptsetup] blocks with 100% CPU usage

Attached to Project: Arch Linux
Opened by Raphael Nestler (rnestler) - Saturday, 23 May 2020, 22:12 GMT
Last edited by Christian Hesse (eworm) - Monday, 25 May 2020, 11:09 GMT
Task Type Bug Report
Category Other
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I was trying to do the following:

cryptsetup -y -v luksFormat /dev/nvme0n1p2

cryptsetup blocks with 100% CPU usage and was only killable with kill -9. I rebooted, tried to upgrade cryptsetup on the live media, but nothing helped. Just formatting the disk with mkfs worked.

Is this a bug in cryptsetup? How could I debug this? I used 2020.05.01
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 25 May 2020, 11:09 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#66531 
Comment by Raphael Nestler (rnestler) - Sunday, 24 May 2020, 10:36 GMT
I created an upstream issue as well: https://gitlab.com/cryptsetup/cryptsetup/-/issues/567
Comment by Raphael Nestler (rnestler) - Sunday, 24 May 2020, 11:10 GMT
A BIOS upgrade fixed the issue for me. Funny enough: When I booted with a Debian (with an older kernel and cryptsetup) cryptsetup worked without problems there.
Comment by David Runge (dvzrv) - Sunday, 24 May 2020, 13:51 GMT
@rnestler: Thanks for the report.

I have moved this ticket to the correct project on flyspray (Arch Linux), as it's not a release engineering bug per se.
Also thanks for adding the upstream ticket.
Comment by Christian Hesse (eworm) - Monday, 25 May 2020, 11:08 GMT
You are running a recent AMD CPU?
Guess this is the well known RDRAND issue, lately spotted in json-c.
Update json-c on the live media and you are fine.

Loading...