All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] quick ia64 patch for 2.5.44 (UP only)
Date: Fri, 25 Oct 2002 23:23:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805255@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805243@msgid-missing>

Hi,

I found that functions in timer.c and rcupdate.c are calling
tasklet_init() for all CPUs before APs start running.
I think per_cpu() cannot be used for not running CPU for ia64,
and this assumption was broken by them.

I attached args for tasklet_init() at booting and you can see
tasklet structures for CPU#0 are only valid.
Caller might be init_timers() and rcu_init().

I cannot come up with good solution for it but I think
we have to change current per_cpu implementation.
Any idea?

Thanks,
Kimi

enter tasklet_init tà00000100000180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init t 00000000008180, funcà00000004a2e340
enter tasklet_init tà00000100000158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100
enter tasklet_init t 00000000008158, funcà00000004a2c100


On Fri, 25 Oct 2002 14:50:33 -0700
Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp> wrote:

> I found that tasklet_hi_action() seemed to call NULL pointer.
> So I tried to put following code (I guess this is wrong fix)
> into the function;
> 
> 	if (t->func = NULL) {
> 		tasklet_unlock(t);
> 		continue;
> 	}
> 
> And the system initialization moved on, but it hung at INIT execution.
> Anyway, I feel this problem might be related to the timer change.
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m\x103393743102152&w=2

-- 
Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>



  parent reply	other threads:[~2002-10-25 23:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25  5:35 [Linux-ia64] quick ia64 patch for 2.5.44 (UP only) David Mosberger
2002-10-25 21:50 ` Kimio Suganuma
2002-10-25 23:23 ` Kimio Suganuma [this message]
2002-10-26  1:09 ` Kimio Suganuma
2002-10-27 16:42 ` Kimio Suganuma
2002-10-27 17:13 ` Erich Focht
2002-10-27 23:57 ` Peter Chubb
2002-10-28  0:51 ` Kimio Suganuma
2002-10-28  1:51 ` Peter Chubb
2002-10-28  3:02 ` David Mosberger
2002-10-28 17:12 ` Luck, Tony

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=marc-linux-ia64-105590709805255@msgid-missing \
    --to=k-suganuma@mvj.biglobe.ne.jp \
    --cc=linux-ia64@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.