Re: rt20 patch question

[Steven Rostedt]

On Wed, 10 May 2006, Mark Hounschell wrote:

> Steven Rostedt wrote:
> > Wow! I asked for some info on your system, and boy, did I get info! :)
> >
>
> Sorry. I talk to much.

No, by all means, I liked it.

>
> >> 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.

Hmm, do you have "Compile kernel with frame pointers" turned on. It's in
kernel hacking. It usually gives a better stack trace.

>
> 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)

I'll look into this.

-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/