Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <1516816150.4109.2.camel@redhat.com>
Subject: Re: "irq/matrix: Spread interrupts on allocation" breaks nouveau in
 mainline kernel
From:   Lyude Paul <lyude@redhat.com>
To:     Thomas Gleixner <tglx@linutronix.de>
Cc:     hpa@zytor.com, keith.busch@intel.com, mingo@kernel.org,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Date:   Wed, 24 Jan 2018 12:49:10 -0500
In-Reply-To: <alpine.DEB.2.20.1801241351080.1997@nanos>
References: <1516744873.29151.3.camel@redhat.com>
         <1516757219.29151.7.camel@redhat.com>
         <alpine.DEB.2.20.1801241351080.1997@nanos>
Organization: Red Hat
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi, please ignore the warning: it happens before and after the regressing
commit (I didn't actually mean to include it on the log I gave here, whoops).
As for how I determined nouveau is getting assigned the same IRQ vector as
another device, I checked using /sys/kernel/debug/irq. Additionally; when
nouveau does initialize properly after resume (e.g. after reverting this
patch) I see it get assigned a seperate vector from the other devices.

On Wed, 2018-01-24 at 13:52 +0100, Thomas Gleixner wrote:
> On Tue, 23 Jan 2018, Lyude Paul wrote:
> 
> > JFYI: I confirmed this patch is definitely broken. I'm seeing nouveau get
> > assigned the same MSI vector as another device on the system, which would
> > explain why interrupts suddenly stop working. I'll keep looking into it
> > further
> > tomorrow.
> 
> How did you determine that it is the same MSI vector as another device?
> 
> Thanks,
> 
> 	tglx
> 
-- 
Cheers,
	Lyude Paul