Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Created attachment 1617361[details]
Snapshots of the kernel panics.
1. Please describe the problem:
This appears to be an ongoing problem with Dell optiplex desktops and the linux kernel. I performed a system upgrade from Fedora 30 to Fedora 31 beta on an Dell Optiplex 3050. The upgrade appears to go fine, I saw the progress bars reach 100% but while attempting the reboot that immediately follows the upgrade, a kernel panic occurs. (See attachment image1). The system operates normally but now after each reboot the system fails to start and will kernel panic (See attachment image2)
The only way the system boot successfully is if it fully powers down. Either by issuing a normal shutdown or using the power button (after a panic). This reminded me of my Dell optiplex 790 that would hang whenever a normal reboot was issued, so I attempted the same fix. I added 'reboot=pci' to the kernel boot parameters and now there are no more kernel panics.
2. What is the Version-Release number of the kernel: 5.3.0-1
3. Did it work previously in Fedora?
This desktop could reboot just fine in Fedora 30 on kernel 5.2. But after upgrading to Fedora 31 beta with kernel 5.3 it kernel panics when a reboot is issued.
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
Yes it is reproducible but may be limited to Dell desktops. As stated a similar issue occurs on my previous Dell Optiplex. But simply install Fedora 31 beta on an Dell Optiplex 3050 and attempt to reboot.
5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``:
I will have to try this later.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
No
7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.
I will also have to run this next week.
7. Workaround: Add 'reboot=pci' to the kernel boot parameters in /etc/default/grub and rebuild grub.
Created attachment 1617361 [details] Snapshots of the kernel panics. 1. Please describe the problem: This appears to be an ongoing problem with Dell optiplex desktops and the linux kernel. I performed a system upgrade from Fedora 30 to Fedora 31 beta on an Dell Optiplex 3050. The upgrade appears to go fine, I saw the progress bars reach 100% but while attempting the reboot that immediately follows the upgrade, a kernel panic occurs. (See attachment image1). The system operates normally but now after each reboot the system fails to start and will kernel panic (See attachment image2) The only way the system boot successfully is if it fully powers down. Either by issuing a normal shutdown or using the power button (after a panic). This reminded me of my Dell optiplex 790 that would hang whenever a normal reboot was issued, so I attempted the same fix. I added 'reboot=pci' to the kernel boot parameters and now there are no more kernel panics. 2. What is the Version-Release number of the kernel: 5.3.0-1 3. Did it work previously in Fedora? This desktop could reboot just fine in Fedora 30 on kernel 5.2. But after upgrading to Fedora 31 beta with kernel 5.3 it kernel panics when a reboot is issued. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes it is reproducible but may be limited to Dell desktops. As stated a similar issue occurs on my previous Dell Optiplex. But simply install Fedora 31 beta on an Dell Optiplex 3050 and attempt to reboot. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I will have to try this later. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. I will also have to run this next week. 7. Workaround: Add 'reboot=pci' to the kernel boot parameters in /etc/default/grub and rebuild grub.