kernel-packages team mailing list archive

[Louis Bouchard <louis.bouchard@xxxxxxxxxxxxx>]

Hello,

It is becoming unclear to me if the cio_ignore needs to be tied to a
bigger crashkernel value or not. I am preparing an update to kdump-tools
which will set the crashkernel value upon install. Right now, I'm
setting it to 196M for LPAR and 128M for zVM.

What should be the default values for LPAR and zVM ?

I will add a separate change to take the cio_ignore into account.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1570775

Title:
  makekdump should re-exec with cio_ignore on s390x

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

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19

  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:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+subscriptions