From: Steven Rostedt <rostedt@goodmis.org>
To: "K.R. Foley" <kr@cybsft.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Lee Revell <rlrevell@joe-job.com>,
John Rigg <lk@sound-man.co.uk>
Subject: Re: 2.6.15-rc5-rt4: BUG: swapper:0 task might have lost a preemption check!
Date: Fri, 23 Dec 2005 13:45:00 -0500 [thread overview]
Message-ID: <1135363500.6652.8.camel@localhost.localdomain> (raw)
In-Reply-To: <43AC2607.1050707@cybsft.com>
On Fri, 2005-12-23 at 10:29 -0600, K.R. Foley wrote:
>
> OK. The BUG still exists (output below) but it does boot now with the
> above patch applied (THANKS Steven!), which would seem to imply the two
> weren't related. ARGH! :)
>
> Dec 23 10:16:27 porky kernel: Event source lapic installed with caps set: 06
> Dec 23 10:16:27 porky kernel: BUG: swapper:0 task might have lost a
> preemption check!
> Dec 23 10:16:27 porky kernel: Brought up 2 CPUs
> Dec 23 10:16:27 porky kernel: checking if image is initramfs... it is
> Dec 23 10:16:27 porky kernel: [<c010424e>] dump_stack+0x1e/0x20 (20)
> Dec 23 10:16:27 porky kernel: [<c011c9cf>]
> preempt_enable_no_resched+0x5f/0x70 (20)
> Dec 23 10:16:27 porky kernel: [<c0100ff2>] cpu_idle+0xb2/0x100 (40)
> Dec 23 10:16:27 porky kernel: [<c0111446>]
> start_secondary+0x296/0x340<6>Freeing initrd memory: 452k freed
>
Yeah, I've seen the "might have lost a preemption check" too. But since
this didn't seem to cause a problem booting my kernel (yet), it went to
the end of the todo list.
Does this cause any other problems?
-- Steve
next prev parent reply other threads:[~2005-12-23 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 2:55 2.6.15-rc5-rt4: BUG: swapper:0 task might have lost a preemption check! Lee Revell
2005-12-23 3:14 ` K.R. Foley
2005-12-23 15:37 ` Steven Rostedt
2005-12-23 16:29 ` K.R. Foley
2005-12-23 18:37 ` Lee Revell
2005-12-23 18:45 ` Steven Rostedt [this message]
2005-12-23 18:51 ` K.R. Foley
2005-12-23 17:47 ` John Rigg
2005-12-23 20:38 ` Steven Rostedt
2005-12-23 21:19 ` John Rigg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1135363500.6652.8.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@sound-man.co.uk \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox