Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270757AbUJUPLz (ORCPT ); Thu, 21 Oct 2004 11:11:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270756AbUJUPIt (ORCPT ); Thu, 21 Oct 2004 11:08:49 -0400 Received: from mx1.elte.hu ([157.181.1.137]:3988 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S270747AbUJUPFh (ORCPT ); Thu, 21 Oct 2004 11:05:37 -0400 Date: Thu, 21 Oct 2004 17:06:55 +0200 From: Ingo Molnar To: Mark_H_Johnson@raytheon.com Cc: Bill Huey , Adam Heath , "K.R. Foley" , linux-kernel@vger.kernel.org, Florian Schmidt , Fernando Pablo Lopez-Lezcano , Lee Revell , Rui Nuno Capela , Thomas Gleixner , Michal Schmidt Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U8 Message-ID: <20041021150655.GA7076@elte.hu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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=-2.201, required 5.9, BAYES_00 -4.90, SORTED_RECIPS 2.70 X-ELTE-SpamLevel: X-ELTE-SpamScore: -2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1347 Lines: 31 * Mark_H_Johnson@raytheon.com wrote: > >do you have PREEMPT_REALTIME enabled? The above trace is a direct > >interrupt - only the timer interrupt is allowed to execute directly in > >the PREEMPT_REALTIME model - things break badly if it happens for any > >other interrupt (such as the soundcard IRQ). > Yes I have PREEMPT_REALTIME enabled. > > The thing that comes to mind is I do have a script that does > echo 0 > '/proc/irq/10/Esoniq AudioPCI/threaded > > as part of ensuring the all the preemption stuff was set right. I may > have run that script prior to getting those messages. I thought you > said before that the non threaded IRQ stuff was disabled. Perhaps this > interface needs to be disabled as well [unless you really decide to > fix this limitation...]. argh, there was a typo in that change so the 'threaded' flags werent really disabled. So i ended up only disabling the global hardirq_preempt flag but not the per-handler 'threaded' flags. Ouch! I've uploaded the -U9.1 patch that has the fix, does it work any better than previous kernels? Ingo - 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/