All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: aivils@unibanka.lv
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: kernel/softirq.c issues under 2.6.5
Date: Wed, 21 Apr 2004 08:21:18 +1000	[thread overview]
Message-ID: <1082499674.16618.3.camel@bach> (raw)
In-Reply-To: <200404201058.12830.aivils@unibanka.lv>

On Tue, 2004-04-20 at 17:58, Aivils wrote:
> Hi all!
> 
> 	My 2.6.5 will not start until i applay patch bellow:
> --- linux-2.6.5/kernel/softirq.c        2004-04-04 06:36:47.000000000 +0300
> +++ linux-2.6.5/kernel/softirq.chg.c    2004-04-20 10:48:28.000000000 +0300
> @@ -409,8 +409,8 @@ static int __devinit cpu_callback(struct
> 
>         switch (action) {
>         case CPU_UP_PREPARE:
> -               BUG_ON(per_cpu(tasklet_vec, hotcpu).list);
> -               BUG_ON(per_cpu(tasklet_hi_vec, hotcpu).list);
> +               per_cpu(tasklet_vec, cpu).list = NULL;
> +               per_cpu(tasklet_hi_vec, cpu).list = NULL;
>                 p = kthread_create(ksoftirqd, hcpu, "ksoftirqd/%d", hotcpu);
>                 if (IS_ERR(p)) {
>                         printk("ksoftirqd for %i failed\n", hotcpu);

This patch should be completely unnecessary.

One possibility is that your compiler isn't obeying the section
attribute for some reason.  Please send .config and output of "gcc -v".

Thanks!
Rusty.
-- 
Anyone who quotes me in their signature is an idiot -- Rusty Russell


  reply	other threads:[~2004-04-20 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20  7:58 kernel/softirq.c issues under 2.6.5 Aivils
2004-04-20 22:21 ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-24 11:00 Zoltan Boszormenyi
2004-04-27  3:25 ` Rusty Russell

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=1082499674.16618.3.camel@bach \
    --to=rusty@rustcorp.com.au \
    --cc=aivils@unibanka.lv \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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.