dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jiri Slaby <jslaby@suse.cz>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Jiri Slaby <jirislaby@gmail.com>
Subject: Re: i915_driver_irq_handler: irq 42: nobody cared
Date: Tue, 27 Mar 2012 10:57:49 +0200	[thread overview]
Message-ID: <20120327085749.GE4276@phenom.ffwll.local> (raw)
In-Reply-To: <4F717CE3.4040206@suse.cz>

On Tue, Mar 27, 2012 at 10:40:03AM +0200, Jiri Slaby wrote:
> Hi,
> 
> I'm getting spurious interrupts leading to disabling the interrupt:
>  42:    1916853    2471662   PCI-MSI-edge      i915@pci:0000:00:02.0
> 
> The message:
> irq 42: nobody cared (try booting with the "irqpoll" option)
> Pid: 20716, comm: virtuoso-t Not tainted 3.3.0-next-20120326_64+ #1673
> 
> It is not new, but now I can reproduce it more-or-less reliably after an
> hour or so. It usually happens when playing a game using wine.
> 
> Do you want me to dump some registers when IRQ_NONE is returned from the
> ISR? As this is MSI, nobody else can sit there.

Yeah, dumping some interrupt regs if the isr returns IRQ_NONE sounds good.
For a start just dump everything that the isr itself reads out or writes
back - I think we can ignore subordinate interrupt sources in i915 for now.

And please mind the guy with bad memory and tell us which chip you have
again?

Yours, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  parent reply	other threads:[~2012-03-27  8:57 UTC|newest]

Thread overview: 34+ 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
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 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-11 10:40                       ` Daniel Vetter
2012-05-03 19:56                         ` Jiri Slaby
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-04-11  6:29                 ` Michel Dänzer
2012-04-11 16:03                   ` Jesse Barnes
2012-03-27  8:57 ` Daniel Vetter [this message]
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=20120327085749.GE4276@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    /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