(In reply to Ivan Ivanov from comment #19) > For SLE15-SP3 CONFIG_RANDOM_TRUST_BOOTLOADER option is enabled > only for armv7h and arm64. > > For 'stable' same option is enabled for all other arches except Arm :-) > > If we do same tests for non-Arm arches and they are passing then > something in arch setup code is not Ok. If we don't do these tests > then CONFIG_RANDOM_TRUST_BOOTLOADER is broken since inception. The issue is basically that with CONFIG_RANDOM_TRUST_BOOTLOADER=y, the kernel crashes if both EFI and the device tree provide randomness. That means that only platforms which use a device tree and EFI can actually run into this issue. x86 and s390x don't use a DT, ppc doesn't use EFI and riscv isn't being tested by openQA so far. That leaves only ARM, but as you found out that doesn't have CONFIG_RANDOM_TRUST_BOOTLOADER=y in TW.