From: ocilent1 <ocilent1@gmail.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: 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: Sun, 18 Jun 2006 12:04:29 +0800 [thread overview]
Message-ID: <200606181204.29626.ocilent1@gmail.com> (raw)
In-Reply-To: <20060618024130.GA32399@tuatara.stupidest.org>
On Sunday 18 June 2006 10:41, Chris Wedgwood wrote:
> On Sat, Jun 17, 2006 at 09:29:56PM +1000, Con Kolivas wrote:
> > > > 1) PCI-VIA-quirk-fixup-additional-PCI-IDs.patch
>
> that shouldn't break things, if it does I *really* want to know
>
> > > > 2)
> >
> > PCI-quirk-VIA-IRQ-fixup-should-only-run-for-VIA-southbridges.patch
>
> nor should that, so again i would like to know if this is the one that
> makes a difference
>
> > > Works like a charm. End of the sound skips.
>
> what cpu/mainboard/etc
It is the 2nd patch
(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.
Because I was too lazy to make a new patch which backs out only the 2nd patch
(PCI-quirk-VIA-IRQ-fixup-should-only-run-for-VIA-southbridges.patch) changes,
I still have not confirmed if its the 2nd patch alone that is causing
breakage, or if its a combination of both of them.
It took me a long time to track down this problem, as I was spending all my
time looking at alsa related stuff, but then we finally found that it was
infact anything above the 2.6.16.17 stable release that was breaking things.
The obvious first target was to backout the VIA related changes made in the
2.6.16.17 release and bingo.... my testers with VIA chipsets were happy
again....
--
*ocilent1
next prev parent reply other threads:[~2006-06-18 4:05 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 [this message]
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
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=200606181204.29626.ocilent1@gmail.com \
--to=ocilent1@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=cw@f00f.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--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