From: Mark Hounschell <markh@compro.net>
To: markh@compro.net, Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Daniel Walker <dwalker@mvista.com>
Subject: Re: rt20 patch question
Date: Thu, 11 May 2006 07:25:15 -0400 [thread overview]
Message-ID: <44631F1B.8000100@compro.net> (raw)
In-Reply-To: <44623ED4.1030103@compro.net>
Mark Hounschell wrote:
> Steven Rostedt wrote:
>>> Configured for "Preempable Kernel" I got the following but no "stops"
>>> came with it.
>>
>> Hmm, do you have "Compile kernel with frame pointers" turned on. It's in
>> kernel hacking. It usually gives a better stack trace.
>>
>
> I'll turn frame pointers on on this machine and do it again and then
> also send you (off list) the logdev stuff you asked for from another
> machine that is configured complete-preempt.
>
This is with frame pointers on but doesn't look any more revealing to
me. After this one my network connection into the emulation was broken
BTW. And yes hard and soft irqs are threaded, preemptable-kernel, and
classic RCU
BUG: scheduling while atomic: softirq-timer/1/0x00000100/15
caller is schedule+0x33/0xf0
[<b01041c9>] show_trace+0xd/0xf (8)
[<b01041e2>] dump_stack+0x17/0x19 (12)
[<b03112ec>] __schedule+0x517/0x95b (96)
[<b031188f>] schedule+0x33/0xf0 (28)
[<b014381f>] synchronize_irq+0x94/0xb9 (40)
[<b0143943>] disable_irq+0x31/0x35 (16)
[<f0a12715>] vortex_timer+0xa1/0x55b [3c59x] (72)
[<b01261d5>] run_timer_softirq+0x1ce/0x3de (56)
[<b012212c>] ksoftirqd+0x110/0x1cb (60)
[<b012f851>] kthread+0xc8/0xcc (32)
[<b0100e15>] kernel_thread_helper+0x5/0xb (268935196)
I hope it was OK to add Ingo to the CC list?
Mark
next prev parent reply other threads:[~2006-05-11 11:25 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 12:23 rt20 patch question Mark Hounschell
2006-05-09 14:38 ` Daniel Walker
2006-05-09 14:58 ` Mark Hounschell
2006-05-09 15:53 ` Daniel Walker
2006-05-10 12:39 ` Steven Rostedt
2006-05-10 13:06 ` Mark Hounschell
2006-05-10 14:10 ` Steven Rostedt
2006-05-10 15:33 ` Mark Hounschell
2006-05-10 16:17 ` Steven Rostedt
2006-05-10 18:30 ` Mark Hounschell
2006-05-10 18:49 ` Steven Rostedt
2006-05-10 19:28 ` Mark Hounschell
2006-05-11 11:25 ` Mark Hounschell [this message]
2006-05-11 12:01 ` Steven Rostedt
2006-05-11 12:22 ` Steven Rostedt
2006-05-11 13:02 ` Mark Hounschell
2006-05-11 13:14 ` Steven Rostedt
2006-05-11 13:26 ` Mark Hounschell
2006-05-11 13:53 ` Steven Rostedt
2006-05-11 14:57 ` Mark Hounschell
2006-05-12 6:47 ` Steven Rostedt
2006-05-12 7:33 ` Sébastien Dugué
2006-05-12 8:18 ` Mark Hounschell
2006-05-12 9:08 ` Mark Hounschell
2006-05-12 9:20 ` Steven Rostedt
2006-05-10 20:33 ` Steven Rostedt
2006-05-12 8:16 ` Ingo Molnar
2006-05-12 8:45 ` Steven Rostedt
2006-05-12 9:16 ` Ingo Molnar
2006-05-12 9:21 ` Ingo Molnar
2006-05-12 12:38 ` Mark Hounschell
2006-05-12 13:18 ` Steven Rostedt
2006-05-12 13:38 ` Mark Hounschell
2006-05-12 13:43 ` Mark Hounschell
2006-05-12 14:05 ` Steven Rostedt
2006-05-12 14:36 ` Mark Hounschell
2006-05-12 14:51 ` Steven Rostedt
2006-05-12 13:16 ` 3c59x vortex_timer rt hack (was: rt20 patch question) Steven Rostedt
2006-05-12 13:36 ` Ingo Molnar
2006-05-12 13:46 ` Steven Rostedt
2006-05-12 14:16 ` Andrew Morton
2006-05-12 14:32 ` Steven Rostedt
2006-05-12 14:39 ` Steven Rostedt
2006-05-12 14:43 ` Ingo Molnar
2006-05-12 14:49 ` Andrew Morton
2006-05-12 15:04 ` Steven Rostedt
2006-05-12 16:53 ` 3c59x vortex_timer rt hack Mark Hounschell
2006-05-12 15:22 ` 3c59x vortex_timer rt hack (was: rt20 patch question) Steven Rostedt
2006-05-12 15:23 ` Andrew Morton
2006-05-12 15:36 ` Steven Rostedt
2006-05-12 16:03 ` Andrew Morton
2006-05-12 16:11 ` Steven Rostedt
2006-05-12 16:27 ` Andrew Morton
2006-05-12 16:38 ` Steven Rostedt
2006-05-10 18:45 ` rt20 patch question Steven Rostedt
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=44631F1B.8000100@compro.net \
--to=markh@compro.net \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.