[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200801171811.34641.m.kozlowski@tuxland.pl>
Date: Thu, 17 Jan 2008 18:11:33 +0100
From: Mariusz Kozlowski <m.kozlowski@...land.pl>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
RT <linux-rt-users@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.24-rc7-rt2
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.
Regards,
Mariusz
> > [<c0100e35>] cpu_idle+0x6d/0x82
> > [<c0323b6e>] rest_init+0x66/0x68
> > [<c043aba6>] start_kernel+0x20c/0x276
> > [<00000000>] 0x0
> > =======================
> > ---------------------------
> > | preempt count: 00000000 ]
> > | 0-level deep critical section nesting:
> > ----------------------------------------
> >
> > Box runs fine though.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists