public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: nobody cared about IRQ 19 (firewire, on a HP 2510p notebook)
Date: Fri, 21 Mar 2008 17:31:11 +0100	[thread overview]
Message-ID: <47E3E2CF.5070408@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080321153952.GA26354@deprecation.cyrius.com>

Martin Michlmayr wrote:
> I just got the following in dmesg a few minutes after booting my
> notebook which was idle at the time this occurred.  This was with
> 2.6.25-rc6 but I've seen the same with 2.6.22 (see the attached
> dmesg from 2.6.22).
> 
> irq 19: nobody cared (try booting with the "irqpoll" option)
> Pid: 0, comm: swapper Not tainted 2.6.25-rc6-amd64 #1
> 
> Call Trace:
>  <IRQ>  [<ffffffff80271c0b>] __report_bad_irq+0x38/0x7c
>  [<ffffffff80271e51>] note_interrupt+0x202/0x249
>  [<ffffffff8027274e>] handle_fasteoi_irq+0xab/0xd0
>  [<ffffffff8020f82c>] do_IRQ+0x6e/0xda
>  [<ffffffff8020c65d>] ret_from_intr+0x0/0x19
>  <EOI>  [<ffffffff80221831>] ? native_irq_enable+0x6/0x7
>  [<ffffffff88006330>] ? :processor:acpi_idle_enter_bm+0x2ab/0x325
>  [<ffffffff803b5ef3>] ? menu_select+0x70/0x99
>  [<ffffffff803b52e1>] ? cpuidle_idle_call+0x77/0xa6
>  [<ffffffff803b526a>] ? cpuidle_idle_call+0x0/0xa6
>  [<ffffffff8020b187>] ? cpu_idle+0xb1/0xdb
>  [<ffffffff8042ea16>] ? rest_init+0x5a/0x5c
> 
> handlers:
> [<ffffffff8806f0f5>] (irq_handler+0x0/0x207 [firewire_ohci])
> Disabling IRQ #19
...
> 02:06.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
...

According to your 2.6.22 dmesg, this happens a while after the firewire 
subsystem seemingly successfully initialized the controller.  Could you 
please post "dmesg | grep firewire" from 2.6.25-rc6 though?

The __report_bad_irq() and "Disabling IRQ #..." can only have happened 
because this condition in fw-ohci.c::irq_handler()

	event = reg_read(ohci, OHCI1394_IntEventClear);

	if (!event || !~event)
		return IRQ_NONE;

happened a lot of times.  This means either
   - Some MMIO reads return bogus values (all zero or all ones in a
     bitfield which should be sparsely populated in a proper interrupt
     event),
or
   - the interrupt was misrouted by the kernel's IRQ infrastructure was
     unable to detect the misrouting, AFAIU.
-- 
Stefan Richter
-=====-==--- --== =-=-=
http://arcgraph.de/sr/

  reply	other threads:[~2008-03-21 16:31 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 [this message]
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
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=47E3E2CF.5070408@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=tbm@cyrius.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