From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: nobody cared about IRQ 19 (firewire, on a HP 2510p notebook)
Date: Sun, 30 Mar 2008 19:40:45 +0200 [thread overview]
Message-ID: <47EFD09D.3020906@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080330161339.GC28821@deprecation.cyrius.com>
Martin Michlmayr wrote:
> * Stefan Richter <stefanr@s5r6.in-berlin.de> [2008-03-30 13:11]:
>> Martin, please check whether the same happens if you disable firewire-ohci
>> in the kernel config (or blacklist it in the modprobe config) and use the
>> ohci1394 driver instead.
>
> Yes, I get essentially the same message with the ohci1394 driver:
>
> [ 895.455783] irq 19: nobody cared (try booting with the "irqpoll" option)
> [ 895.455783] Pid: 0, comm: swapper Not tainted 2.6.25-rc7-amd64 #1
> [ 895.455783]
> [ 895.455783] Call Trace:
> [ 895.455783] <IRQ> [<ffffffff88078155>] :ohci1394:ohci_irq_handler+0x4b/0x76e
> [ 895.455783] [<ffffffff8026c883>] __report_bad_irq+0x30/0x72
> [ 895.455783] [<ffffffff8026cac2>] note_interrupt+0x1fd/0x23f
> [ 895.455783] [<ffffffff8026d34f>] handle_fasteoi_irq+0xa5/0xc8
> [ 895.455783] [<ffffffff8020f53c>] do_IRQ+0x6d/0xd9
> [ 895.455783] [<ffffffff8020c46d>] ret_from_intr+0x0/0x19
> [ 895.455783] <EOI> [<ffffffff803a25a4>] menu_reflect+0x0/0x75
> [ 895.455783] [<ffffffff8800642b>] :processor:acpi_idle_enter_simple+0x18d/0x1fe
> [ 895.455783] [<ffffffff803a1b2b>] cpuidle_idle_call+0x7a/0xb3
> [ 895.455783] [<ffffffff803a1ab1>] cpuidle_idle_call+0x0/0xb3
> [ 895.455783] [<ffffffff8020b06c>] cpu_idle+0xa9/0xd3
> [ 895.455783]
> [ 895.455783] handlers:
> [ 895.455783] [<ffffffff8807810a>] (ohci_irq_handler+0x0/0x76e [ohci1394])
> [ 895.455783] Disabling IRQ #19
>
> dmesg is attached.
>
Thanks.
I tend to believe it is a problem to be addressed in the x86 platform
support, not a driver problem.
I Cc'd some random x86 folk... To rehash the issue:
- Controller: Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
Board: PM965/GM965/GL960 based
The R5C832 is known to work with ohci1394 according to
http://hardware4linux.info/component/14348/ and other reports.
- Martin also saw it happen with Linux 2.6.22.
- firewire-ohci + firewire-core as well as ohci1394 + ieee1394
appear to initialize the controller on Martin's laptop just fine.
Among else this means that a number of register reads and writes
succeed.
- Some time later, without having actually used the FireWire
controller, "irq 19: nobody cared"/ "Disabling IRQ #19" occurs.
AFAIU the code, this is apparently because firewire-ohci's or
ohci1394's IRQ handler was called repeatedly but got either 0 or ~0
when reading the chip's interrupt event register.
--
Stefan Richter
-=====-==--- --== ====-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-03-30 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 15:39 nobody cared about IRQ 19 (firewire, on a HP 2510p notebook) Martin Michlmayr
2008-03-21 16:31 ` Stefan Richter
2008-03-22 11:27 ` Martin Michlmayr
2008-03-30 11:11 ` Stefan Richter
2008-03-30 16:13 ` Martin Michlmayr
2008-03-30 17:40 ` Stefan Richter [this message]
2008-03-30 20:10 ` Thomas Gleixner
2008-03-31 9:57 ` Martin Michlmayr
2008-03-31 10:17 ` Thomas Gleixner
2008-03-31 14:44 ` Martin Michlmayr
2008-04-01 7:20 ` Thomas Gleixner
2008-04-01 7:41 ` Benjamin Herrenschmidt
2008-03-31 1:06 ` Jarod Wilson
2008-03-31 10:19 ` Thomas Gleixner
2008-03-31 10:28 ` Martin Michlmayr
2008-03-31 12:58 ` Stefan Richter
2008-03-31 13:00 ` Stefan Richter
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=47EFD09D.3020906@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mingo@redhat.com \
--cc=tbm@cyrius.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox