From: "Christian Böhme" <monodhs@gmx.de>
To: linuxppc-dev@ozlabs.org
Subject: Interrupt routing broken on TiBook IV with 2.6.21.x ?
Date: Mon, 21 May 2007 02:06:19 +0200 [thread overview]
Message-ID: <4650E27B.3020401@gmx.de> (raw)
Hi all,
With the availability of the stable 2.6.21.x kernels I recently started to
move over from OSS to ALSA for audio I/O. Along with that move came the
surprise that not the simplest audio output works anymore (actually, this
was the case with the stable 2.6.20.x kernels and OSS already which I
therefore opted to avoid).
The problem I ran into is that no matter which application (speaker-test,
aplay, xmms, gxine) using either the native ALSA API or via the OSS
compatibility layer, none of these is able to sustain audio output for
more than 7 seconds. In fact, most attempts max out at statistically one
second (with many even shorter than that). After the signal at the output
jack died, the application appears to be blocking forever (it does not spin)
with no signs of ending its output.
I initially presented this problem on alsa-user@lists.sourceforge.net where
someone suggested that it might actually be caused by (broken) interrupt
routing for the built-in audio device. This assumption may be supported
by the observation that once the sound previously produced by the application
(speaker-test in the simplest case) stopped being sent through the output
jack, no increase in the interrupt counter occurs.
An example output of /proc/interrupts on my machine looks like this (why
eth0 does not show up in this listing is beyond me):
CPU0
19: 39005 MPIC 1 Level ide0
20: 34 MPIC 1 Level ide1
25: 151785 MPIC 1 Level VIA-PMU
26: 131 MPIC 1 Level keywest i2c
27: 1 MPIC 1 Level ohci_hcd:usb1
28: 1 MPIC 1 Level ohci_hcd:usb2
30: 197 MPIC 1 Edge PMac Output
31: 1 MPIC 1 Edge PMac Input
40: 2 MPIC 1 Level ohci1394
42: 0 MPIC 1 Level keywest i2c
47: 7682 MPIC 1 Level GPIO1 ADB
48: 39571 MPIC 1 Level radeon@pci:0000:00:10.0
57: 0 MPIC 1 Level eth1
58: 1 MPIC 1 Level yenta
61: 1 MPIC 1 Edge Sound Headphone Detection
BAD: 0
Has anyone any idea what causes the audio output to die prematurely ?
Cheers,
Christian
next reply other threads:[~2007-05-21 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 0:06 Christian Böhme [this message]
2007-05-21 1:56 ` Interrupt routing broken on TiBook IV with 2.6.21.x ? Benjamin Herrenschmidt
2007-05-21 20:08 ` Christian Böhme
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=4650E27B.3020401@gmx.de \
--to=monodhs@gmx.de \
--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).