From: Mikael Pettersson <mikpe@csd.uu.se>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: APIC Error when doing apic_pm_suspend
Date: Wed, 5 Dec 2001 18:16:46 +0100 [thread overview]
Message-ID: <15374.22142.86391.322681@harpo.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.33.0112051123500.18928-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.33.0112051123500.18928-100000@netfinity.realnet.co.sz>
Zwane Mwaikambo writes:
> I get an APIC error 0x40 when resuming from an apm -s. If i'm correct
> that would be an illegal register access wouldn't it? I tried putting
> enter/exit printks in the apic_pm_resume/suspend functions and it showed
> that both returned before the APIC error printk. Is there anyway of finding out
> which register access it was? I "thought" it would be one of the
> apic_writes in the pm functions but looks like i might be wrong.
>
> The kernel is compiled with local APIC and gets detected and enabled on
> boot (UP machine).
No, 0x40 is an illegal vector error. It's a (semi-) known quirk in the P6 family
of processors that you get this error when writing a null vector to any of the
LVT entries, even if you are also setting the mask bit at the same time.
Both the clear_local_APIC() call at PM suspend and the reinitialisation at PM
resume can trigger this.
The "error" is mostly harmless. Ignore it for now, I'll do a patch to silence it later.
/Mikael
next prev parent reply other threads:[~2001-12-05 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 9:33 Zwane Mwaikambo
2001-12-05 10:09 ` Arjan van de Ven
2001-12-05 12:57 ` Zwane Mwaikambo
2001-12-05 17:16 ` Mikael Pettersson [this message]
2001-12-06 10:54 ` Zwane Mwaikambo
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=15374.22142.86391.322681@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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®