From: Yinghai Lu <yinghai@kernel.org>
To: Chris Leech <christopher.leech@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irq: mask irq before move it
Date: Mon, 30 Mar 2009 15:25:07 -0700 [thread overview]
Message-ID: <86802c440903301525h41481c98lfff9b40b98b2d7f3@mail.gmail.com> (raw)
In-Reply-To: <20090330221034.GC27774@cleech-lnx.jf.intel.com>
On Mon, Mar 30, 2009 at 3:10 PM, Chris Leech
<christopher.leech@intel.com> wrote:
> On Fri, Mar 27, 2009 at 09:43:01PM -0700, Yinghai Lu wrote:
>>
>> Imapct: fix panic
>>
>> try to mask the irq, before move the irq desc
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> This change did not fix the issue I'm seeing. The following output was
> generated with 2.6.29 + this patch.
>
> I will send system information and kernel config separately.
in your /proc/interrupts
57: 0 0 0 0 0 0
0 0 PCI-MSI-edge aerdrv, pciehp
how can that be shared?
YH
next prev parent reply other threads:[~2009-03-30 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 22:04 2.6.29 bug with SPARSE_IRQ + NUMA_MIGRATE_IRQ_DESC Chris Leech
[not found] ` <86802c440903261929s775fe85cv86b900e2610acf1d@mail.gmail.com>
[not found] ` <20090327163438.GA10185@cleech-lnx.jf.intel.com>
2009-03-28 4:43 ` [PATCH] irq: mask irq before move it Yinghai Lu
2009-03-30 22:09 ` Chris Leech
2009-03-30 22:10 ` Chris Leech
2009-03-30 22:25 ` Yinghai Lu [this message]
2009-03-30 22:56 ` Chris Leech
2009-03-31 1:53 ` Chris Leech
2009-03-31 13:19 ` Thomas Gleixner
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=86802c440903301525h41481c98lfff9b40b98b2d7f3@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=christopher.leech@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®