On Sun, 2012-06-10 at 00:44 -0700, John Wright wrote:
On Sat, Jun 02, 2012 at 07:02:11PM +0100, Ben Hutchings wrote:
The help text for this option is:
Generate crash dump after being started by kexec.
This should be normally only set in special crash dump kernels
which are loaded in
On Sun, Jun 10, 2012 at 03:02:30PM +0100, Ben Hutchings wrote:
On Sun, 2012-06-10 at 00:44 -0700, John Wright wrote:
On Sat, Jun 02, 2012 at 07:02:11PM +0100, Ben Hutchings wrote:
The help text for this option is:
Generate crash dump after being started by kexec.
This should be
Thanks a lot for the extra information. I'm convinced and I'll enable
this for the next upload.
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
signature.asc
Description: This is a digitally signed message part
On Mon, Jun 11, 2012 at 12:55:19AM +0100, Ben Hutchings wrote:
Thanks a lot for the extra information. I'm convinced and I'll enable
this for the next upload.
Wonderful, thank you! (And sorry I didn't include that information from
the beginning.)
--
John Wright j...@debian.org
The help text for this option is:
Generate crash dump after being started by kexec.
This should be normally only set in special crash dump kernels
which are loaded in the main kernel with kexec-tools into
a specially reserved region and then later executed after
a crash by kdump/kexec. ...
Are
Seconded. Also reported in [1]. The status of this issue is also the
same in Wheezy's linux-image-3.0.0-1-amd64 and experimental's
linux-image-3.1.0-rc7-amd64_3.1.0~rc7-1~experimental.1_amd64.deb
I haven't been able to figure out if enabling CONFIG_CRASH_DUMP adds
any overhead at all. Are there
Source: linux-2.6
Severity: wishlist
Tags: patch
Now that we ship debug info, missing CONFIG_CRASH_DUMP=y is the only
thing preventing users of stock Debian kernels from easily taking crash
dumps with makedumpfile/kdump-tools and analyzing them with the crash
utility.
I have built a kernel with
7 matches
Mail list logo
