From: Steven Rostedt <rostedt@goodmis.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.15-rt12 bugs
Date: Mon, 23 Jan 2006 19:24:57 -0500 [thread overview]
Message-ID: <1138062297.6695.3.camel@localhost.localdomain> (raw)
In-Reply-To: <6bffcb0e0601230521l59b8360et@mail.gmail.com>
On Mon, 2006-01-23 at 14:21 +0100, Michal Piotrowski wrote:
> Hi,
>
> I have noticed some bugs in latest 2.6.15-rt12, here are some of them:
> http://www.stardust.webpages.pl/files/rt/2.6.15-rt12/rt-dmesg
The only bug I see in this is:
BUG: kstopmachine:338 task might have lost a preemption check!
[<c0103b1b>] dump_stack+0x1b/0x1f (20)
[<c0118736>] preempt_enable_no_resched+0x4a/0x50 (20)
[<c014224d>] restart_machine+0x1a/0x1d (12)
[<c0142274>] do_stop+0x24/0x65 (20)
[<c012d6de>] kthread+0x7b/0xa9 (36)
[<c01010c5>] kernel_thread_helper+0x5/0xb (135438364)
Which I'll go and take a look at. I need to turn on
CONFIG_DEBUG_PREEMPT on my SMP machine.
> Here is my config:
> http://www.stardust.webpages.pl/files/rt/2.6.15-rt12/rt-config
You might want to turn off:
CONFIG_DEBUG_STACKOVERFLOW
This dumps out the biggest stack usage. Those dumps are caused by this,
and are not bugs. It just shows you what's using the most stack, that's
all. I find it quite annoying, and just turn it off.
-- Steve
next prev parent reply other threads:[~2006-01-24 0:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 13:21 2.6.15-rt12 bugs Michal Piotrowski
2006-01-24 0:24 ` Steven Rostedt [this message]
2006-01-24 1:23 ` [PATCH RT] kstopmachine has legit preempt_enable_no_resched (was: 2.6.15-rt12 bugs) Steven Rostedt
2006-01-24 7:45 ` Ingo Molnar
2006-01-24 13:33 ` Michal Piotrowski
2006-01-24 14:19 ` Steven Rostedt
2006-01-24 15:37 ` Michal Piotrowski
2006-01-24 18:11 ` Steven Rostedt
2006-01-24 21:00 ` Michal Piotrowski
2006-01-24 21:17 ` Steven Rostedt
2006-01-26 17:47 ` Michal Piotrowski
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=1138062297.6695.3.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
/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