Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964964AbVJDUic (ORCPT ); Tue, 4 Oct 2005 16:38:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964965AbVJDUic (ORCPT ); Tue, 4 Oct 2005 16:38:32 -0400 Received: from xproxy.gmail.com ([66.249.82.205]:25462 "EHLO xproxy.gmail.com") by vger.kernel.org with ESMTP id S964964AbVJDUib convert rfc822-to-8bit (ORCPT ); Tue, 4 Oct 2005 16:38:31 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oNGZvLp8YL9SmY2oZHHXPuPQqAmO8BJGyRXgjgoqAvxSAWvifzDzaiG8Carhos1yvLoC55Lz8kjgFZYEhNhLvLKod1pxdtGCMLPIRW2HASDGIFjaPdeuQ2xXO0gM5RRbBcU5LVSGH7Gi7eL9ExLjLmCIq80aBx9O2G/Saf5aKNU= Message-ID: <5bdc1c8b0510041338n61bb5320qc47906d8e9ed7285@mail.gmail.com> Date: Tue, 4 Oct 2005 13:38:30 -0700 From: Mark Knecht Reply-To: Mark Knecht To: tglx@linutronix.de Subject: Re: 2.6.14-rc3-rt2 Cc: linux-kernel@vger.kernel.org In-Reply-To: <1128450029.13057.60.camel@tglx.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-Disposition: inline References: <20051004084405.GA24296@elte.hu> <43427AD9.9060104@cybsft.com> <20051004130009.GB31466@elte.hu> <5bdc1c8b0510040944q233f14e6g17d53963a4496c1f@mail.gmail.com> <5bdc1c8b0510041111n188b8e14lf5a1398406d30ec4@mail.gmail.com> <1128450029.13057.60.camel@tglx.tec.linutronix.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2815 Lines: 77 On 10/4/05, Thomas Gleixner wrote: > On Tue, 2005-10-04 at 11:11 -0700, Mark Knecht wrote: > > > I have now had one burst of xruns. As best I can tell I was > > downloading some video files for mplayer to look at, or possibly > > running one of them. I see this in qjackctl: > > > > I guess its related to the priority leak I'm tracking down right now. > Can you please set following config options and check if you get a bug > similar to this ? > > BUG: init/1: leaked RT prio 98 (116)? > Thomas, As per the config options I could actually get turned on I see something different: Detected 12.564 MHz APIC timer. Brought up 1 CPUs time.c: Using PIT/TSC based timekeeping. testing NMI watchdog ... OK. NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 PCI: Using MMCONFIG at e0000000 ACPI: Subsystem revision 20050902 BUG: swapper/1: spin-unlock irq flags assymetry? Call Trace:{_spin_unlock_irqrestore+89} {acpi_ev_create_gpe_block+642} {acpi_os_wait_semaphore+135} {acpi_ev_gpe_initialize+109} {acpi_ev_initialize_events+151} {acpi_enable_subsystem+69} {acpi_init+86} {init_bio+266} {init+506} {child_rip+8} {init+0} {child_rip+0} --------------------------- | preempt count: 00000000 ] | 0-level deep critical section nesting: ---------------------------------------- WARNING: swapper/1 changed soft IRQ-flags. Call Trace:{local_irq_enable+26} {_spin_unlock_irqrestore+101} {acpi_ev_create_gpe_block+642} {acpi_os_wait_semaphore+135} {acpi_ev_gpe_initialize+109} {acpi_ev_initialize_events+151} {acpi_enable_subsystem+69} {acpi_init+86} {init_bio+266} {init+506} {child_rip+8} {init+0} {child_rip+0} --------------------------- | preempt count: 00000000 ] | 0-level deep critical section nesting: ---------------------------------------- ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) I'll do a bit more testing and wait to hear about the data above. Cheers, Mark - 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/