Bug 672867 - kernel crashdump analysis section contains errors
Summary: kernel crashdump analysis section contains errors
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: deployment-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromir Hradilek
QA Contact: Nobody's working on this, feel free to take it
URL:
Whiteboard:
Depends On: 672874
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-26 16:00 UTC by Dave Allan
Modified: 2016-04-27 04:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-28 13:27:21 UTC


Attachments (Terms of Use)

Description Dave Allan 2011-01-26 16:00:58 UTC
Description of problem:
The deployment guide at:

http://docs.fedoraproject.org/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-crash.html

says:

yum install --enablerepo=rhel-debuginfo crash kernel-debuginfo

which results in the following error:

Error getting repository data for rhel-debuginfo, repository not found

Dropping the --enablerepo argument says kernel-debuginfo isn't found.  The package appears to be called kernel-debug now, but the files installed by the kernel-debuginfo package are not where the document says they should be.

The document says to start crash with a command similar to the following:

crash /var/crash/timestamp/vmcore /usr/lib/debug/lib/modules/`uname -r`/vmlinux

but the /usr/lib/debug directory does not exist.

Comment 1 Dave Allan 2011-01-26 18:49:58 UTC
So, more information is available in BZ 672874, but the mistake in the docs
turns out to be that

yum install --enablerepo=rhel-debuginfo crash kernel-debuginfo

should be:

yum install crash
debuginfo-install kernel

The debuginfo package creates /usr/lib/debug..., so the rest of the section of
the deployment guide is correct.  Many thanks to Dave Anderson for gently
pointing this out to me.

Comment 2 Jaromir Hradilek 2011-01-26 22:30:25 UTC
Hi Dave, and thank you for reporting this.

Fixed in the development version, commit b7a251af.

Comment 3 Dave Allan 2011-01-27 02:47:32 UTC
great--thanks for the quick turnaround!


Note You need to log in before you can comment on or make changes to this bug.