Jammy kernel does not boot when Secure Encrypted Virtualization( SEV) is enabled

[Louis Bouchard]

Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor of the kernel does not boot on a QEMU server with Secure Encrypted Virtualization( SEV) enabled.

Using the same kernel without the -kvm optimisation does boot correctly
---
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Dec 20 10:41 seq
 crw-rw---- 1 root audio 116, 33 Dec 20 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:

Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: Scaleway SCW-ENT1-XL
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-23-generic N/A
 linux-backports-modules-5.13.0-23-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.13.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-3.0
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
dmi.product.name: SCW-ENT1-XL
dmi.product.version: pc-q35-3.0
dmi.sys.vendor: Scaleway

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1955395

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

apport information

[Louis Bouchard (louis)]

Recent tests with the most recent 5.15 kernel (5.15.0-25-generic) do display the same problem, though the symptom is different.

Booting w/o the swiotlb=262144 leads to the boot sequence stopping after these messages :

[ 1.376749] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD
[ 1.379840] cryptd: max_cpu_qlen set to 1000
[ 1.381359] scsi host1: ahci
[ 1.384854] AVX2 version of gcm_enc/dec engaged.
[ 1.385579] AES CTR mode by8 optimization enabled
[ 1.386280] scsi host2: ahci
[ 1.387162] scsi host3: ahci
[ 1.387659] scsi host4: ahci
[ 1.388141] scsi host5: ahci
[ 1.388675] scsi host6: ahci
[ 1.389091] ata1: SATA max UDMA/133 abar m4096@0x91000000 port 0x91000100 irq 36
[ 1.389937] ata2: SATA max UDMA/133 abar m4096@0x91000000 port 0x91000180 irq 36
[ 1.390787] ata3: SATA max UDMA/133 abar m4096@0x91000000 port 0x91000200 irq 36
[ 1.391599] ata4: SATA max UDMA/133 abar m4096@0x91000000 port 0x91000280 irq 36
[ 1.392417] ata5: SATA max UDMA/133 abar m4096@0x91000000 port 0x91000300 irq 36
[ 1.393251] ata6: SATA max UDMA/133 abar m4096@0x91000000 port 0x91000380 irq 36
[ 1.707933] ata3: SATA link down (SStatus 0 SControl 300)
[ 1.709684] ata4: SATA link down (SStatus 0 SControl 300)
[ 1.711379] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.712945] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.714405] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.715926] ata6: SATA link down (SStatus 0 SControl 300)
[ 3.352937] pcieport 0000:00:1e.0: pciehp: Slot(0): No device found
[ 3.356935] pcieport 0000:00:1e.2: pciehp: Slot(2): No device found
[ 3.368942] pcieport 0000:00:1e.1: pciehp: Slot(1): No device found
[ 3.368958] pcieport 0000:00:1e.3: pciehp: Slot(3): No device found
[ 3.384970] pcieport 0000:00:1e.4: pciehp: Slot(4): No device found
[ 3.384991] pcieport 0000:00:1e.6: pciehp: Slot(6): No device found
[ 3.396926] pcieport 0000:00:1e.5: pciehp: Slot(5): No device found
[ 3.396957] pcieport 0000:00:1e.7: pciehp: Slot(7): No device found

And after a period of time we start seeing :
[ 242.880954] INFO: task kworker/u16:0:8 blocked for more than 120 seconds.
[ 242.882063] Not tainted 5.15.0-25-generic #25-Ubuntu
[ 242.882895] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 242.884165] task:kworker/u16:0 state:D stack: 0 pid: 8 ppid: 2 flags:0x00004000 ...