Description of problem: Kernel Panic on boot (CPIO Magick error) after dnf upgrade upgraded kernel to 4.18.7-200.fc28.i686 from 4.18.5-200.fc28.i686. Had to set default boot kernel in grub2 to 4.18.5-200.fc28.i686 in order to boot system. Version-Release number of selected component (if applicable): kernel 4.18.7-200.fc28 How reproducible: Boot kernel 4.18.7-200.fc28 Steps to Reproduce: 1.Boot Kernel 4.18.7-200.fc28 2. 3. Actual results: Kernel panic and CPIO Magick error Expected results: Fedora boots without panic. Additional info: cat /etc/grub2.cfg | grep menuentry if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" menuentry_id_option="" export menuentry_id_option menuentry 'Fedora (4.18.7-200.fc28.i686) 28 (Twenty Eight)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.16.3-301.fc28.i686-advanced-a17ad5dd-b3f1-4c37-b1cc-4604ea531918' { menuentry 'Fedora (4.18.5-200.fc28.i686) 28 (Twenty Eight)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.16.3-301.fc28.i686-advanced-a17ad5dd-b3f1-4c37-b1cc-4604ea531918' { menuentry 'Fedora (4.17.19-200.fc28.i686) 28 (Twenty Eight)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.16.3-301.fc28.i686-advanced-a17ad5dd-b3f1-4c37-b1cc-4604ea531918' { menuentry 'Fedora (0-rescue-c86137f1ca2f43eea7981952c3c9cb5a) 28 (Twenty Eight)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-c86137f1ca2f43eea7981952c3c9cb5a-advanced-a17ad5dd-b3f1-4c37-b1cc-4604ea531918' {
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.