[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41b516cb0903301853i37aaae1ft4e8d1de5e3bf28f4@mail.gmail.com>
Date: Mon, 30 Mar 2009 18:53:45 -0700
From: Chris Leech <christopher.leech@...el.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] irq: mask irq before move it
On Mon, Mar 30, 2009 at 3:56 PM, Chris Leech
<christopher.leech@...el.com> wrote:
> On Mon, Mar 30, 2009 at 03:25:07PM -0700, Yinghai Lu wrote:
>> On Mon, Mar 30, 2009 at 3:10 PM, Chris Leech
>> <christopher.leech@...el.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@...nel.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?
>
> I don't know, I'm not really up on how drivers that deal with
> PCI-Express switch ports work. I'd be happy to test again with both
> advances error reporting and hotplug removed from my configuration.
Removing AER and PCI hotplug did not change anything. There were no
shared MSI interrupts showing in that case.
- Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists