From: Sebastian Kloska <kloska@scienion.de>
To: Keith Duthie <psycho@albatross.co.nz>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: APM realy sucks on 2.6.x
Date: Mon, 07 Jun 2004 16:47:10 +0200 [thread overview]
Message-ID: <40C47FEE.6080505@scienion.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0406080228110.27816@loki.albatross.co.nz>
Thanks ...
The pure ALSA system with PCI Cirrus Logic CS4281
(my configuration) just dropped of my list of
the 'bad' one ....
Does this bug freeze the machine ? Or just block
the outputting program ?
PCM will be the next to look at...
+-compile->reboot->check->-+
^ |
| |
+---<----------------------+
Kind of feel like in the old days where
a decend 'printf(stderr,....)' was THE
state of the art debugging tool ....
Cheers
S.,
Keith Duthie wrote:
> On Mon, 7 Jun 2004, Sebastian Kloska wrote:
>
>
>> So if anybody out there could give me guidance on how the apm code
>> might interact with the ALSA sound system it would be highly
>> appreciated....
>
>
> In a word, badly. For at least one chipset, suspending while outputting
> to the pcm device causes the program outputting to the pcm device to enter
> the uninterruptible sleep state. A reboot is then required for the pcm
> device to be usable again...
>
> (I attempted to report this back in February, but my bug report and
> workaround patch apparently didn't get through the alsa-devel spam
> filters.)
--
**********************************
Dr. Sebastian Kloska
Head of Bioinformatics
Scienion AG
Volmerstr. 7a
12489 Berlin
phone: +49-(30)-6392-1708
fax: +49-(30)-6392-1701
http://www.scienion.de
**********************************
next prev parent reply other threads:[~2004-06-07 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 21:26 APM realy sucks on 2.6.x Sebastian Kloska
2004-06-04 23:14 ` Keith Duthie
2004-06-05 8:03 ` Sebastian Kloska
2004-06-04 23:54 ` Hugh Dickins
2004-06-05 17:18 ` Sebastian Kloska
2004-06-06 3:29 ` Michael Clark
2004-06-06 4:25 ` Andrew Morton
2004-06-06 13:56 ` Sebastian Kloska
2004-06-07 12:38 ` Pavel Machek
2004-06-07 13:37 ` Sebastian Kloska
2004-06-07 14:05 ` Pavel Machek
2004-06-07 14:28 ` Sebastian Kloska
2004-06-07 14:48 ` Pavel Machek
2004-06-07 19:53 ` Felipe Alfaro Solana
2004-06-07 21:13 ` Sebastian Kloska
2004-06-08 4:16 ` Clemens Schwaighofer
2004-06-08 7:12 ` Sebastian Kloska
2004-06-08 8:58 ` Pavel Machek
2004-06-08 9:02 ` Clemens Schwaighofer
2004-06-08 9:17 ` Pavel Machek
2004-06-08 9:50 ` Clemens Schwaighofer
2004-06-08 9:55 ` Pavel Machek
2004-06-08 23:59 ` Clemens Schwaighofer
2004-06-08 17:48 ` Bill Davidsen
2004-06-08 18:59 ` Daniel Gryniewicz
2004-06-08 20:18 ` Ian Stirling
2004-06-07 14:42 ` Keith Duthie
2004-06-07 14:44 ` Pavel Machek
2004-06-07 14:47 ` Sebastian Kloska [this message]
2004-06-07 14:51 ` Pavel Machek
2004-06-07 15:09 ` Sebastian Kloska
2004-06-07 16:26 ` Pavel Machek
2004-06-07 15:19 ` Keith Duthie
-- strict thread matches above, loose matches on Subject: below --
2004-06-07 8:11 Sebastian Kloska
2004-06-08 9:49 Sau Dan Lee
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=40C47FEE.6080505@scienion.de \
--to=kloska@scienion.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=psycho@albatross.co.nz \
/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