linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Christian Böhme" <monodhs@gmx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Interrupt routing broken on TiBook IV with 2.6.21.x ?
Date: Mon, 21 May 2007 22:08:40 +0200	[thread overview]
Message-ID: <4651FC48.8000002@gmx.de> (raw)
In-Reply-To: <1179712614.32247.597.camel@localhost.localdomain>

Benjamin Herrenschmidt wrote:

> Nope... it can't be a routing problem since interrupt -is- routed (you
> are getting it !)

Actually, these were the exact words from the ALSA developer.  For some
reason, however, the interrupt count does not increase after some (variable)
time.  It looks as if the ALSA code waits for but not receiving them.  After
a restart, an audio signal does leave the jack and the interrupt count
increases but only for about a second (sometimes more, often less).  No idea 
whether interrupts must be routed/are routable on this very machine I have at 
all ...

> Which exact tipb model is this ? (cat /proc/device-tree/model)

PowerBook3,5 of the 2002-11 release variety.

I stuck to OSS up to the 2.6.19.x kernels where everything (surprisingly)
``just worked''.  Then came the 2.6.20.x series and <root>/sound/oss/\
dmasound/dmasound_awacs.c started spitting out loads of ``tx-irq: xfer died -
patching it up...'' messages with stuttering audio output but nothing
different in their respective implementations from 2.6.19.x to 2.6.20.x.

Is there anything particular I can dive into myself to expedite finding the
cause of the problem without learning the full details of the PPC implemen-
tation ?


Cheers,
Christian

  reply	other threads:[~2007-05-21 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21  0:06 Interrupt routing broken on TiBook IV with 2.6.21.x ? Christian Böhme
2007-05-21  1:56 ` Benjamin Herrenschmidt
2007-05-21 20:08   ` Christian Böhme [this message]
2007-05-21 22:11     ` Benjamin Herrenschmidt
2007-05-21 22:47       ` Christian Böhme
2007-05-21 23:15         ` Benjamin Herrenschmidt
2007-05-21 23:44           ` Christian Böhme

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=4651FC48.8000002@gmx.de \
    --to=monodhs@gmx.de \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).