Ubuntu
linux package

Ubuntu 20.10 install image does not boot

Bug #1878341 reported by Martin Měřinský
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 20.04 LTS install image doesn't boot on my computer, where Ubuntu 19.10 works just fine.
CPU AMD Phenom II X4 965
RAM Kingston, DDR3, 4 × 4 GiB
MB Gigabyte GA-990XA-UD3 rev. 1.1, Last BIOS
GPU Gigabyte Radeon RX 550
Result is kernel panic.

The same image on the same USB flash disk works on another computer, so problem isn't caused by corrupted image download or malfunctioned USB flash disk.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mermar 1791 F.... pulseaudio
 /dev/snd/controlC1: mermar 1791 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-10-30 (197 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 enp4s0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=1c03cde1-ba25-4c24-bd9b-31b9cf3051f6 ro
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-51-generic N/A
 linux-backports-modules-5.3.0-51-generic N/A
 linux-firmware 1.183.5
RfKill:

Tags: eoan wayland-session
Uname: Linux 5.3.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/09/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14e
dmi.board.name: GA-990XA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990XA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

See original description
Revision history for this message
Martin Měřinský (mermar) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1878341/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Jouni Mettala (jouni-mettala) wrote :

I classify this kernel panic as a bug in linux. Then kernel developers can have a look. Bot will ask you to collect information. You can run apport collect from 19.10 to get more detailed hardware information.

Do you have 19.10 installed on that computer? Could you test some kernels there? Be sure that you can select older kernel in grub when new one panics.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1878341

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: focal
Revision history for this message
Martin Měřinský (mermar) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected eoan wayland-session
description: updated
Revision history for this message
Martin Měřinský (mermar) wrote : CRDA.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : Lspci.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : Lsusb.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : ProcEnviron.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : ProcModules.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : PulseList.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : UdevDb.txt

apport information

Revision history for this message
Martin Měřinský (mermar) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jouni Mettala (jouni-mettala) wrote : Re: Ubuntu 20.04 install image does not boot

This is from boot screenshot:
RIP: 0010:pci_assign_unassigned_root_bus_resources+0x1c2/0x1d0

Could you test latest upstream kernel? Verify that you can select older kernel from bootloader if new one panics too.
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Revision history for this message
Martin Měřinský (mermar) wrote :

Thank you for your effort.

I installed 5.7.0-050700rc5 and it boots OK.

sudo dpkg -i linux-headers-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb
sudo dpkg -i linux-headers-5.7.0-050700rc5_5.7.0-050700rc5.202005101931_all.deb
sudo dpkg -i linux-modules-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb
sudo dpkg -i linux-image-unsigned-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb
sudo update-grub

I'm attaching result of journalctl -b.

Jouni Mettala (jouni-mettala)
tags: added: kernel-fixed-upstream
Revision history for this message
Jouni Mettala (jouni-mettala) wrote :

This panic is happening early in boot. No modules are linked in. We can assume it is not usb subsystem bug. This is from dmesg.
"pci 0000:00:00.0:[Firmware Bug]: reg 0x1c: invalid BAR (can't size)".

It is perhaps possible to boot your usb with some boot paramater like pci=nocrs https://wiki.ubuntu.com/Kernel/KernelBootParameters

If you happen to upgrade to focal via update-manager or do-release upgrade it would be good to know does kernel still panic.

Revision history for this message
Martin Měřinský (mermar) wrote :

ubuntu-20.10-beta-desktop-amd64.iso does not boot as well. Ends with the same kernel panic.

Revision history for this message
Martin Měřinský (mermar) wrote :

Adding boot parameter pci=nocrs makes no difference.

> If you happen to upgrade to focal via update-manager or do-release upgrade it would be good to know does kernel still panic.

I'm staying with Ubuntu 19.10, I did not upgrade, I cannot risk unbootable computer.

Revision history for this message
Martin Měřinský (mermar) wrote :

While it is something with PCI(?) I tried to remove both PCI cards:
* Tuner ASUS MyCinema P7131 Hybrid Analog/DVB TV card
* USB 3.1 adapter Kouwell UB-135-2
But the same kernel panic occurred.

Revision history for this message
Martin Měřinský (mermar) wrote :

I downloaded files from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/amd64/
and installed 5.9.0

sudo dpkg -i linux-headers-5.9.0-050900_5.9.0-050900.202010112230_all.deb
sudo dpkg -i linux-headers-5.9.0-050900-generic_5.9.0-050900.202010112230_amd64.deb
sudo dpkg -i linux-modules-5.9.0-050900-generic_5.9.0-050900.202010112230_amd64.deb
sudo dpkg -i linux-image-unsigned-5.9.0-050900-generic_5.9.0-050900.202010112230_amd64.deb
sudo update-grub

which works:
uname -a
Linux sevaka 5.9.0-050900-generic #202010112230 SMP Sun Oct 11 22:34:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

So the problem is in Ubuntu 20.10 beta install image itself?

Martin Měřinský (mermar)
summary: - Ubuntu 20.04 install image does not boot
+ Ubuntu 20.10 install image does not boot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.