I had two up-to-date Azure instances (16.04 and 18.04) where Linux-
crashdump was installed. Both failed, with the following being shown at
the end of the serial console:
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ 18
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764246
Title:
kdump kernel panics on Bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
OK, so it seems it's really the minimum of reserved memory kernel needs in
Bionic that is affecting
the success of kdump here.
Thanks for the report Gaëtan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
By increasing the size reserved to 256MB it's working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764246
Title:
kdump kernel panics on Bionic
To manage notifications about this bug go to:
https
I got the same behavior on Xenial with kernel 4.15.0-43-generic.
[4.598980] [ pid ] uid tgid total_vm rss pgtables_bytes swapents
oom_score_adj name
[4.601946] Kernel panic - not syncing: Out of memory and no killable
processes...
[4.601946]
[4.605054] CPU: 0 PID: 1 Comm
The OOM seems to be happening during initrd decompression. That has been
observed before and also in Cosmic. I want to reduce the initrd
footprint in case framebuffer drivers are included, which might happen
when cryptsetup or plymouth are installed.
On the other hand, just incrementing the reserv
I tried here with a Bionic VM (kernel 4.15.0-34) and kdump worked fine, using
the default
config (128M reserved for the crash kernel).
I'll try to mimic the HW of Daniel's guest and perhaps the kernel
version, although it's super old and seems not available anymore.
@Paul, perhaps worth for you
A console screen when I triggered.
** Attachment added: "trigger.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764246/+attachment/5193476/+files/trigger.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
kdump is not still working on 18.04.
Kernel : 4.15.0-34-generic
linux-crashdump : 4.15.0.34.36
ubuntu@u-VM-07:~$ cat /var/crash/kexec_cmd
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic
root=UUID=51adaf62-9023-4c45-bf94-889906e3d2d2 ro net.ifnames=0 biosdevname=0
nr_cp
i also see the kdump cannot work on 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764246
Title:
kdump kernel panics on Bionic
To manage notifications about this bug go to:
https://bugs.launc
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
11 matches
Mail list logo
