From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <greg@kroah.com>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Fastboot mailing list <fastboot@lists.osdl.org>,
Morton Andrew Morton <akpm@osdl.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
Date: 03 Jun 2005 12:36:00 -0600 [thread overview]
Message-ID: <m13brz9tkf.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050603182147.GB5751@kroah.com>
Greg KH <greg@kroah.com> writes:
> On Fri, Jun 03, 2005 at 04:55:24PM +0530, Vivek Goyal wrote:
> > Hi,
> >
> > In kdump, sometimes, general driver initialization issues seems to be cropping
>
> > in second kernel due to devices not being shutdown during crash and these
> > devices are sending interrupts while second kernel is booting and drivers are
>
> > not expecting any interrupts yet.
>
> What are the errors you are seeing?
> How would the drivers be able to be getting interrupts delivered to them
> if they haven't registered the irq handler yet?
As I recall the drivers were not getting the interrupts but the interrupts
were happening. To stop being spammed the kernel disables the irq line,
at the interrupt controller. Then when the driver registered the
interrupt it would never receive the interrupt.
Eric
next prev parent reply other threads:[~2005-06-03 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 11:25 [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel Vivek Goyal
2005-06-03 11:54 ` Richard B. Johnson
2005-06-03 15:24 ` Alan Stern
2005-06-03 18:26 ` Eric W. Biederman
2005-06-03 18:21 ` Greg KH
2005-06-03 18:36 ` Eric W. Biederman [this message]
2005-06-04 13:18 ` Denis Vlasenko
2005-06-04 13:43 ` [Fastboot] " Dipankar Sarma
2005-06-04 14:03 ` Dipankar Sarma
2005-06-04 21:14 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2005-06-04 10:43 Vivek Goyal
2005-06-04 10:57 Vivek Goyal
2005-06-04 15:35 ` Alan Stern
2005-06-04 18:26 ` Grant Grundler
[not found] <4bExX-3uT-11@gated-at.bofh.it>
2005-06-04 12:38 ` Bodo Eggert
2005-06-07 3:07 Vivek Goyal
2005-06-07 5:07 ` Grant Grundler
2005-06-07 9:59 ` Eric W. Biederman
2005-06-07 16:21 ` Grant Grundler
2005-06-07 11:56 Vivek Goyal
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=m13brz9tkf.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=fastboot@lists.osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=vgoyal@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