[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-08-05 04:11 EDT---
Thanks for promoting it to xenial-updates. Successfully verfied and closed.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-08-04 13:24 EDT---
makedumpfile & kdump from xenial-proposed as of today are version 
1.5.9-5ubuntu0.1 and are fixing that problem. Please promote it to 
xenial-updates.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-26 10:29 EDT---
makedumpfile & kdump from xenial-proposed as of today are version 
1.5.9-5ubuntu0.1 and are fixing that problem. Please promote it to 
xenial-updates.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

/etc/kernel/postinst.d/kdump-tools $(uname -r)

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From peter.oberparlei...@de.ibm.com 2016-07-14 08:43 EDT---
As an alternate solution, try this:

1) Modify /usr/share/initramfs-tools/scripts/init-top/udev

Replace line
udevadm trigger --action=add
with
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add

2) Modify /etc/default/kdump-tools

Replace existing KDUMP_CMDLINE_APPEND= lines with
KDUMP_CMDLINE_APPEND="cio_ignore=all,!condev"

3) Rebuild the kdump initramfs

/etc/kernel/postinst.d/kdump-tools

4) Check if kdump works

echo c > /proc/sysrq-trigger

Explanation:

- Ubuntu 16.04 uses zdev to configure z Systems specific devices
- zdev also handles cio_ignore configuration via a Udev rule that triggers
when the CCW bus is registered (see /etc/udev/rules.d/41-cio-ignore.rules)
- Because of the way that Ubuntu's initramfs tools trigger coldplug of
Uevents, the Uevent for the CCW bus is not generated and the cio_ignore
rule is not triggered. I consider this a bug in Ubuntu's udev package
because systemd provides a corresponding coldplug unit file (see
/lib/systemd/system/systemd-udev-trigger.service) that performs the steps
as proposed in 1)
- With cio_ignore handling covered by the udev rule, KDUMP can use the
command line in 2) to blacklist all devices except the console. The
latter needs to be excluded as the kernel would otherwise not boot on
a z/VM guest

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-13 11:52 EDT---
Hmm, just one hour ago the s390-tools maintainer submitted a patch for the 
manpage of cio_ignore  to clarify that the example command "cio_ignore -u -k" 
modifies(!) the current cio_ignore blacklist.
It was not obvious until today, that it really modifies something!

What does it mean:
1. Under z/VM, if somebody had invoked "cio_ignore -u -k" via installation of 
kdump-tools, performs no reboot AND attaches additional CCW devices, they will 
not show up in the channel subsystem (e.g. via lscss) until they are 
unblacklisted (e.g. via cio_ignore -r )
2. Similar for LPAR, if you define additional CCW devices via dynamic I/O 
configuration change in HCD.
3. If someone performs a "cio_ignore -p" after invoking "cio_ignore -u -k" 
(e.g. via installation of kdump-tools), the change becomes effective and 
visible also for existing unused devices, and all unused CCW devices are 
blacklisted and no more visible.
4. After a reboot, the cio_ignore blacklist is concurrent to what has been 
specified via kernel parameter line. (Which means: Everything is fine again.)

My recommendation:
1. Go ahead with the actual implementation as of today, since it is worth to 
have a kdump when required, even with the above misbehaviour (which can be 
worked around).
2. When a new version of cio_ignore (within s390-tools) is available, you 
should pick up this new s390-tools version and also fix the postinst script in 
kdump-tools package picking by adjusting the cio_ignore parameters.

We will open a new bug to fix the postinst script again, when an updated
version of s390-tools is available.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-13 05:53 EDT---
Yep, that works as intended.
And thanks for also correcting maxcpus=1 to nr_cpus=1.
You may go ahead with that and SRU version 1.5.9-5ubuntu1 of both packages to 
xenial.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-12 09:26 EDT---
Version 1.5.9-5 does not contain the required fix. Still waiting for 1.5.9-7 in 
xenial updates.
@Canonical: When is this available in xenial updates?

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-01 05:48 EDT---
As of today, I can update to the following levels:
ii  kdump-tools1:1.5.9-5
ii  kexec-tools1:2.0.10-1ubuntu2
ii  makedumpfile   1:1.5.9-5

Version 1.5.9-5 does not contain the required fix. Still waiting for
1.5.9-7 in xenial updates.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-06-28 12:13 EDT---
(In reply to comment #12)
> This bug was fixed in the package makedumpfile - 1:1.5.9-7
>
> ---
> makedumpfile (1:1.5.9-7) sid; urgency=medium
>
> * [d/rules] Lower kexec-tools dependency to -2
> The ubuntu merge will happen on an 1:2.0.10-2 version so it cannot
> depends on -3.
>
> -- Louis Bouchard   Tue, 31 May 2016 14:36:07
> +0200

I can not install
makedumpfile_1.5.9-7
kexec-tools_2.0.10-2
- not even via xenial-proposed?

Thus I picked makedumpfile_1.6.0_1 and kexec-tools_2.0.10-2 (from yaketty??) 
manually and it works as expected.
/etc/default/kdump-tools has KDUMP_CMDLINE_APPEND populated with the values as 
intended, so I treat this is fixed in a newer version. When a fixed version is 
available for _xenial_ as well, we can close this bug.

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

+APPEND=$(/sbin/cio_ignore -u -k)

-- 
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:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-05-10 04:13 EDT---
Hi Louis,

it's easier than expected:
If you kexec with cio_ignore as proposed above, 128M will be enough for both 
z/VM and LPAR. And to ease it up, you can use that cio_ignore mechanism in 
/etc/default/kdump-tools for z/VM and LPAR.

-- 
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-05-03 07:28 EDT---
On an LPAR with 8458 (!!) ccw devices (only 11 of them in use) I set 
crashkernel with various values:
256M : no dump created
288M : oom killer killed some processes, dump was created, but system did not 
come up
320M : no oom killer, dump properly created
Then I invoked cio_ignore -u -k and added these values to KDUMP_CMD_APPEND in 
/etc/default/kdump_tools. Kdump worked fine, even with crashkernel=128M

IMO the best thing is to set this dynamically in /etc/default/kdump_tools by 
the following suggested patch:
--- /etc/default/kdump-tools.orig   2016-04-21 15:11:57.0 +0200
+++ /etc/default/kdump-tools2016-05-03 13:17:38.862816261 +0200
@@ -63,7 +63,8 @@
# for the kdump kernel.  If unset, it defaults to "irqpoll maxcpus=1 nousb"
#KDUMP_KEXEC_ARGS=""
#KDUMP_CMDLINE=""
-#KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"
+APPEND=
+KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
$APPEND"

# ---
# Architecture specific Overrides:

The cmdline during kdump is set properly, the values from cio_ignore are
reflected.

-- 
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp