From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261453AbULAV3v (ORCPT ); Wed, 1 Dec 2004 16:29:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261458AbULAV3v (ORCPT ); Wed, 1 Dec 2004 16:29:51 -0500 Received: from mx2.elte.hu ([157.181.151.9]:63971 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261453AbULAV3o (ORCPT ); Wed, 1 Dec 2004 16:29:44 -0500 Date: Wed, 1 Dec 2004 22:29:25 +0100 From: Ingo Molnar To: Rui Nuno Capela Cc: linux-kernel@vger.kernel.org, Lee Revell , mark_h_johnson@raytheon.com, "K.R. Foley" , Bill Huey , Adam Heath , Florian Schmidt , Thomas Gleixner , Michal Schmidt , Fernando Pablo Lopez-Lezcano , Karsten Wiese , Gunther Persoons , emann@mrv.com, Shane Shrybman , Amit Shah , Esben Nielsen , Andrew Morton Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-19 Message-ID: <20041201212925.GA23410@elte.hu> References: <20041129152344.GA9938@elte.hu> <48590.195.245.190.94.1101810584.squirrel@195.245.190.94> <20041130131956.GA23451@elte.hu> <17532.195.245.190.94.1101829198.squirrel@195.245.190.94> <20041201103251.GA18838@elte.hu> <32831.192.168.1.5.1101905229.squirrel@192.168.1.5> <20041201154046.GA15244@elte.hu> <20041201160632.GA3018@elte.hu> <20041201162034.GA8098@elte.hu> <33059.192.168.1.5.1101927565.squirrel@192.168.1.5> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <33059.192.168.1.5.1101927565.squirrel@192.168.1.5> User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-4.9, required 5.9, autolearn=not spam, BAYES_00 -4.90 X-ELTE-SpamLevel: X-ELTE-SpamScore: -4 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Rui Nuno Capela wrote: > > i think i found the bug - it's an upstream ACPI bug. Does the patch > > below (or the -31-19 kernel, which i've just uploaded) fix the xruns? > > > > So far so good. > > I have now an armed RT-V0.31-19 on my laptop, running for about 30 > minutes already, running the usual 'jackd -R -dalsa -dhw:0 -r44100 > -p64 -n2 -S -P' from qjackctl, several qsynth (fluidsynth) engines are > up and running, normal desktop janitor work (KDE) and yes, ACPI is on. > Oh, wi-fi is also pumping nice :) > > Guess what? No XRUNs, not even one to show you a single latency trace. > > I'll keep you posted, if anything goes less right than it is :). great - it seems the ACPI fix made a difference. If there are no xruns then you might want to try the # of engines at which point xruns show up. (can the soundcard period size / buffering be reduced further, to make it more sensitive to scheduling latencies?) Ingo