From: Karl Weigel <xml-22047@gmx.de>
To: linux-smp@vger.kernel.org
Subject: "unexpected IO-APIC" in boot.msg
Date: Wed, 11 Dec 2002 08:54:48 +0100 [thread overview]
Message-ID: <200212110854.48384.xml-22047@gmx.de> (raw)
Hi,
after changing to 2.4.20-kernel I analysed my logfiles and found a message,
that you like to be informed about this IO-APIC. I hope that the supplied
excerpt contains enough information to decide, whether this is interessting
to you. If you need more input, I will supply it, if I can.
I do not see, whether this APIC causes any problems for me.
Regards
Karl W. Weigel
--- excerpt from /var/log/boot.msg -------------------------------
<7>IO APIC #2......
<7>.... register #00: 02000000
<7>....... : physical APIC id: 02
<7>.... register #01: 00178002
<7>....... : max redirection entries: 0017
<7>....... : PRQ implemented: 1
<7>....... : IO APIC version: 0002
<4> WARNING: unexpected IO-APIC, please mail
<4> to linux-smp@vger.kernel.org
<7>.... IRQ redirection table:
<7> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
<7> 00 000 00 1 0 0 0 0 0 0 00
<7> 01 001 01 0 0 0 0 0 1 1 39
<7> 02 001 01 0 0 0 0 0 1 1 31
<7> 03 001 01 0 0 0 0 0 1 1 41
<7> 04 001 01 0 0 0 0 0 1 1 49
<7> 05 001 01 0 0 0 0 0 1 1 51
<7> 06 001 01 0 0 0 0 0 1 1 59
<7> 07 001 01 0 0 0 0 0 1 1 61
<7> 08 001 01 0 0 0 0 0 1 1 69
<7> 09 001 01 1 1 0 1 0 1 1 71
<7> 0a 001 01 0 0 0 0 0 1 1 79
<7> 0b 001 01 0 0 0 0 0 1 1 81
<7> 0c 001 01 0 0 0 0 0 1 1 89
<7> 0d 001 01 0 0 0 0 0 1 1 91
<7> 0e 001 01 0 0 0 0 0 1 1 99
<7> 0f 001 01 0 0 0 0 0 1 1 A1
<7> 10 000 00 1 0 0 0 0 0 0 00
<7> 11 000 00 1 0 0 0 0 0 0 00
<7> 12 000 00 1 0 0 0 0 0 0 00
<7> 13 000 00 1 0 0 0 0 0 0 00
<7> 14 000 00 1 0 0 0 0 0 0 00
<7> 15 000 00 1 0 0 0 0 0 0 00
<7> 16 000 00 1 0 0 0 0 0 0 00
<7> 17 000 00 1 0 0 0 0 0 0 00
reply other threads:[~2002-12-11 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200212110854.48384.xml-22047@gmx.de \
--to=xml-22047@gmx.de \
--cc=linux-smp@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