public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Prashant Dinkar Kharche <pkharche@inmage.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: kdump not working Intel S5520UR motherboards with Xeon processor
Date: Mon, 23 Jan 2012 10:18:54 -0500	[thread overview]
Message-ID: <20120123151854.GL5650@redhat.com> (raw)
In-Reply-To: <7967B71B602AF546971AB6303361B1A561AC86E1E8@mbe.inside.abhaisystems.com>

On Sat, Jan 21, 2012 at 10:21:17AM -0800, Prashant Dinkar Kharche wrote:
> Hi,
> 
> I have been trying to get kdump working on Intel S5520 chipset with Xeon processor on RHEL 5 update 5  or update 6, but it appears that when I trigger a crash dump, system reboots abruptly right after loading the kdump kernel. Key observation during this experiment was that when I turn off acpi interrupt handling (acpi=off), crash has worked on RHEL 5 update 5. I have captured output of lspci and cpuinfo  below for reference.
> 
> Whereas, on RHEL 6 kdump works fine on this hardware. Could someone please help me identify the patches for RHEL 5 update 5 kernel that might be required for this issue?

This can only be done by Red Hat as they are the only ones that know what
patches are in their kernel.  Please file a bugzilla or work with your TAM
to bring attention to the problem at Red Hat.

Cheers,
Don

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2012-01-23 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 20:30 watchdogs and kdump Don Zickus
2011-10-27 21:43 ` Pádraig Brady
2011-10-28 13:39   ` Don Zickus
2012-01-21 18:21   ` kdump not working Intel S5520UR motherboards with Xeon processor Prashant Dinkar Kharche
2012-01-23 15:18     ` Don Zickus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120123151854.GL5650@redhat.com \
    --to=dzickus@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=pkharche@inmage.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox