From: Mark Hounschell <markh@compro.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Daniel Walker <dwalker@mvista.com>
Subject: Re: rt20 patch question
Date: Wed, 10 May 2006 14:30:47 -0400 [thread overview]
Message-ID: <44623157.9090105@compro.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0605101215220.19935@gandalf.stny.rr.com>
Steven Rostedt wrote:
> Wow! I asked for some info on your system, and boy, did I get info! :)
>
Sorry. I talk to much.
>> I can only say for sure that I do not have these "stops" when running
>> any other kernel or when running the rt20 kernel in any of the
>> non-complete preemption modes.
>>
Configured for "Preempable Kernel" I got the following but no "stops"
came with it.
BUG: scheduling while atomic: softirq-timer/1/0x00000100/15
caller is schedule+0x33/0xf0
[<b0309acc>] __schedule+0x517/0x95b (8)
[<f09d7627>] mdio_ctrl+0xaa/0x135 [e100] (48)
[<f09d7627>] mdio_ctrl+0xaa/0x135 [e100] (12)
[<b030a06c>] schedule+0x33/0xf0 (36)
[<b012eee5>] prepare_to_wait+0x12/0x4f (8)
[<b0142318>] synchronize_irq+0x96/0xba (20)
[<b012eda0>] autoremove_wake_function+0x0/0x37 (12)
[<f0a13677>] vortex_timer+0xa0/0x563 [3c59x] (24)
[<b0125b76>] __mod_timer+0x8c/0xc3 (12)
[<f09d8998>] e100_watchdog+0x0/0x39c [e100] (24)
[<b030a4cf>] cond_resched_softirq+0x64/0xaa (8)
[<b02a2dcd>] dev_watchdog+0x77/0xac (4)
[<f0a135d7>] vortex_timer+0x0/0x563 [3c59x] (12)
[<b0125902>] run_timer_softirq+0x1bf/0x3a7 (8)
[<b0121960>] ksoftirqd+0x112/0x1cc (52)
[<b012184e>] ksoftirqd+0x0/0x1cc (52)
[<b012eb9c>] kthread+0xc2/0xc6 (4)
[<b012eada>] kthread+0x0/0xc6 (12)
[<b0100e35>] kernel_thread_helper+0x5/0xb (16)
Mark
next prev parent reply other threads:[~2006-05-10 18:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 12:23 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 [this message]
2006-05-10 18:49 ` Steven Rostedt
2006-05-10 19:28 ` Mark Hounschell
2006-05-11 11:25 ` Mark Hounschell
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=44623157.9090105@compro.net \
--to=markh@compro.net \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome