Upgrade to 19.04 from 18.10 doesnt boot

Bug #1825698 reported by adithya jayaprakash
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upgrade completes but shows error message that linux kernel 5.0.0-13 may not be in working state.
After completion of upgrade Ubuntu doesn't boot at all.. Just shows few blank screens and hangs.
I reverted back to my old kernel 4.18.0-17 that was in Ubuntu 18.10 and it booted fine..
Then I dleleted the new 5.0.0-13 kernel and headers.
Now Ubuntu 19.04 boots fine with old kernel.

I also tried reinstalling kernel 5.0.0-13. But faced same issue again. So again I went back to old kernel.
I noticed others too have been facing this problem.
KINDLY LOOK INTO THE BUG AND LET US KNOW THE SOLUTION

Tags: cosmic
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 1825698

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: cosmic
Revision history for this message
adithya jayaprakash (adithyajp) wrote :

Sorry I cannot add the log files now since i do not have the said kernel. I am running Ubuntu 19.04 now with 4.18.0-17.
But I can tell you what the error message was.

Actual results:
* upgrade process ended with warning message:

    Could not install 'linux-image-5.0.0-13-generic'
    The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it.

    triggers looping, abandoned

Workaround:

  Run recommended `dpkg --configure -a` before actual reboot.

I could not run the recommended workaround.. So i deleted the 5.0.0-13 and booted Ubuntu 19.04 with 4.18.0-17.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Terry Rudd (terrykrudd) wrote :

This looks to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420. Can you please confirm?

Revision history for this message
adithya jayaprakash (adithyajp) wrote :

Yes.. It looks like it is same problem.
As the bug 1825420 referred to virtual ubuntu, I thought this requires separate reporting.
You can consider this duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420 if it doesnt matter whether it is in virtual os or ubuntu

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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