still present in trusty! /boot in sda1 and / is on LVM
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/828731
Title:
kdump functionality not working as expected when /boot is a
same bug than before in trusty.
/boot on sde5
and / is on sdd2
can you release a fix please. I need to evaluate my kernel panic FAST!
thank you
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
Nagaraj, I see no reason to think your problem is related to this bug.
This bug is specifically about a separate /boot partition, which you do
not have, and your symptoms don’t match either. You should file a new
report.
--
You received this bug notification because you are a member of Kernel
First of all, doing ponytail on a 3 year old bug is not going to bring
you much attention.
Especially since this bug pertains to a mechanism that is now only used
on Precise. It is unfortunate though that the server guide is
misleading on how to configure kernel dump. I would suggest to open a
I have a setup with Ubuntu 14.04 LTS server. The /boot is not on a
separate partition. I followed the kdump setup as mentioned in
https://help.ubuntu.com/14.04/serverguide/kernel-crash-dump.html
After triggering the kdump, system panics but system never
comeup/reboot. It get stuck at the call
Is this really fixed on Ububuntu 14.04 LTS?
I've just tested triggering a crash dump and it didn't work. A Google
search pointed me to this bug. When I see /boot on a separate partition,
I just realized it is the damn case! Others like dbgsym kernel from
ddeb, kdump-tools, linux-crashdump all
6 matches
Mail list logo
