--- 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.lau
--- 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 Kerne
--- 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 Kerne
/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
--- 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=devic
--- 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 unti
--- 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 a
--- 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 Kerne
--- 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
--- 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
+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 System
--- 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/V
--- 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 o
13 matches
Mail list logo