From: Thomas Charbonnel <thomas@undata.org>
To: Dan Nyborg <nyborg@vertice.ca>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: hdsp + acpi/apm = bug/feature?
Date: Mon, 01 Dec 2003 12:50:19 +0100 [thread overview]
Message-ID: <3FCB2AFB.5070205@undata.org> (raw)
In-Reply-To: <3FCA1B3E.7020102@vertice.ca>
Dan Nyborg wrote :
> hello,
>
> some posts were made by myself a couple of months back regarding system
> lockups experienced with the hdsp driver - my system would lock during
> capture or playback.
>
> this lock has been traced to kernel power management, either acpi or
> apm. when either of these are enabled, i experience locks. without them,
> no problems.
>
> i use a 2.4.20 kernel with andrew morton's low latency patch. the cpu is
> an athlon.
>
> thanks,
>
> dan.
>
Hi Dan,
There is no power management support in the hdsp driver at the moment,
so the problem you have shouldn't come from this (and is definitely not
a 'feature' :)
Did you use the kernel's built in ACPI support or an up-to-date patch
from the linux acpi project ?
Did you try without the the low latency patch ?
What I would suggest is that you try the new 2.4.23 kernel. The problem
you're experiencing might have been fixed.
Thomas
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-01 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 12:23 [PATCH] snd-via82xx whitelist addition: ASUS A7V8X Sergey Vlasov
2003-11-30 16:30 ` hdsp + acpi/apm = bug/feature? Dan Nyborg
2003-12-01 11:50 ` Thomas Charbonnel [this message]
2003-12-01 20:58 ` Dan Nyborg
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=3FCB2AFB.5070205@undata.org \
--to=thomas@undata.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nyborg@vertice.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.