** Tags added: petest-459
--
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/1564475
Title:
128M is not enough for kdump on s390 LPARs
Status in Ubuntu on IBM z Systems:
Fix Releas
I see, thanks a lot!.
Opened
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1570775 to
generate and use cio_ignore in kdump.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/b
s390-tools zipl generation bug report
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1570645
--
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/1564475
Title:
128M is not e
@thorsten
If I understand correctly cio_ignore command needs to be on the running
instance that is about to crash, rather than on the re-exec kernel. Thus
it needs to be computed and added to e.g. /etc/zipl.conf. At the moment
we do not generate/update /etc/zipl.conf in an automated way, but the
m
Server guide bug number
https://bugs.launchpad.net/serverguide/+bug/1570644
--
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/1564475
Title:
128M is not enough for kdump on s390 LPAR
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1604
--
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/1564475
Title:
128M is not enough for kdump on s390
** Changed in: ubuntu-z-systems
Status: New => Fix Released
** Changed in: makedumpfile (Ubuntu Xenial)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launch
This bug was fixed in the package s390-tools - 1.34.0-0ubuntu5
---
s390-tools (1.34.0-0ubuntu5) xenial; urgency=medium
* Add condition to cpacfstatsd.service to only start on LPARs (which may
still fail, if LPAR is not configured with the right counters).
* Add a system group
This bug was fixed in the package zipl-installer - 0.0.33ubuntu3
---
zipl-installer (0.0.33ubuntu3) xenial; urgency=medium
* Reluctantly Bump crashkernel to 196M, as otherwise 128M is not enough
by default to collect a kdump on any LPAR, defeating the intended
purpose in the
** Also affects: zipl-installer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Xenial)
Importance: High => Low
** Changed in: s390-tools (Ubuntu Xenial)
Importance: Un
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Also affects: makedumpfile (Ubuntu Xenial)
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Confirmed
--
You received this bug notification because you a
** Changed in: ubuntu-z-systems
Importance: Undecided => Critical
--
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/1564475
Title:
128M is not enough for kdump on s390 LPARs
Stat
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
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/1564475
Title:
128M is not enough for kdump on s390 LP
On 1 April 2016 at 12:22, Louis Bouchard wrote:
> If there is a way to determine if we're on a zVM or Lpar, I could adapt
> kdump-config to add the appropriate crashkernel=value pair in
> /etc/zipl.conf and re-run zipl upon installation of kdump-tools, which
> is required in order to capture a dum
If there is a way to determine if we're on a zVM or Lpar, I could adapt
kdump-config to add the appropriate crashkernel=value pair in
/etc/zipl.conf and re-run zipl upon installation of kdump-tools, which
is required in order to capture a dump.
--
You received this bug notification because you ar
"Ok, if we go with the 128M default our current assumption is that on
all LPARs kdump for Ubuntu will fail." -> well, that doesn't sound good
either, cause then essentially we take away 128M of RAM away without
actually providing anything to the LPAR installations =(
--
You received this bug noti
***WARNING***
KDUMP_CMDLINE_APPEND is used to add parameters to the command used by
kexec to reboot when the system crashes. Adding crashkernel= there is
useless and will most likely be ignored.
The crashkernel= parameter has to be made available on the system when
it first boots so having it in
128MB is just a sensible default enabled by default everywhere, if in
your case you need more do adjust it accordingly in /etc/zipl.conf and
execute `sudo zipl` and then reboot.
There is no dynamic sizing / computation of zipl.conf and/or crashkernel
paramemter on Ubuntu, and on all architectures
I do not want to increase it beyond 128MB by default, as this amount of
memory is reserved by default on all installations big or small. And
there will always be newer kernel (that reserves more memory) or more
devices that require higher values. Adjusting kernel args in
/etc/zipl.conf is well-know
** Package changed: ubuntu => makedumpfile (Ubuntu)
--
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/1564475
Title:
128M is not enough for kdump on s390 LPARs
Status in makedumpfil
20 matches
Mail list logo
