Kernel panic in 5.4.0-21-generic when try to launch on system with 256 MB RAM

Bug #1872535 reported by Rinaldus
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have VPS with 256 MB RAM. I had Ubuntu 19.10 there, but decided to upgrade to 20.04. But right after upgrade I can't load it, there's kernel panic. Old kernel from Ubuntu 19.10 loads successfully. I have Ubuntu 20.04 installed in my VirtualBox and I tried to decrease RAM to 256 MB. It gives the same kernel panic. Here's screenshot: https://i.imgur.com/dBRwBAi.png
Will Ubuntu 20.04 never work on 256 MB budget VPS anymore or is it bug?

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 1872535

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
Revision history for this message
Rinaldus (pitersv) wrote :

It's impossible to give more logs, than I have already given. I can't load with 256 MB. If I increase RAM of my virtual machine and load the system, logs will be different. I would like the human read this bug, not stupid bot.

Rinaldus (pitersv)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Andrea Righi (arighi) wrote :

I've just tried to provision a new VM (via uvtools) using the latest focal kernel (5.4.0-25-generic) and it seems to boot fine with 256MB of memory. However, I haven't tried to do the release upgrade from 19.10 (I'll test this later).

If you have a way to boot into the previous kernel you can try to install the linux-kvm kernel and boot with this one, it has smaller memory footprint and it should be able to boot fine. Then, once it's booted you probably need also a swap file / swap partition to be able to do your normal activities without triggering the oom killer.

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.