Bug 224034 - reboot on startup after kernel-2.6.19 installation
Summary: reboot on startup after kernel-2.6.19 installation
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools (Show other bugs)
(Show other bugs)
Version: 6
Hardware: i686 Linux
Target Milestone: ---
Assignee: Neil Horman
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-23 18:56 UTC by Ronny Buchmann
Modified: 2008-05-06 17:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 17:55:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ronny Buchmann 2007-01-23 18:56:10 UTC
Description of problem:
starting kdump init script triggers a reboot

Version-Release number of selected component (if applicable):

How reproducible:
install kernel-2.6.19-1.2895.fc6

Steps to Reproduce:
1. /etc/init.d/kdump start
Actual results:

Expected results:
load kdump kernel

Additional info:
it seems the init script needs some fixes from rawhide/rhel5

especially s#-f /proc/vmcore#-s /proc/vmcore#

Comment 1 Neil Horman 2007-01-23 19:48:09 UTC
yeah, I'll fix that shortly.  sorry about that, and thanks!

Comment 2 Neil Horman 2007-01-23 20:23:53 UTC
fixed in -55.fc6.  Thanks!

Comment 3 Bug Zapper 2008-04-04 05:42:22 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 4 Bug Zapper 2008-05-06 17:55:46 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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