All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: ck@vds.kolivas.org
Cc: Hugo Vanwoerkom <rociobarroso@att.net.mx>,
	ocilent1@gmail.com, linux list <linux-kernel@vger.kernel.org>,
	Chris Wedgwood <cw@f00f.org>
Subject: sound skips on 2.6.16.17
Date: Sat, 17 Jun 2006 21:29:56 +1000	[thread overview]
Message-ID: <200606172129.56986.kernel@kolivas.org> (raw)
In-Reply-To: <4493D24D.2010902@att.net.mx>

On Saturday 17 June 2006 19:58, Hugo Vanwoerkom wrote:
> ocilent1 wrote:
> > You don't happen to use a VIA chipset do you? For PCLinuxOS kernels, I
> > found that a few people with VIA based mobos started experiencing
> > sound problems (skipping / stuttering) once we hit 2.6.16.17. Backing out
> > the following 2 patches added in 2.6.16.17 seem to fix the problems.
> >
> > 1)  PCI-VIA-quirk-fixup-additional-PCI-IDs.patch
> > 2)  PCI-quirk-VIA-IRQ-fixup-should-only-run-for-VIA-southbridges.patch
> >
> > I have attached some patches you might want to try that reverse out the
> > above patches. You will need to apply the patches in the correct order
> > (as above)

> Works like a charm. End of the sound skips.

Not sure if this has been reported to lkml so I'm cc'ing it here and the 
stable maintainer.

-- 
-ck

       reply	other threads:[~2006-06-17 11:30 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     ` Con Kolivas [this message]
2006-06-18  2:41       ` sound skips on 2.6.16.17 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
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=200606172129.56986.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.org \
    --cc=cw@f00f.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 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.