From: Jiri Slaby <jslaby@suse.cz>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org, Jiri Slaby <jirislaby@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: i915_driver_irq_handler: irq 42: nobody cared
Date: Tue, 27 Mar 2012 10:40:03 +0200 [thread overview]
Message-ID: <4F717CE3.4040206@suse.cz> (raw)
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.
thanks,
-- js suse labs
next reply other threads:[~2012-03-27 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 8:40 Jiri Slaby [this message]
2012-03-27 8:57 ` i915_driver_irq_handler: irq 42: nobody cared Daniel Vetter
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=4F717CE3.4040206@suse.cz \
--to=jslaby@suse.cz \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=keithp@keithp.com \
/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