From: Stephan Maciej <stephanm@muc.de>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.2[12] v VIA Rhine and VIA82x audio (working with a fight)
Date: Sun, 21 Sep 2003 15:05:08 +0200 [thread overview]
Message-ID: <200309211505.17352.stephanm@muc.de> (raw)
In-Reply-To: <1064096092.23121.1.camel@dhcp23.swansea.linux.org.uk>
On Sunday 21 September 2003 00:14, Alan Cox wrote:
> On Sad, 2003-09-20 at 21:09, Jamie Lokier wrote:
> > On a 2.5.75 kernel, I don't hear anything from the analogue input.
>
> CMPCI in everything pre 2.4.22pre10-ac or so is obsolete and has all
> sorts of problems with the later chips. C Tien of Cmedia sent a lot of
> updates to the driver that were merged at that point.
Are these in 2.4.23-pre4?
> I'd be interested
> to know if you still have problems wiht that
If yes, there are problems with the updates. Sound randomly locks my machine
up, without any oops message and not even blinking keyboard lights. Only a
hard reset helps.
I have suspected this as being the reason for the lockups:
static ssize_t cm_read(struct file *file, char *buffer, size_t count, loff_t
*ppos)
{
[...]
DECLARE_WAITQUEUE(wait, current);
[...]
add_wait_queue(&s->dma_adc.wait, &wait);
while (count > 0) {
[...]
if (cnt <= 0) {
start_adc(s);
if (file->f_flags & O_NONBLOCK)
return ret ? ret : -EAGAIN;
Shouldn't we do a remove_wait_queue before the return()?
There are many more places to fix if that's a bug. I am willing to provide a
patch if anyone tells me if I am right with the assumption above.
Stephan
next prev parent reply other threads:[~2003-09-21 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 16:38 2.4.2[12] v VIA Rhine and VIA82x audio (working with a fight) Dr. David Alan Gilbert
2003-09-20 17:45 ` Alan Cox
2003-09-20 19:05 ` Dr. David Alan Gilbert
2003-09-20 20:09 ` Jamie Lokier
2003-09-20 22:14 ` Alan Cox
2003-09-21 13:05 ` Stephan Maciej [this message]
2003-09-21 13:16 ` Alan Cox
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=200309211505.17352.stephanm@muc.de \
--to=stephanm@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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 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.