public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Stevenson <james@stev.org>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21pre3-ac5
Date: 29 Jan 2003 22:52:51 +0000	[thread overview]
Message-ID: <1043880772.1925.3.camel@god.stev.org> (raw)
In-Reply-To: <200301291500.h0TF0xW31184@devserv.devel.redhat.com>

Hi

i seem to keep getting really flaky / cracking sounds with the
Via 686a/8233/8235 audio driver 1.9.1-ac2

any ideas on how i can work out whats going wrong ?
Its an on board sound card from the AOpen MK77 board



Via 686a/8233/8235 audio driver 1.9.1-ac2
via82cxxx: Six channel audio available
PCI: Setting latency timer of device 00:11.5 to 64
ac97_codec: AC97 Audio codec, id: ADS96 (Analog Devices AD1885)
via82cxxx: board #1 at 0xE000, IRQ 12
via_audio: ignoring drain playback error -11

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97
Audio Controller (rev 30)
	Subsystem: AOPEN Inc.: Unknown device 006a
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin C routed to IRQ 12
	Region 0: I/O ports at e000 [size=256]

thanks
	James




On Wed, 2003-01-29 at 15:00, Alan Cox wrote:
> This patch fixes the random oops some peopel saw on 2.4.21pre-ac* before.
> It should also fix highmem I/O and a pile of the minor glitches. I've left
> the more interesting changes out of this patch set so that the stability
> stuff can be dealt with first.
> 
> To minimise changes while verifying the fixes this is against pre3 still.




      reply	other threads:[~2003-01-29 22:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 15:00 Linux 2.4.21pre3-ac5 Alan Cox
2003-01-29 22:52 ` James Stevenson [this message]

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=1043880772.1925.3.camel@god.stev.org \
    --to=james@stev.org \
    --cc=alan@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox