Return-Path: <linux-kernel-owner+w=401wt.eu-S1755543AbYAQR5Z@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755543AbYAQR5Z (ORCPT <rfc822;w@1wt.eu>);
	Thu, 17 Jan 2008 12:57:25 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752203AbYAQR5R
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 17 Jan 2008 12:57:17 -0500
Received: from xdsl-664.zgora.dialog.net.pl ([81.168.226.152]:1317 "EHLO
	tuxland.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751598AbYAQR5Q (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 17 Jan 2008 12:57:16 -0500
From: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
To: Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 2.6.24-rc7-rt2
Date: Thu, 17 Jan 2008 18:57:10 +0100
User-Agent: KMail/1.9.7
Cc: LKML <linux-kernel@vger.kernel.org>, RT <linux-rt-users@vger.kernel.org>,
       Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
References: <1200336080.318.8.camel@localhost.localdomain> <200801171811.34641.m.kozlowski@tuxland.pl> <Pine.LNX.4.58.0801171223430.24969@gandalf.stny.rr.com>
In-Reply-To: <Pine.LNX.4.58.0801171223430.24969@gandalf.stny.rr.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200801171857.11837.m.kozlowski@tuxland.pl>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1954
Lines: 57

Hello,

> > > > I found this in dmesg:
> > > >
> > > > BUG: swapper:0 task might have lost a preemption check!
> > > > Pid: 0, comm: swapper Not tainted 2.6.24-rc7-rt2 #3
> > > >  [<c010386b>] show_trace_log_lvl+0x1d/0x3b
> > > >  [<c01042f3>] show_trace+0x12/0x14
> > > >  [<c0104a2f>] dump_stack+0x6a/0x70
> > > >  [<c0115419>] preempt_enable_no_resched+0x5c/0x5e
> > >
> > > This is really really strange. cpu_idle calls __preempt_enable_no_resched
> > > and not preempt_enable_no_resched (notice the prefixed underscores).
> > > So I don't know how you got that output. Did you get any strance rejects
> > > in applying this patch?
> >
> > Nope. Your rt patch applied cleanly to vanilla 2.6.24-rc7.
> >
> 
> OK, do you still get this message? Also I'm assuming this is x86, right?
> 
> Could you also do the following.
> 
> Go into your kernel build directory.
> Start up gdb (I'm hoping that you compiled with DEBUG_INFO)
>   gdb vmlinux
> (gdb) li *0xc0100e35
> 
> and show me what you get.

Oh crap. You are totaly right. I messed with quilt on that tree to bisect that thing
with LOCKDEP. A few patches from rt series were left unapplied somehow :/ Sorry for
the noise then.

Regards,

	Mariusz

BTW this is the gdb output which ofcourse is bogus.

(gdb) l*0xc0100e35
0xc0100e35 is in cpu_idle (arch/x86/kernel/process_32.c:203).
198                             __get_cpu_var(irq_stat).idle_timestamp = jiffies;
199                             idle();
200                     }
201                     tick_nohz_restart_sched_tick();
202                     preempt_enable_no_resched();
203                     schedule();
204                     preempt_disable();
205             }
206     }
207   
--
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/