From: Lee Revell <rlrevell@joe-job.com>
To: ocilent1@gmail.com
Cc: Chris Wedgwood <cw@f00f.org>, Con Kolivas <kernel@kolivas.org>,
ck@vds.kolivas.org, Hugo Vanwoerkom <rociobarroso@att.net.mx>,
linux list <linux-kernel@vger.kernel.org>
Subject: Re: sound skips on 2.6.16.17
Date: Mon, 19 Jun 2006 17:24:40 -0400 [thread overview]
Message-ID: <1150752280.2754.38.camel@mindpipe> (raw)
In-Reply-To: <200606191154.33747.ocilent1@gmail.com>
On Mon, 2006-06-19 at 11:54 +0800, ocilent1 wrote:
> On Sunday 18 June 2006 12:40, Chris Wedgwood wrote:
> > On Sun, Jun 18, 2006 at 12:04:29PM +0800, ocilent1 wrote:
> > > (PCI-quirk-VIA-IRQ-fixup-should-only-run-for-VIA-southbridges.patch)
> > > that is causing the sound stuttering/skipping problems for our users
> > > with VIA chipsets. Backing out the first patch alone did not fix the
> > > problem (PCI-VIA-quirk-fixup-additional-PCI-IDs.patch) but to back
> > > out the 2nd patch, you need to have initially backed out the first
> > > patch, due to the way the patches apply in series.
> >
> > what mainboard/CPU do you have there?
> >
> > what does 'lspci -n' say?
>
> It is a compaq presario with KM266 mobo AMD XP2200+
>
Here is lspci -n output from another user on the ALSA lists who is
afflicted by this bug:
00:00.0 Class 0600: 1106:0204
00:00.1 Class 0600: 1106:1204
00:00.2 Class 0600: 1106:2204
00:00.3 Class 0600: 1106:3204
00:00.4 Class 0600: 1106:4204
00:00.7 Class 0600: 1106:7204
00:01.0 Class 0604: 1106:b188
00:0a.0 Class 0200: 10ec:8139 (rev 10)
00:0f.0 Class 0101: 1106:0571 (rev 06)
00:10.0 Class 0c03: 1106:3038 (rev 81)
00:10.1 Class 0c03: 1106:3038 (rev 81)
00:10.2 Class 0c03: 1106:3038 (rev 81)
00:10.3 Class 0c03: 1106:3038 (rev 81)
00:10.4 Class 0c03: 1106:3104 (rev 86)
00:11.0 Class 0601: 1106:3227
00:11.5 Class 0401: 1106:3059 (rev 60)
00:18.0 Class 0600: 1022:1100
00:18.1 Class 0600: 1022:1101
00:18.2 Class 0600: 1022:1102
00:18.3 Class 0600: 1022:1103
01:00.0 Class 0300: 1002:4151
01:00.1 Class 0380: 1002:4171
Is it likely to be fixed in 2.6.17.1?
Lee
next prev parent reply other threads:[~2006-06-19 21:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4487F942.3030601@att.net.mx>
[not found] ` <200606161115.53716.ocilent1@gmail.com>
[not found] ` <4493D24D.2010902@att.net.mx>
2006-06-17 11:29 ` sound skips on 2.6.16.17 Con Kolivas
2006-06-18 2:41 ` Chris Wedgwood
2006-06-18 4:04 ` ocilent1
2006-06-18 4:40 ` Chris Wedgwood
2006-06-18 4:49 ` ocilent1
2006-06-18 11:11 ` Hugo Vanwoerkom
2006-06-18 13:35 ` karsten wiese
2006-06-19 3:54 ` ocilent1
2006-06-19 21:24 ` Lee Revell [this message]
2006-06-19 21:50 ` Chris Wedgwood
2006-06-20 18:35 ` Lee Revell
2006-06-20 19:36 ` Chris Wedgwood
2006-06-24 14:08 ` Jacek J
2006-06-27 22:25 ` Lee Revell
2006-06-27 22:48 ` Chris Wedgwood
2006-07-07 16:33 ` Lee Revell
2006-07-07 17:00 ` Chris Wedgwood
2006-07-07 18:00 ` Lee Revell
2006-07-19 6:03 ` ocilent1
2006-07-19 6:33 ` Chris Wedgwood
2006-07-19 11:25 ` ocilent1
2006-07-19 13:47 ` Hugo Vanwoerkom
2006-07-19 13:51 ` ocilent1
2006-10-07 21:39 ` sound skips on 2.6.18-ck1 Hugo Vanwoerkom
2006-10-07 21:56 ` Hugo Vanwoerkom
2006-10-08 16:18 ` Hugo Vanwoerkom
2006-10-08 17:19 ` [ck] " Andreas Mohr
2006-10-08 17:33 ` Daniel Drake
2006-06-18 11:06 ` sound skips on 2.6.16.17 Hugo Vanwoerkom
2006-06-18 13:10 ` Sergey Vlasov
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=1150752280.2754.38.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ck@vds.kolivas.org \
--cc=cw@f00f.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocilent1@gmail.com \
--cc=rociobarroso@att.net.mx \
/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