All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [patch] logical CPU numbering
Date: Thu, 17 Apr 2003 20:25:21 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705542@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705277@msgid-missing>


On Thu, Apr 17, 2003 at 01:13:44PM -0600, Bjorn Helgaas wrote:
> On Thursday 03 April 2003 11:31 am, Martin Hicks wrote:
> > This patch should be applied.  I finally got around to doing some more
> > testing with it.  If a CPU fails to start, currently we get messages
> > like the following for subsequent CPU's:
> > 
> > 
> > CPU 17: nasid 18, slice 0, cnode 9
> > CPU 17: base freq 0.000MHz, ITC ratio\x10/2, ITC freq\x1000.000MHz
> > Calibrating delay loop... 1494.72 BogoMIPS
> > phys CPU#17 (0x12) not responding - cannot use it.               <<-BOGUS
> 
> I don't quite understand how this works.  The current code is clearly
> wrong, but if the AP in a 2-CPU system fails to start, won't the new
> code print "phys CPU#0 not responding"?  That doesn't seem accurate.
> 
> If we really need this printk, it seems like the logical place to put it
> would be in do_boot_cpu(), where we already print the "Processor X/Y
> is stuck" message.  2.5 seems to have just removed the "not responding"
> printk, though, and I'd be inclined to do the same.  Any objections?

I have no objections.

mh

-- 
Wild Open Source Inc.                  mort@wildopensource.com


      parent reply	other threads:[~2003-04-17 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 19:03 [Linux-ia64] [patch] logical CPU numbering Martin Hicks
2003-03-20 20:07 ` Wichmann, Mats D
2003-03-25 18:03 ` Martin Hicks
2003-04-03 18:31 ` Martin Hicks
2003-04-17 19:13 ` Bjorn Helgaas
2003-04-17 20:25 ` Martin Hicks [this message]

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-105590723705542@msgid-missing \
    --to=mort@wildopensource.com \
    --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.