Closing as per the latest posts.
** Changed in: linux (Ubuntu Oneiric)
Status: Confirmed = Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I started getting proper kernel crash dumps last week. Congratulations
and thanks to whoever made that work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec
I ran through the steps on an identical machine and realized that
update-initramfs was leaving untouched the kernel I was using
(3.0.0-15-generic). Went back to the original machine, switched to a
different kernel (3.0.0-12-server), and can reliably generate a crash
file there. Other kernels
@brandon
LP bug 785425 and LP bug 828731have fixed most of the issues with kdump.
Changes are scheduled to be retrofitted from Precise to the older
versions.
The only thing I have found while testing all this was when the system
has = 2Gb. This means that the crashkernel= clause will limit the
Technically, the 64MB-too-small bug is #785394, but whatever it takes to
get this done!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec Properly
To manage
@louis
I'm still unable to trigger a crashdump, and my crash screen looks
identical to that of the original bug reporter's.
I believe there's enough mem for the crashdump:
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.0.0-15-generic
root=/dev/mapper/nfcm7-root ro
On oneiric I have the same problem, even after doing the same steps as
Sudhakar. On a VM w/VMware fusion I can occasionally get a crash dump
(one in three or four times), but on a native hardware install I haven't
gotten a crash dump yet.
--
You received this bug notification because you are a
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec Properly
To manage notifications about this bug go to:
Bah, assigning to linux-crashdump forces it to linux-meta which is not
what I wanted. Moving back to linux for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing
per 20110916 release meeting: not oneiric release critical, removing
tracking tag.
** Tags removed: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec Properly
To manage notifications about this bug go to:
Yep, still doesn't work in Oneiric. The crash kernel can't boot due to
insufficient memory, kexec-tools still pulls in a dynamically-linked
makedumpfile(8)... has *anyone* worked on this at all?
** Changed in: linux (Ubuntu Oneiric)
Status: Incomplete = Confirmed
--
You received this bug
Hi Joe,
This has been nominated against Oneiric but it does not appear to have
been tested with Oneiric yet. Care to test and confirm this is still an
issue? Thanks.
** Changed in: linux (Ubuntu Oneiric)
Status: Confirmed = Incomplete
--
You received this bug notification because you
@ Daniel Richard G.
I performed following steps to resolve the crashdump hang issue.
[Issue 1]default crashkernel=...
Changed the crashkernel to use 128M instead of 64M in /etc/grub.d/10_linux.
dmesg displays 128M reservation as expected.
[Issue 2] makedumpfile throws error while loading
@Sudhakar,
I believe you'll need to regenerate the initrd with e.g. update-
initramfs -k all -u, so that the new makedumpfile binary is copied into
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This will be the subject of an upcoming bug when I'm back from vacation,
but I have been able to highlight a clear problem : when /boot is on a
separate partition, which is done by default when LVM is used at install
time, then crashdump will fail, since the /boot is empty.
A workaround is
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec Properly
To manage notifications about this bug go to:
I'm trying to get crash dumps working, and there's a number of
showstoppers going on (in current Natty).
First, the default crashkernel=... memory allocation for systems with up
to 2GB RAM isn't even enough for the Ubuntu kernel: bug #785394
Second, the linux-crashdump package depends on
** Changed in: linux-meta (Ubuntu)
Importance: Undecided = High
** Also affects: linux-meta (Ubuntu Oneiric)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Concerning:
https://bugs.launchpad.net/ubuntu/+source/linux-
meta/+bug/710733/+attachment/1826111/+files/LucidCrashdumpConsole.jpg
Helps if I actually look at the code:
http://lxr.linux.no/linux+v2.6.37.2/drivers/tty/sysrq.c#L128
128static void sysrq_handle_crash(int key)
129{
130
I performed some more testing today on a Natty desktop. I'm able to
generate a crash dump. However, I've been getting intermittent
failures. Like you mention, changing maxsize doesn't seem to help. It
was just a coincidence that crash dump worked for the first time, after
I increased maxsize.
For the life of me I haven't been able to get a crash dump at all.
After I echo c to sysrq-trigger the system locks up but never reboots.
Additionally, after I manually reboot it apport tells me nothing and
there is no crash file in /var/crash.
** Changed in: linux-meta (Ubuntu)
Status:
Bug 599601 is likely a duplicate of this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec Properly
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Actually maxsize is in /etc/default/apport is not used and has been
removed from that file. I've been unable to generate a crash report at
all using Natty.
** Changed in: linux-meta (Ubuntu)
Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)
--
You received this bug
Interesting. So maybe there is an issue that causes intermittent
failures on natty. I was able to get it to work a couple of times after
increasing maxsize. I'll try setting maxsize back to what it was and
see if I can get a crash report. I'm still unable to get a crash
report on Lucid
@Brian
Thanks for the suggestion. I enabled apport on my 10.04 server. I
forced the crash. The server seemed to reboot extremely fast. However,
there was not file written to /var/crash. If I reboot and try perform
the crash again, I get the same results.
I tried forcing a crash again after
** Attachment added: LucidCrashdumpConsole.jpg
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/710733/+attachment/1826111/+files/LucidCrashdumpConsole.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I continued testing with my netbook running Natty. I doubled the size
of maxsize=209715200 to maxsize=419430400. This allowed the dump file
to be generated! Strange because this size of the dump file is ~190Mb,
so the maxsize of 200Mb should have been enough. I'll continue to play
with it to
BTW, I should have been clearer. I doubled the size of maxsize in the
/etc/default/apport file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710733
Title:
LKCD Not Executing kexec Properly
--
I haven't tried to recreate this yet myself but looking at the bug it
occurred to me that apport is disabled for all those releases. Could
you make sure apport is on by editing /etc/default/apport? Thanks in
advance.
** Changed in: linux-meta (Ubuntu)
Status: New = Incomplete
--
You
** Attachment added: 2010-12-22 16.47.09.jpg
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/710733/+attachment/1819852/+files/2010-12-22%2016.47.09.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: altsysrq_t_output.txt
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/710733/+attachment/1819853/+files/altsysrq_t_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
32 matches
Mail list logo
