From: Jiri Slaby <jslaby@suse.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Jiri Slaby <jirislaby@gmail.com>,
Keith Packard <keithp@keithp.com>,
dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
daniel@ffwll.ch
Subject: Re: i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?]
Date: Tue, 10 Apr 2012 10:44:19 +0200 [thread overview]
Message-ID: <4F83F2E3.6010703@suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.02.1204062343050.2542@ionos>
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
next prev parent reply other threads:[~2012-04-10 8:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 8:40 i915_driver_irq_handler: irq 42: nobody cared Jiri Slaby
2012-03-27 8:42 ` Jiri Slaby
2012-03-30 9:59 ` Jiri Slaby
2012-03-30 10:45 ` Chris Wilson
2012-03-30 12:11 ` Jiri Slaby
2012-03-30 12:24 ` Chris Wilson
2012-04-06 21:31 ` i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?] Jiri Slaby
2012-04-06 22:40 ` Thomas Gleixner
2012-04-09 17:12 ` Jesse Barnes
2012-04-09 17:52 ` Dave Airlie
2012-04-10 8:44 ` Jiri Slaby [this message]
2012-04-10 8:50 ` Daniel Vetter
2012-04-10 8:52 ` i915_driver_irq_handler: irq 42: nobody cared Jiri Slaby
2012-04-10 16:50 ` Marcin Slusarz
2012-04-09 17:11 ` Jesse Barnes
2012-04-10 8:47 ` Jiri Slaby
2012-04-10 8:58 ` Daniel Vetter
2012-04-10 9:48 ` Jiri Slaby
2012-04-10 16:26 ` Jesse Barnes
2012-04-10 16:26 ` Jesse Barnes
2012-04-10 18:11 ` Jiri Slaby
2012-04-10 18:34 ` Jesse Barnes
2012-04-10 19:52 ` Jiri Slaby
2012-04-10 20:32 ` Daniel Vetter
2012-04-10 20:34 ` Jesse Barnes
2012-04-10 20:34 ` Jesse Barnes
2012-04-11 10:40 ` Daniel Vetter
2012-05-03 19:56 ` Jiri Slaby
2012-05-03 21:15 ` Daniel Vetter
2012-05-03 21:15 ` Daniel Vetter
2012-05-03 21:16 ` Jiri Slaby
2012-05-03 21:54 ` Jesse Barnes
2012-05-03 23:15 ` Ben Widawsky
2012-05-03 23:15 ` Ben Widawsky
2012-04-11 6:29 ` Michel Dänzer
2012-04-11 6:29 ` Michel Dänzer
2012-04-11 16:03 ` Jesse Barnes
2012-03-27 8:57 ` Daniel Vetter
2012-03-27 10:54 ` Jiri Slaby
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=4F83F2E3.6010703@suse.cz \
--to=jslaby@suse.cz \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.