[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Bug 513800] New: attempt to use kdump just freezes the box



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: attempt to use kdump just freezes the box

https://bugzilla.redhat.com/show_bug.cgi?id=513800

           Summary: attempt to use kdump just freezes the box
           Product: Fedora
           Version: 11
          Platform: x86_64
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: low
         Component: kexec-kdump
        AssignedTo: vgoyal redhat com
        ReportedBy: matt castelein rocsoft com
         QAContact: lwang redhat com
                CC: matt castelein rocsoft com,
                    fedora-triage-list redhat com
   Estimated Hours: 0.0
    Classification: Fedora
          Clone Of: 239244


+++ This bug was initially created as a clone of Bug #239244 +++

Description of problem:
After getting some kernel problems, I finally decided to give kdump a try, but
to my surprise, it does not work.
Any attempt to use kdump (with sysrq-c or echo c >/proc/sysrq-trigger) leads to
instant system crash. sysrq does not work anymore at this point and the only
solution is hard poweroff.
I see that FC7 does not ship kernel-kdump package anymore, but since FC7 kernel
is built with CONFIG_RELOCATABLE, it should be fine as kdump kernel I presume.

Version-Release number of selected component (if applicable):
kernel-2.6.21-1.3116.fc7

How reproducible:
100% reproducible.

Steps to Reproduce:
boot kernel with crashkernel=128M 16M option
run service kdump start
run sysctl kernel.sysrq=1
press sysrq-t or echo c >/proc/sysrq-trigger

Additional info:
The system is DELL Latitude D620 laptop with Intel Core2 Duo T7200 CPU, 2G RAM,
i686 arch.
Latest FC7 stuff from development repo.

--- Additional comment from green linuxhacker ru on 2007-05-14 15:24:47 EDT ---

I upgraded to 2.6.21-1.3142.fc7 and the problem is still present.

--- Additional comment from fedora-triage-list redhat com on 2008-04-03
20:33:50 EDT ---

Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

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

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

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

--- Additional comment from fedora-triage-list redhat com on 2008-05-06
21:41:26 EDT ---

This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

--- Additional comment from matt castelein rocsoft com on 2009-07-24 19:47:31
EDT ---

I have encountered this problem on Fedora 11.  I am following the instructions
at:
 https://fedoraproject.org/wiki/Kernel/kdump.. When I get to the point where I
do "echo c > /proc/sysrq-trigger"  the box just freezes and no dump kernel is
loaded.  It just sits there until I reset it.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]