From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261154AbVF0UJ7 (ORCPT ); Mon, 27 Jun 2005 16:09:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261473AbVF0UJ7 (ORCPT ); Mon, 27 Jun 2005 16:09:59 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:2806 "EHLO av.mvista.com") by vger.kernel.org with ESMTP id S261154AbVF0UJ5 (ORCPT ); Mon, 27 Jun 2005 16:09:57 -0400 Subject: Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24 From: Daniel Walker Reply-To: dwalker@mvista.com To: Chuck Harding Cc: Linux Kernel Discussion List In-Reply-To: References: <20050608112801.GA31084@elte.hu> <20050625091215.GC27073@elte.hu> <200506250919.52640.gene.heskett@verizon.net> <200506251039.14746.gene.heskett@verizon.net> Content-Type: text/plain Organization: MontaVista Date: Mon, 27 Jun 2005 13:09:51 -0700 Message-Id: <1119902991.4794.5.camel@dhcp153.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2005-06-27 at 12:01 -0700, Chuck Harding wrote: > What can be causing the following message to appear in dmesg and > how can I fix it? > > BUG: scheduling with irqs disabled: kapmd/0x00000000/46 > caller is schedule_timeout+0x51/0x9e > [] schedule+0x96/0xf6 (8) > [] schedule_timeout+0x51/0x9e (28) > [] process_timeout+0x0/0x5 (32) > [] apm_mainloop+0x7a/0x96 (24) > [] default_wake_function+0x0/0x16 (12) > [] default_wake_function+0x0/0x16 (32) > [] apm_driver_version+0x1c/0x38 (16) > [] apm+0x0/0x289 (8) > [] apm+0xaf/0x289 (8) > [] kernel_thread_helper+0x0/0xb (20) > [] kernel_thread_helper+0x5/0xb (4) > > This was also present in earlier final-V0.7.50 version I've tried > (since -00) I don't get hangs but that doesn't look like it should > be happening. Thanks. If you have PREEMPT_RT enabled, it looks like interrupts are hard disabled then there is a schedule_timeout() requested. You could try turning off power management and see if you still have problems. Daniel