Martin Michlmayr wrote:
quoted text
> * 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/
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/