From: Richard Miller <9fans@hamnavoe.com>
To: quanstro@quanstro.net, 9fans@9fans.net
Subject: Re: [9fans] Kernel panic when compiling Go on native Plan 9
Date: Fri, 2 Nov 2012 15:25:02 +0000 [thread overview]
Message-ID: <fef1ca0a1588df6a73f29343961886b2@hamnavoe.com> (raw)
In-Reply-To: <aca947c35dbaa3f7ed69a7882d9a2bf2@brasstown.quanstro.net>
> i found in nix that when mixing acpi and mp i had to defend against
> double-entries for i/o apics since the numbering can be different. but
> it will be interesting to see what happened to start 2 cpu1s.
Looks like the same thing: MP table says 2 cpus with apic ids 0 and 1,
ACPI table says 2 cpus (the same ones) with ids 0 and 2.
Mixing information from MP and ACPI tables seems to me like just asking
for trouble.
next prev parent reply other threads:[~2012-11-02 15:25 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 9:50 Pavel Klinkovsky
2012-11-02 10:56 ` Pavel Klinkovsky
2012-11-02 11:59 ` Richard Miller
2012-11-02 13:04 ` erik quanstrom
2012-11-02 12:19 ` Anthony Martin
2012-11-02 13:39 ` Pavel Klinkovsky
2012-11-02 13:51 ` Richard Miller
2012-11-02 13:57 ` erik quanstrom
2012-11-02 15:25 ` Richard Miller [this message]
2012-11-02 16:42 ` cinap_lenrek
2012-11-02 14:16 ` Pavel Klinkovsky
2012-11-02 13:39 ` Pavel Klinkovsky
2012-11-02 14:00 ` erik quanstrom
2012-11-02 14:39 ` Anthony Martin
2012-11-02 15:13 ` erik quanstrom
2012-11-02 16:44 ` steve
2012-11-02 15:21 ` Pavel Klinkovsky
2012-11-02 16:03 ` Pavel Klinkovsky
2012-11-02 17:07 ` Skip Tavakkolian
2012-11-02 17:09 ` erik quanstrom
2012-11-02 16:19 ` [9fans] Kernel panic when allocating a huge memory Pavel Klinkovsky
2012-11-02 16:29 ` erik quanstrom
2012-11-02 17:36 ` Pavel Klinkovsky
2012-11-02 18:36 ` John Floren
2012-11-02 18:52 ` erik quanstrom
2012-11-02 19:09 ` Skip Tavakkolian
2012-11-02 19:18 ` erik quanstrom
2012-11-02 20:28 ` Charles Forsyth
2012-11-03 5:43 ` pmarin
2012-11-03 6:53 ` steve
2012-11-03 6:56 ` erik quanstrom
2012-11-03 9:16 ` Charles Forsyth
2012-11-03 10:02 ` lucio
2012-11-03 15:40 ` erik quanstrom
2012-11-03 15:50 ` Charles Forsyth
2012-11-03 16:31 ` Kurt H Maier
2012-11-03 16:33 ` erik quanstrom
2012-11-03 16:46 ` hiro
2012-11-03 16:51 ` Kurt H Maier
2012-11-03 17:04 ` erik quanstrom
2012-11-03 17:13 ` Kurt H Maier
2012-11-03 17:22 ` Dan Cross
2012-11-03 17:28 ` Kurt H Maier
2012-11-03 17:38 ` hiro
2012-11-03 21:29 ` Steve Simon
2012-11-03 17:40 ` erik quanstrom
2012-11-03 17:45 ` Kurt H Maier
2012-11-03 17:57 ` erik quanstrom
2012-11-03 18:06 ` Kurt H Maier
2012-11-03 18:48 ` Charles Forsyth
2012-11-04 14:02 ` erik quanstrom
2012-11-04 14:18 ` hiro
2012-11-04 14:58 ` Charles Forsyth
2012-11-04 18:57 ` Bakul Shah
2012-11-04 14:54 ` Charles Forsyth
2012-11-04 16:14 ` Martin Harriss
2012-11-04 16:18 ` Charles Forsyth
2012-11-04 16:27 ` tlaronde
2012-11-04 19:17 ` tlaronde
2012-11-03 21:15 ` hiro
2012-11-03 16:55 ` balaji
2012-11-03 17:05 ` Matthew Veety
2012-11-02 17:42 ` [9fans] Kernel panic when compiling Go on native Plan 9 Pavel Klinkovsky
2012-11-05 13:33 ` [9fans] Kernel panic when allocating a huge memory Pavel Klinkovsky
2012-11-05 13:50 ` erik quanstrom
2012-11-05 15:56 ` Pavel Klinkovsky
2012-11-05 13:51 ` cinap_lenrek
2012-11-05 15:56 ` Pavel Klinkovsky
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=fef1ca0a1588df6a73f29343961886b2@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
--cc=quanstro@quanstro.net \
/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).