From: Vivek Goyal <vgoyal@redhat.com>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: Maneesh Soni <maneesh@in.ibm.com>,
sripathik@in.ibm.com, linux-acpi@vger.kernel.org
Subject: Re: kdump bugs with rt kernels
Date: Thu, 31 Jul 2008 09:01:29 -0400 [thread overview]
Message-ID: <20080731130129.GA26782@redhat.com> (raw)
In-Reply-To: <48909108.6070106@in.ibm.com>
On Wed, Jul 30, 2008 at 09:34:24PM +0530, Sachin P. Sant wrote:
> Hi Vivek,
>
> There have been few kdump bugs reported against rt kernels.
> I think Ankita would have sent out a mail regarding this.
>
> I had been debugging one of that problem which involves
> LS21 hardware. What i found was kdump kernel hangs during
> ACPI initialization. (acpi_sleep_init() function from
> drivers/acpi/sleep/main.c file)
>
> I also found that rt kernel ignores irqpoll option. So can
> this be the reason for these IRQ related problems during
> kdump kernel ?
>
I think it might not be related to irqpoll. irqpoll will make system
work if kernel has explicitly disabled the irq.
> I remember some time back you had debugged a similar issue
> related to interrupts not being properly routed during kdump
> boot. Could you throw some light on what could be happening ?
>
> If i disable ACPI using pci=noacpi or acpi=noirq kdump kernel
> boots fine. Also if i use plain vanilla kernel or RHEL kernels
> kdump works fine. So this is rt specific issue.
>
Ok, so as long as acpi is removed from the picture, things seems to be
fine. So it definitely looks something related to acpi data structures
and initialization.
Have you made sure that kexec-tools are parsing ACPI tables and ACPI
non volatile RAM area from /proc/iomem and passing it to second kernel?
Other than that I would think of diving deeper into the acpi code to find
out where it is hanging.
CCing ACPI mailing list. Hopefully we might get some ideas about what's
wrong here.
Thanks
Vivek
parent reply other threads:[~2008-07-31 13:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <48909108.6070106@in.ibm.com>]
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=20080731130129.GA26782@redhat.com \
--to=vgoyal@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=sachinp@in.ibm.com \
--cc=sripathik@in.ibm.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