From: Andrew McGregor <andrew@indranet.co.nz>
To: Con Kolivas <kernel@kolivas.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: xmms (audio) skipping in 2.5 (not 2.4)
Date: Tue, 04 Mar 2003 23:00:46 +1300 [thread overview]
Message-ID: <84002989.1046818846@[192.168.0.1]> (raw)
In-Reply-To: <200303041915.43743.kernel@kolivas.org>
Per chance, do you have an NVidia graphics card and Maestro 3 or USB audio?
If so, you're possibly getting DMA starvation. There are games you can
play with the PCI latency timers to help with this, but I cannot recall the
details; searching around for Dell Inspiron laptop audio issues might find
them. I just replaced the machine I saw this on, so I can't help anymore.
Andrew
--On Tuesday, 4 March 2003 7:15 p.m. +1100 Con Kolivas <kernel@kolivas.org>
wrote:
> On Tue, 4 Mar 2003 06:48 pm, Martin J. Bligh wrote:
>> >> >> So ... is there any easy way I can diagnose this? Does anyone else
>> >> >> have a similar problem?
>> >> >
>> >> > Most of us who have worked with an O(1) scheduler based kernel have
>> >> > found this at various times. See the previous discussion with akpm
>> >> > about the interactivity estimator. Akpm found that decreasing the
>> >> > maximum timeslice duration would blunt the effect of the
>> >> > interactivity estimator giving preference to the "wrong" task. In
>> >> > 2.4.20-ck4 I avoid this problem with the "desktop tuning" of
>> >> > making the max timeslice==min timeslice. Try an -mm kernel with
>> >> > the scheduler tunables patch and try playing with the max
>> >> > timeslice. Most have found that <=25 will usually stop these skips.
>> >> > The default max timeslice of 300ms is just too long for the
>> >> > desktop and interactivity estimator.
>> >>
>> >> Heh, cool. I have the same patch in my tree too, fixed it without
>> >> rebooting even ;-) Still a *tiny* bit of skipping, but infinitely
>> >> better than it was.
>> >
>> > Try decreasing prio_bonus_ratio to 15 as well
>>
>> Doesn't seem to make much difference, actually.
>> But "waggle scrollbar a bit" isn't very scientific .. ;-)
>> Does contest (or anything else) measure this kind of thing more
>> precisely?
>
> Last time I tried to do a whole swag of tunables it was showing
> differences but I was plagued by memory leaks ruining the data. I'll try
> again in the near future. Also Bill Davidsen's trivial response
> benchmark may show something too.
>
> Con
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2003-03-04 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 5:25 Martin J. Bligh
2003-03-04 5:36 ` Con Kolivas
2003-03-04 5:52 ` Martin J. Bligh
2003-03-04 7:28 ` Con Kolivas
2003-03-04 7:48 ` Martin J. Bligh
2003-03-04 8:15 ` Con Kolivas
2003-03-04 10:00 ` Andrew McGregor [this message]
2003-03-04 15:59 ` Martin J. Bligh
2003-03-12 22:59 ` Pavel Machek
2003-03-12 23:42 ` Martin J. Bligh
2003-03-04 9:48 ` Giuliano Pochini
2003-03-04 14:13 ` Anton Blanchard
2003-03-04 14:18 ` Maciej Soltysiak
2003-03-04 14:31 ` Sean Neakums
2003-03-04 16:17 ` Martin J. Bligh
2003-03-04 18:39 ` Aaron Lehmann
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='84002989.1046818846@[192.168.0.1]' \
--to=andrew@indranet.co.nz \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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
all inboxes | Powered by JetHome®