From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261587AbVF1JM5 (ORCPT ); Tue, 28 Jun 2005 05:12:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261870AbVF1JM4 (ORCPT ); Tue, 28 Jun 2005 05:12:56 -0400 Received: from mx2.elte.hu ([157.181.151.9]:32642 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261587AbVF1JMi (ORCPT ); Tue, 28 Jun 2005 05:12:38 -0400 Date: Tue, 28 Jun 2005 11:12:22 +0200 From: Ingo Molnar To: Steven Rostedt Cc: Daniel Walker , Chuck Harding , Linux Kernel Discussion List Subject: Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24 Message-ID: <20050628091222.GA30629@elte.hu> References: <20050608112801.GA31084@elte.hu> <20050625091215.GC27073@elte.hu> <200506250919.52640.gene.heskett@verizon.net> <200506251039.14746.gene.heskett@verizon.net> <1119902991.4794.5.camel@dhcp153.mvista.com> <20050628081843.GA16455@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050628081843.GA16455@elte.hu> User-Agent: Mutt/1.4.2.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 * Ingo Molnar wrote: > * Steven Rostedt wrote: > > > Although turning off apm works, this is a fix to the symptom and not a > > cure. Has someone already taken a look at this code? Since > > apm_bios_call_simple calls local_save_flags and afterwards > > raw_lock_irq_restore is then called. Shouldn't that have been > > raw_local_save_flags? > > ah, indeed. I fixed this bug and have uploaded the -50-26 patch. > Chuck, does this fix the APM problems for you? i've also uploaded -50-27 in which i've improved the irq-flags debugging code. They are activated if CONFIG_DEBUG_PREEMPT is enabled, and can come in two variants of kernel messages: BUG: bad raw irq-flag value 80000000, test/3810! BUG: bad soft irq-flag value 00000202, test/3810! so we should now be able to detect mismatches of irq flags right where they occur. Ingo