mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Johnson <ddj@cascv.brown.edu>
To: linux-kernel@vger.kernel.org
Subject: Unexpected IO-APIC messages
Date: Mon, 16 Jul 2001 15:04:47 -0400	[thread overview]
Message-ID: <20010716150447.A13358@mookie.cis.brown.edu> (raw)

When booting up 2.4.2-2smp (RH 7.1) on a new system here, the kernel
complains about the IO-APIC register contents, and asks that mail be
sent to linux-smp@vger.kernel.org.

It appears that the linux-smp list is defunct; at least there have been
no new messages archived on geocrawler since August 2000.  It also
appears that the new IO APIC reg01.version of 0x20 was reported about
a year ago on the linux-smp list, and reg_01.__reserved_2 of 0x80 was
reported on this list around February 2001.  

The relevant dmesg info from our machine follows:
----
testing the IO APIC.......................

IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.... register #01: 00178020
.......     : max redirection entries: 0017
.......     : IO APIC version: 0020
 WARNING: unexpected IO-APIC, please mail
          to linux-smp@vger.kernel.org
 WARNING: unexpected IO-APIC, please mail
          to linux-smp@vger.kernel.org
.... register #02: 00000000
.......     : arbitration: 00
----

The APIC information from lspci -v follows:
----
03:00.0 PIC: Intel Corporation 82806AA PCI64 Hub Advanced Programmable Interrupt
 Controller (rev 01) (prog-if 20 [IO(X)-APIC])
        Subsystem: Intel Corporation 82806AA PCI64 Hub Advanced Programmable Int
errupt Controller
        Flags: fast devsel
        Memory at fe400000 (32-bit, non-prefetchable) [disabled] [size=4K]
----


If anyone is planning to do anything about new IO-APIC versions and stuff,
at least the mailing list address should be corrected.

If nobody cares until a bug comes along, perhaps the message should be
changed to say "unrecognized" or "unknown" rather than unexpected, so
the d**n users don't pee in their pants when they see the boot log
scrolling by.

Or maybe just parse and print out the values and refer the user to
linux/Documentation/i386/IO-APIC.txt (which also still refers to the
linux-smp mailing list) for further information.

Thanks,


	-- ddj

	Dave Johnson
	ddj@cascv.brown.edu

             reply	other threads:[~2001-07-16 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 19:04 Dave Johnson [this message]
2001-07-16 20:14 ` Randy.Dunlap

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=20010716150447.A13358@mookie.cis.brown.edu \
    --to=ddj@cascv.brown.edu \
    --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

all inboxes | Powered by JetHome®