The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: grub (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd just like to report in that I couldn't get it to work, it only did
after raising the limit to 256M on a server with 256GB of memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
** No longer affects: grub (Ubuntu Raring)
** No longer affects: grub (Ubuntu Quantal)
** No longer affects: grub (Ubuntu Saucy)
** Changed in: grub (Ubuntu Precise)
Assignee: Chris J Arges (arges) = (unassigned)
** Changed in: grub (Ubuntu Precise)
Status: In Progress = Confirmed
Please keep in mind the 128Mb is some kind of catchall for defined when
memory sizes did not go much higher than 16Gb. I will inquire in the ML
that covers makedumpfile to see if there is a way to come up with an
estimate of the required memory and will report back.
In the meantime, I don't see
RFE
Let there be a separate tool/command that would provide an estimate of
the memory required for the localhost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded
I have at least one example where I had to it bumped to above 128M (I picked
256M out of my head).
Summary of hardware, 16 total cores, 24G ram, 37 drives, mix of xfs/nfs, drive
size mostly 2 TBs.
I'll see if we can't get some internal examples.
--
You received this bug notification because
Bryan: Are you saying 256MB was needed in order for the crash kernel to
boot, that 128MB was not enough?
(I'm not sure that there is any advantage to reserving more memory than
needed, aside from the kernel one day growing to need 129MB)
--
You received this bug notification because you are a
128MB didn't work
256MB did
Nothing else was tested on this machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded crashkernel=... memory reservation in
Ah, okay, that's an issue. Not only do we not have an easy way of
measuring how much memory a kernel needs to boot, we don't know how that
requirement varies depending on the system configuration...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: grub (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: grub (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu
btw, this bug will need to be re-targetted to kexec-tools; the
crashkernel= definition has been moved to kexec-tools recently :
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/kexec-tools
/trusty-proposed/revision/63
kexec-tools (1:2.0.3-4ubuntu2) trusty; urgency=low
2
3 * Add
== Test on a VM with 384Mb of memory ==
1)Original setup - crashkernel=384M-2G:64M,2G-:128M
ubuntu@SaucyS:~$ free
total used free sharedbuffers cached
Mem:306572 144412 162160 0 21900 73716
-/+ buffers/cache: 48796
** Also affects: kexec-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kexec-tools (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: kexec-tools (Ubuntu)
Status: New
** Branch linked: lp:ubuntu/trusty-proposed/kexec-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
is
Pushed changes into kexec-tools trusty. Let's test these changes first,
then modify the grub packages in earlier releases via SRU if trusty is
working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package kexec-tools - 1:2.0.3-4ubuntu3
---
kexec-tools (1:2.0.3-4ubuntu3) trusty; urgency=low
* Increase memory parameter crashkernel command line to 128M to avoid
OOM kernel panic. (LP: #785394)
-- Chris J Arges chris.j.ar...@ubuntu.com Wed, 18 Dec
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu
** Also affects: grub (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: kexec-tools (Ubuntu)
** No longer affects: kexec-tools (Ubuntu Precise)
** No longer affects: kexec-tools (Ubuntu Quantal)
** No longer affects: kexec-tools (Ubuntu Raring)
** No longer affects:
ubuntu p/q/r/s/t versions of the source package show the same options:
./trusty/grub-0.97/debian/update-grub:
extra_opts=$extra_opts crashkernel=384M-2G:64M,2G-:128M
./raring/grub-0.97/debian/update-grub:
extra_opts=$extra_opts
I systematically change the setting on all my VMs to 128M as I have had
repeated failure with 64M. I think that the default should be raised to
128Mb which is the default on Debian anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Agreed. It's not clear that there is *any* standard Ubuntu kernel
configuration that can boot in 64MB. And having that as a default is
worse than useless, because the crash-kernel's OOM prevents the system
from recovering automatically after a kernel crash.
--
You received this bug notification
@Daniel
I'm wrong, not fixed in 13.04+
I ran some tests:
@Chiluk first up vm images do only need 64 mb reserved:
Trusty 512 MB (m1.tiny) image on OpenStack: allocted 64 MB of ram for
crashdump and it worked. (dump size of 23 mb)
Desktop images fail
Trusty 2047 MB (Vagrant/Virtualbox desktop
Yeah looks like the minimum amount of ram required to complete the
writing of a dump in the case of a generic-image and default initrd is
roughly 109-110M with the 3.8 kernel (I just tested it).
My $.02 on this matter is that the default values should work for
default installs. Right now that is
Bryan: Could you elaborate on how this issue appears to be fixed in
13.04? Was the memory reservation increased to 128MB, or is the kernel
now capable of booting in 64MB? Given the lack of any updates here, I'm
doubtful that any progress has been made at all.
Dave: Have you tried crash-booting a
This appears to be fixed in 13.04+. Any chance we can get a fix
backported to 12.04?
If not, can we increase the memory by default?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
@apw
After our meeting at UDS-P, you suggested to change the following in
/etc/initramfs/initramfs.conf :
#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Daniel, I have talked with Andy and Colin over the matter. I will be
working with them on this bug as well as on #785425 and #828731 in order
to get the kdump functionality completely functional.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Louis, thank you; that will be very much appreciated.
You may also want to look at bug #885071, against linux-crashdump, which
consolidates some of these issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still present in Oneiric. The 3.0.0-12-generic kernel, like
its predecessors, fails to crash dump with 64M and succeeds with 128M.
The failure mode with 64M is a bit less clear, however---something about
a bad IRQ.
** Attachment added: Boot and crash with 64M crashkernel reservation
Note that even with enough memory reserved, a crash dump is still not
produced due to bug #785425.
(Why won't Launchpad allow me to upload more than one attachment at a
time?)
** Attachment added: Boot and crash with 128M crashkernel reservation (works,
almost)
Hmm. 128MiB seems like an awful lot to reserve, particularly towards
the lower end of that memory range. It would be nice to not need quite
so much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like it's OOMing while unpacking the initramfs. What does this
output?
ls -l /boot/initrd.img-$(uname -r)
zcat /boot/initrd.img-$(uname -r) | wc -c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: kexec-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded crashkernel=... memory reservation in
It seems that the default is to use the current kernel and initrd for
the kexec kernel. This is going to consume some 36MB of this 64MB
window, another 4.5 for the kernel itself and we down to close to 20MB
of memory left to boot in, which seems to be asking a lot.
It seems we could be a little
It is possible to change the initramfs used for kexec relatively easy,
see kdump.init.d in the source. We could therefore consider building an
initrd with MODULES=dep, for my machine here that drops the initrd by
10MB compressed and nearly 30MB uncompressed:
$ zcat
Hello gentlemen,
# ls -l /boot/initrd.img-2.6.38-8-generic
-rw-r--r-- 1 root root 14389163 2011-05-19 17:29
/boot/initrd.img-2.6.38-8-generic
# zcat /boot/initrd.img-2.6.38-8-generic | wc -c
32537600
I use a generic (rather than targeted) initrd because the system is
installed using an imaging
** Attachment added: Kernel log: cold boot + crash + crashkernel boot +
out-of-memory error
https://bugs.launchpad.net/bugs/785394/+attachment/2135696/+files/crashkernel-oom.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
38 matches
Mail list logo
