Public bug reported:
As part of the makedumpfile autopkgtest, a test is done to make sure one can
dump the kernel.
The test executes
$ kdump-config status
and expects to find that it is ready to kdump, however it is not.
The check fails at:
$ cat /sys/kernel/kexec_crash_loaded
Previously it was 1, but now it is 0.
Is this intentional? Do we need to change something in makedumpfile? Or
is something missing in the kernel?
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-7-generic 4.18.0-7.8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: xnox 9240 F.... pulseaudio
/dev/snd/controlC1: xnox 9240 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 3 17:07:41 2018
HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c
InstallationDate: Installed on 2012-01-12 (2425 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic
root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M
crashkernel=384M-:128M vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.18.0-7-generic N/A
linux-backports-modules-4.18.0-7-generic N/A
linux-firmware 1.175
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-06-25 (69 days ago)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F18g
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic package-from-proposed uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790513
Title:
kdump-config status - not ready to kdump with v4.18 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790513/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
