The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH RT] kstopmachine has legit preempt_enable_no_resched (was: 2.6.15-rt12 bugs)
Date: Tue, 24 Jan 2006 14:33:11 +0100	[thread overview]
Message-ID: <6bffcb0e0601240533h3ba1a01ci@mail.gmail.com> (raw)
In-Reply-To: <1138065822.6695.6.camel@localhost.localdomain>

Hi,

On 24/01/06, Steven Rostedt <rostedt@goodmis.org> wrote:
> Here Ingo,
>
> The kstop_machine has a legitimate preempt_enable_no_resched.
>
> -- Steve
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
> Index: linux-2.6.15-rt12/kernel/stop_machine.c
> ===================================================================
> --- linux-2.6.15-rt12.orig/kernel/stop_machine.c        2006-01-23 09:15:37.000000000 -0500
> +++ linux-2.6.15-rt12/kernel/stop_machine.c     2006-01-23 19:58:26.000000000 -0500
> @@ -134,7 +134,7 @@
>  {
>         stopmachine_set_state(STOPMACHINE_EXIT);
>         raw_local_irq_enable();
> -       preempt_enable_no_resched();
> +       __preempt_enable_no_resched();
>  }
>
>  struct stop_machine_data
>
>
>

Great thanks!

Now 2.6.15-rt14 works fine (after disabling CONFIG_DEBUG_STACKOVERFLOW).

I have noticed only one warning
WARNING: softirq-tasklet/8 changed soft IRQ-flags.
 [<c0103b1b>] dump_stack+0x1b/0x1f (20)
 [<c0135218>] illegal_API_call+0x41/0x46 (20)
 [<c0135267>] local_irq_disable+0x1d/0x1f (8)
  [<f886dbd5>] skge_extirq+0x117/0x138 [skge] (32)
 [<c01202d5>] tasklet_action+0x8a/0xf1 (24)
  [<c01205c1>] ksoftirqd+0x10f/0x19e (32)
  [<c012d7ca>] kthread+0x7b/0xa9 (36)
 [<c01010c5>] kernel_thread_helper+0x5/0xb (1047875612)
---------------------------
| preempt count: 00000000 ]
| 0-level deep critical section nesting:
----------------------------------------

------------------------------
| showing all locks held by: |  (softirq-tasklet/8 [c18a97d0,  98]):
------------------------------

And problems while loading ipv6 module
Running ntpdate to synchronize clockCould not allocate 4 bytes percpu data
modprobe: FATAL: Error inserting ipv6
(/lib/modules/2.6.15-rt14/kernel/net/ipv6/ipv6.ko): Cannot allocate
memory

Could not allocate 4 bytes percpu data
modprobe: FATAL: Error inserting ipv6
(/lib/modules/2.6.15-rt14/kernel/net/ipv6/ipv6.ko): Cannot allocate
memory

Here is my dmesg:
http://www.stardust.webpages.pl/files/rt/2.6.15-rt14/rt-dmesg
Here is my config:
http://www.stardust.webpages.pl/files/rt/2.6.15-rt14/rt-config

Regards,
Michal Piotrowski

  parent reply	other threads:[~2006-01-24 13:33 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
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 [this message]
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=6bffcb0e0601240533h3ba1a01ci@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox