From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@hamnavoe.com, 9fans@9fans.net
Subject: Re: [9fans] local apic unreadable?
Date: Mon, 11 Jun 2012 09:03:27 -0400 [thread overview]
Message-ID: <69e4f759b821d860c917e37f3db45391@brasstown.quanstro.net> (raw)
In-Reply-To: <35958772805f8f85bca9c0fe40f54669@hamnavoe.com>
On Mon Jun 11 07:02:26 EDT 2012, 9fans@hamnavoe.com wrote:
> OK, solved. This motherboard (or bios) gives the io apic an id of 0,
> same as the boot processor's local apic. The unexpected aliasing
> causes the lapic (virtual) address to be overwritten by the ioapic
> address, so the lapic timer code is looking in the wrong place for its
> registers.
though unexpected, it's not aliasing. lapics and apics have different
apic id namespaces.
> Erik's kernel has also had a similar fix, presumably made some time
> ago - there's a 9fans post about a "wierd lapic/ioapic configuration"
> which I should have spotted as a clue ...
1. may 2011, according to the dump.
- erik
prev parent reply other threads:[~2012-06-11 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 17:07 Richard Miller
2012-06-08 17:33 ` erik quanstrom
2012-06-08 17:53 ` Richard Miller
2012-06-08 18:01 ` erik quanstrom
2012-06-11 11:00 ` Richard Miller
2012-06-11 13:03 ` erik quanstrom [this message]
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=69e4f759b821d860c917e37f3db45391@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=9fans@hamnavoe.com \
/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;
as well as URLs for NNTP newsgroup(s).