public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, 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 22:10:00 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0803302201110.3219@apollo.tec.linutronix.de> (raw)
In-Reply-To: <47EFD09D.3020906@s5r6.in-berlin.de>

On Sun, 30 Mar 2008, Stefan Richter wrote:
> I tend to believe it is a problem to be addressed in the x86 platform support,
> not a driver problem.

Depends. It might be unfixable.

> 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.

Can we please have a full boot log (dmesg) and the output of /proc/interrupts and "lspci -vvv"

Thanks,
	tglx

  reply	other threads:[~2008-03-30 20:11 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
2008-03-30 20:10         ` Thomas Gleixner [this message]
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=alpine.LFD.1.10.0803302201110.3219@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mingo@redhat.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --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