← Back to team overview

kernel-packages team mailing list archive

[Bug 1570775] Re: makekdump should re-exec with cio_ignore on s390x



Before commiting this into the new kdump-tools, let me confirm with you

The current use has the following kexec command (from kdump-config show)

kexec command:
  /sbin/kexec -p --command-line="root=/dev/mapper/vg_ubuntu-root BOOT_IMAGE=0 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

Your suggestion is to have the following kexec command :

kexec command:
  /sbin/kexec -p --command-line="root=/dev/mapper/vg_ubuntu-root BOOT_IMAGE=0 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service cio_ignore=all,!0009,!0200,!0600-0602" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

I have implemented this by adding the cio_ignore statement (from
cio_ignore -k -u) to the KDUMP_CMDLINE_APPEND statement in /etc/default
/kdump-tools file if installed on s390.

This differs from the statement in https://wiki.ubuntu.com/S390X that
says that it should be added to /etc/zipl.conf and, hence applied to any
running kernel, not only the one that is kexec'd.



You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.

  makekdump should re-exec with cio_ignore on s390x

Status in Ubuntu on IBM z Systems:
Status in makedumpfile package in Ubuntu:

Bug description:
  As per

  We should re-exec with cio_ignore lines. As per report there, it
  should result in lowered required crashdump setting.

  Hypothetically, one should be able to test this imperially by lowering
  crashdump memory settings until kdump does not succeed anymore. And
  then generated and append `cio_ignore -k -u` to the
  KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a
  lower memory usage.

  Once this is developed / verified / tested, we should probably SRU
  this back to xenial.

To manage notifications about this bug go to: