Bug 1657453
| Summary: | 4.20.0-0.rc5 failure to boot due to amdgpu and iwlwifi issues | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James A. Robinson <jim.robinson> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 29 | CC: | airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, phea.duch, steved |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-12-17 22:14:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
James A. Robinson
2018-12-08 11:13:23 UTC
If you are using the vanilla packages your best bet is to run git bisect between the working and non-working kernel version to find which commit broke boot on your machine. Hi, I went through the process of a git bisect between v4.20-rc4 and v4.20-rc5 and didn't find anything. I ought to have tried a v4.20-rc4 build right off the bat using the rc5 config, because that would have clued me in on the issue. Turns out I can build v4.20-rc5 w/o any problem as long as CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not on. Here are the differences in the config distrubuted with the packages: $ diff /boot/config-4.20.0-0.rc4.git1.1.vanilla.knurd.1.fc29.x86_64 /boot/config-4.20.0-0.rc5.git3.1.vanilla.knurd.1.fc29.x86_64 3c3 < # Linux/x86_64 4.20.0-0.rc4.git1.1.vanilla.knurd.1.fc29.x86_64 Kernel Configuration --- > # Linux/x86_64 4.20.0-0.rc5.git3.1.vanilla.knurd.1.fc29.x86_64 Kernel Configuration 23c23 < CONFIG_BUILD_SALT="4.20.0-0.rc4.git1.1.vanilla.knurd.1.fc29.x86_64" --- > CONFIG_BUILD_SALT="4.20.0-0.rc5.git3.1.vanilla.knurd.1.fc29.x86_64" 104a105 > # CONFIG_PSI_DEFAULT_DISABLED is not set 381c382 < # CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set --- > CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y 740a742 > CONFIG_KVM_AMD_SEV=y 5725d5726 < CONFIG_SND_SOC_INTEL_SKYLAKE_SSP_CLK=m 5726a5728,5730 > CONFIG_SND_SOC_INTEL_SKYLAKE_SSP_CLK=m > CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC=y > CONFIG_SND_SOC_INTEL_SKYLAKE_COMMON=m 5750d5753 < CONFIG_SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m 5751a5755 > CONFIG_SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m 8114c8118 < # CONFIG_CRYPTO_DEV_SP_PSP is not set --- > CONFIG_CRYPTO_DEV_SP_PSP=y Copying config-4.20.0-0.rc5.git3.1.vanilla.knurd.1.fc29.x86_64 to my v4.20-rc5 to my kernel tree .config and changing CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT to match the rc4 release allows me to compile a kernel that boots properly on my system: $ diff /boot/config-4.20.0-0.rc5.git3.1.vanilla.knurd.1.fc29.x86_64 .config 3c3 < # Linux/x86_64 4.20.0-0.rc5.git3.1.vanilla.knurd.1.fc29.x86_64 Kernel Configuration --- > # Linux/x86 4.20.0-rc5 Kernel Configuration 382c382 < CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y --- > # CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set My CPU is an AMD 2990WX, my BIOS is running AGESA 1.0.0.2. I'm thinking this may be a long standing bug... I see in this old thread: [SOLVED] Problem with AMDGPU: blank screen at boot https://forums.gentoo.org/viewtopic-t-1074902-postdays-0-postorder-asc-start-0.html a comment: PostPosted: Sat Jan 06, 2018 3:49 pm "I had a similar error with my Vega 64 and the latest 4.15-rc kernel which went away when I disabled AMD Secure Memory Encryption (SME) support under Processor Type and Features, although could be completely unrelated to your issue." There's also quite a bit of discussion in that thread about firmware modules, but honestly it reads a lot like people who don't really know what they are talking about suggesting blind changes because "it works for them." The easiest workaround to this so far has been for me to adjust /etc/sysconfig/grub to include mem_encrypt=off in the GRUB_CMDLINE_LINUX, so for example: GRUB_CMDLINE_LINUX="resume=/dev/mapper/fedora_filum-swap rd.lvm.lv=fedora_filum/root rd.luks.uuid=luks-e348dab7-017b-4b74-a77c-0162668047e7 rd.lvm.lv=fedora_filum/swap rhgb quiet mem_encrypt=off" This allows me to install and boot off the fedora packaged kernels. CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is off again in the Rawhide kernels so I'll go ahead and close this. |