4.18.0-14-generic unbootable on Toshiba

Bug #1815258 reported by shanen (Shannon Jacobs) on 2019-02-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After the update for the 4.18.0-14-generic kernel the machine freezes on booting. Machine still books under the 0-13 kernel. Booting in Recovery Mode seems go normally to the Recovery Menu. At that point it reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That is repeated with another OK. Then it says "Starting Daily apt upgrade and clean activities" followed by an OK. Next is a second attempt for the same "apt upgrade" and it appears to be frozen. No OK ever received and no further progress towards booting.

Not sure how additional details can be acquired.

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 1815258

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
description: updated
description: updated
Brad Figg (brad-figg) on 2019-02-09
Changed in linux (Ubuntu):
status: Incomplete → Triaged

I am unable to run that command under the afflicted kernel because the machine cannot boot under that kernel.

The robotic message tells me to change the status to confirmed after adding the previous comment, but the instructions there say that the confirmed status is supposed to be done by someone else.

By the way, my current theory (based on weak understanding) is that there might be some logs of the boot failures somewhere else, but I do not know where they are. Under Linux I can only boot under the 0-13 kernel, and the problem appeared with the 0-14 kernel.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
Brad Figg (brad-figg) on 2019-02-09
tags: added: bjf-tracking

Okay, after the latest update (from the 0-13 kernel) it now seems to be booting normally. I hope that means the problem has been corrected and this bug can be closed. Perhaps some kind of regression bug?

If anyone over there wants me to collect any additional information about what was going on, please let me know what you need and how to collect it. Minimum might be some confirmation if you have a hypothesis of what got broken and want to make sure you squashed the bug.

P.S. I'd be more enthusiastic if I had a few bucks on the table (for example, via that imaginary charity share brokerage). I don't really feel that I have much skin in the game beyond the fuzzy philosophy that freedom involves choice and Linux is one of the choices I should understand and consider.

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

Other bug subscribers