public inbox for linux-ia64@vger.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] Re: CPU hotplug boot change for IA64
Date: Tue, 06 Aug 2002 20:26:12 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905919@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905894@msgid-missing>

Hi Erich,

On Tue, 6 Aug 2002 20:33:09 +0200
Erich Focht <efocht@ess.nec.de> wrote:

> > I removed cpu_initialized and fixed several bugs.
> > I tested SMP and UP kernels on 2-way Bigsur.
> > Please let me know if there is any problem on the patch.
> 
> The patch looks fine. Before applying it to 2.5.29 my BigSur ended up
> with no tasks beeing scheduled to cpu#1 and no migration_task and
> ksoftirqd for the same cpu. But the system came up. After applying it 
> the system hangs in the boot sequence right after "Freeing unused
> kernel memory". But CPU#1 was woken up correctly. Sorry, have no kdb
> to be able to tell you more...
> 
> Does anybody else have these problems?

I had a problem that the system hang at booting on 2.5.29 without
my patch. After that, I turned off CONFIGs as much as possible
and then I succeeded to boot the kernel.
I suspect IDE/ATAPI driver or something was causing the problem
(I'm not sure, though.)
Anyway, I'd like to reproduce the problem. Could you send me your
.config?

Regards,
Kimi

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



  parent reply	other threads:[~2002-08-06 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 21:44 [Linux-ia64] Re: CPU hotplug boot change for IA64 David Mosberger
2002-08-02 22:18 ` Kimio Suganuma
2002-08-03  0:53 ` Kimio Suganuma
2002-08-03  3:29 ` Rusty Russell
2002-08-03  4:10 ` Kimio Suganuma
2002-08-05  1:19 ` Rusty Russell
2002-08-05  4:33 ` Andrew Morton
2002-08-06 18:33 ` Erich Focht
2002-08-06 20:26 ` Kimio Suganuma [this message]
2002-08-08  4:19 ` Kimio Suganuma

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-105590701905919@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox