From: Alan Cox <alan@redhat.com>
To: cogwepeter@greenie.frogspace.net (Peter)
Cc: linux-kernel@vger.kernel.org, alan@redhat.com (Alan Cox)
Subject: Re: 2.4.19 -- ac97_codec failure ALi 5451
Date: Thu, 9 Jan 2003 21:50:47 -0500 (EST) [thread overview]
Message-ID: <200301100250.h0A2olE20795@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301090206290.30969-100000@greenie.frogspace.net> from "Peter" at Jan 09, 2003 06:35:53 PM
> Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio,
> version 0.14.9d, 00:57:19 Jan 9 2003
> PCI: Enabling device 00:06.0 (0000 -> 0003)
> PCI: Assigned IRQ 10 for device 00:06.0
> trident: ALi Audio Accelerator found at IO 0x1000, IRQ 10
> ac97_codec: AC97 Audio codec, id: 0x4144:0x5372 (Unknown)
So far so good.
> ali: AC97 CODEC read timed out.
> last message repeated 127 times
> ali: AC97 CODEC write timed out.
> ac97_codec: AC97 codec, id: 0x0000:0x0000 (Unknown)
Something lost the codec. Could be power management - was the laptop
suspended before it went funny ?
Alan
next prev parent reply other threads:[~2003-01-10 2:42 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 [this message]
2003-01-10 4:30 ` Peter
2003-01-10 13:15 ` Peter
2003-01-10 13:36 ` Alan Cox
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=200301100250.h0A2olE20795@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=cogwepeter@greenie.frogspace.net \
--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.