From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Detecting SMP in user space
Date: Thu, 19 Apr 2001 14:21:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005431@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005429@msgid-missing>
Andreas-
On my system the boot messages are copied into `/var/log/messages'
so you can always go there even if the boot log is cleared.
On Thu, Apr 19, 2001 at 02:56:17PM +0200, Andreas Schwab wrote:
> Bill Nottingham <notting@redhat.com> writes:
>
> |> Andreas Schwab (schwab@suse.de) said:
> |> > |> How about simply running 'top' or a 'dmesg | grep CPU'?
> |> >
> |> > As I already said, I'm running a UP kernel, thus top only ever sees one
> |> > CPU. The latter fails if the boot messages have already been cleared from
> |> > the kernel log.
> |>
> |> I believe the ACPI boot messages on ia64 tell you how many processors
> |> it found.
>
> How can I get at the ACPI boot messages if the kernel log is already
> cleared?
>
> Andreas.
>
> --
> Andreas Schwab "And now for something
> SuSE Labs completely different."
> Andreas.Schwab@suse.de
> SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
> Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
next prev parent reply other threads:[~2001-04-19 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 12:48 [Linux-ia64] Re: Detecting SMP in user space Bill Nottingham
2001-04-19 12:56 ` Andreas Schwab
2001-04-19 14:21 ` Don Dugger [this message]
2001-04-19 14:30 ` Andreas Schwab
2001-04-19 15:22 ` Dunlap, Randy
2001-04-19 15:40 ` Andreas Schwab
2001-04-19 16:33 ` Dunlap, Randy
2001-04-20 18:44 ` Andreas Schwab
2001-04-20 19:53 ` Dunlap, Randy
2001-04-20 20:24 ` Andreas Schwab
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-105590693005431@msgid-missing \
--to=n0ano@valinux.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.