From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?] Date: Tue, 10 Apr 2012 10:44:19 +0200 Message-ID: <4F83F2E3.6010703@suse.cz> References: <4F717CE3.4040206@suse.cz> <4F717D80.9040207@suse.cz> <4F758400.3080907@suse.cz> <1333104359_155028@CP5-2952> <4F75A303.3030409@suse.cz> <1333110296_156038@CP5-2952> <4F7F60BF.9070500@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Thomas Gleixner Cc: Chris Wilson , Jiri Slaby , Keith Packard , dri-devel@lists.freedesktop.org, LKML , daniel@ffwll.ch List-Id: dri-devel@lists.freedesktop.org On 04/07/2012 12:40 AM, Thomas Gleixner wrote: > On Fri, 6 Apr 2012, Jiri Slaby wrote: >> It very looks like the generic IRQ handling code is broken. Like it >> frees/corrupts irq_desc and ... > > OMG, your problem analyzing skills are amazing. Hehe, no I did *no* analysis. I stand here as a bug reporter. > What the heck makes you assume that the irq core code is broken? Core > code, which works on a gazillion of machines and different device > drivers and does not corrupt anything except that i915 thingy? Note that this is a -next regression. And i915 graphics used. This definitely doesn't run on a gazillion of machines. > If you're still convinced that the irq core is messing with your > device string, Nope, thanks for the input. -- js suse labs