public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dale Harris <rodmur@maybe.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.24, ACPI, hyperthreading and strange messages
Date: Thu, 5 Feb 2004 15:04:34 -0800	[thread overview]
Message-ID: <20040205230434.GC27523@maybe.org> (raw)


Howdie,

I'm seeing some usual messages from dmesg with a kernel that I have
running on a cluster.  I have hyperthreading capable Xeons, Supermicro
mobos, and the nodes have LinuxBIOS (but the mayor does not).  I had to
bump the CONFIG_NR_CPUS to 8 to be able to even see both CPUs on the
nodes.  The messages I see that concern me are:

[on the nodes, where hyperthreading is not activated]:

  WARNING: No sibling found for CPU 0.
  WARNING: No sibling found for CPU 1.

[next occurs on the nodes and the mayor]

  ACPI: System description tables not found
      ACPI-0084: *** Error: acpi_load_tables: Could not get RSDP, AE_NOT_FOUND
      ACPI-0134: *** Error: acpi_load_tables: Could not load tables: AE_NOT_FOUND
  ACPI: Unable to load the System Description Tables
  PCI: Probing PCI hardware
  PCI: ACPI tables contain no PCI IRQ routing entries



So the problem occured independant of what BIOS I have, at least so it
seems.  Links full kernel config and dmesgs are below:

[a node, with linux bios, no HT]
   http://research.amnh.org/users/rodmur/dmesg.new
[the mayor, no linux bios, HT activated]
   http://research.amnh.org/users/rodmur/dmesg.dmtr
[kernel config used on all machines]
   http://research.amnh.org/users/rodmur/config.bproc


Is there a problem with the kernel or my configuration of it?


--
Dale Harris   
rodmur@maybe.org
/.-)

             reply	other threads:[~2004-02-05 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 23:04 Dale Harris [this message]
2004-02-05 23:58 ` 2.4.24, ACPI, hyperthreading and strange messages Dale Harris

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=20040205230434.GC27523@maybe.org \
    --to=rodmur@maybe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox