From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"Frans Pop" <elendil@planet.nl>,
linux-kernel@vger.kernel.org, "Andi Kleen" <andi@firstfloor.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!
Date: Thu, 21 Aug 2008 15:14:03 +0200 [thread overview]
Message-ID: <19f34abd0808210614g15330a02u7a0625f88dfe4798@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0808211340100.22938@cliff.in.clinika.pl>
On Thu, Aug 21, 2008 at 2:57 PM, Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Thu, 21 Aug 2008, Vegard Nossum wrote:
>
>> Ah, right. Here is a dump of the LVT registers:
>>
>> [00000320] = 000100ef
>> [00000330] = 00000200
>> [00000340] = 00010000
>> [00000350] = 00010700
>> [00000360] = 00000400
>> [00000370] = 000000fe
>>
>> Maybe I've misunderstood something (again), but should those vectors
>> really be 0 for 330-360? (At least 330 + 360, which are not masked.)
>
> Masked entries should be fine long-term, although I have a vague
> recollection at least some implementations do send a vector error when an
> LVT register is written with a masked entry implying an invalid vector,
> e.g. a value like 0x00010000.
>
> Overall the issue of the validity of the vector exists for interrupts
> using the native APIC priority model only, that is ones using the Fixed
> and LoPri delivery modes. All the others either ignore the vector
> altogether, such as the ExtINTA delivery mode, or assign a special meaning
> to it, such as the StartUp mode.
>
> In this case the thermal entry at 0x330 uses the SMI delivery mode and
> the LINT1 entry at 0x360 uses the NMI mode, so the vector is ignored for
> both.
>
> Thus this LVT is entirely valid and if you receive invalid vector
> interrupts, then the reason must be elsewhere. Of course you cannot
> exclude a possibility where at some intermediate stage the LVT of your
> system has not been correctly initialised.
Thank you for the excellent explanations! I've double-checked and
everything you said makes perfect sense.
The reason must be elsewhere.
Vegard
PS: My APICs have version 0x20, which according to the Intel manual is
a reserved value. My book is from 2005, though.
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-08-21 13:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 19:06 Frans Pop
2008-08-20 19:38 ` Rafael J. Wysocki
2008-08-20 20:26 ` Frans Pop
2008-08-20 21:56 ` Rafael J. Wysocki
2008-08-21 9:27 ` Maciej W. Rozycki
2008-08-21 11:18 ` Vegard Nossum
2008-08-21 11:51 ` Maciej W. Rozycki
2008-08-21 12:01 ` Maciej W. Rozycki
2008-08-21 12:20 ` Vegard Nossum
2008-08-21 12:57 ` Maciej W. Rozycki
2008-08-21 13:14 ` Vegard Nossum [this message]
2008-08-21 13:15 ` Mikael Pettersson
2008-08-30 19:33 ` Yinghai Lu
2008-08-30 19:16 ` Frans Pop
2008-08-30 20:16 ` Maciej W. Rozycki
2008-09-04 20:18 ` Frans Pop
2008-08-21 11:30 ` Matthew Garrett
2008-08-21 11:31 ` Matthew Garrett
2008-08-22 0:02 ` Frans Pop
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=19f34abd0808210614g15330a02u7a0625f88dfe4798@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=andi@firstfloor.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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®