From: Alan Cox <alan@redhat.com>
To: peter@cogweb.net (Peter)
Cc: linux-kernel@vger.kernel.org, alan@redhat.com (Alan Cox)
Subject: Re: 2.4.19 -- ac97_codec failure ALi 5451
Date: Fri, 10 Jan 2003 08:36:13 -0500 (EST) [thread overview]
Message-ID: <200301101336.h0ADaDG10038@devserv.devel.redhat.com> (raw)
In-Reply-To: <1042204553.3e1ec789564b6@webmail.cogweb.net> from "Peter" at Jan 10, 2003 05:15:53 AM
> I've downloaded the latest driver and am running 2.4.20 (yea!) -- the trident.c here
> is actually more recent than 2.5.55. It now loads fast and with no protest from
> ac97_codec, which has a new ID (ADS114). However, there's still not a peep (I try
> cat test.mp3 > /dev/dsp) -- and when KDE Control Center tries to restart the arts
> sound server, it alarmingly fails on "CPU overload" or just freezes the whole
> system. Is there anything I can do to get more information about what is not
> happening?
No but the info is very useful. The key change involving ac97 is that the
new code in 2.4.x waits much longer for the codec reset to finish. I'm not
sure where the audio has gone however 8(
next prev parent reply other threads:[~2003-01-10 13:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 5:50 2.4.19-ac4 build problem Peter
2002-09-04 16:21 ` Greg KH
2002-09-05 3:59 ` Peter
2002-09-05 6:58 ` Greg KH
2002-09-12 2:41 ` 2.4.19-ac4 Out of Memory cogwepeter
2003-01-10 2:35 ` 2.4.19 -- ac97_codec failure ALi 5451 Peter
2003-01-10 2:50 ` Alan Cox
2003-01-10 4:30 ` Peter
2003-01-10 13:15 ` Peter
2003-01-10 13:36 ` Alan Cox [this message]
2003-01-21 0:41 ` 2.4.20 USB storage (SCSI emulation) Peter Nome
2003-01-21 1:18 ` Matthew Dharm
2003-01-21 2:01 ` Peter Nome
2002-09-05 8:00 ` 2.4.19-ac4 build problem Peter
2002-09-05 16:26 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-01-13 4:40 2.4.19 -- ac97_codec failure ALi 5451 peter
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=200301101336.h0ADaDG10038@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cogweb.net \
/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