9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 'no fat' - boot failure
Date: Tue, 15 May 2012 05:11:18 -0400	[thread overview]
Message-ID: <fe871afd64357b631f125edee081aa30@kw.quanstro.net> (raw)
In-Reply-To: <4e5c4b87148d6168441298940a9906db@sp.inri.net>

On Mon May 14 22:57:54 EDT 2012, sl@9front.org wrote:
> > > Can you try getting rid of *nomp=1 and setting *msi=1
> > >
> >
> > I tried removing *nomp and adding *msi and got similar errors,
> > but with ioapicenable and mpreenable.  The disks got recognized
> > a lot faster this time, which was better, but my keyboard didn't work :-/
> > I can't really capture the full output as a lot of it scrolls off the screen
> > but I can write a more detailed description if anybody is interested.
>
> Some combination of *msi=1, *nousbehci=1 and/or *nousbuhci=1 may enable
> the SATA drive and USB keyboard simultaneously (especially if your system
> is capable of falling back to PS2 keyboard emulation), but in these cases
> USB itself has never worked for me. This is all hit or miss; it's a bit
> surprising that so many modern mp systems seem to work as well as they do.
> Prior to aiju's msi hack, my T61 was not able to use mp and its Ethernet
> port at the same time.

are you calling msi a hack, or the implementation?

imho, msi interrupts are quite nice.  much better than mp interrupts
through an ioapic.

in any event, i would be interested in a dump of these machine's ioapics and lapics.
one thing that i've found to be a problem with plan 9 is the incorrect
assumption that ioapics and lapics occupy the same apic id space.  this
is not true.  in addition, the mp table seldom has much information.
the acpi tables often need consulting.  the 9atom kernel has support
for all this.  (perhaps bordering on overkill.  :-)) i've included a listing
of an odd machine i have to illustrate the wierd setups some machines have.

- erik

ibmblade; grep -i apic /dev/kmesg
APIC lapic addr 0xfee00000, flags 0x00000001
apic proc 0/0 apicid 0 flags  (mp)
apic proc 1/2 apicid 2 flags
apic proc 2/3 apicid 4 flags
apic proc 3/4 apicid 6 flags
apic proc 4/5 apicid 8 flags
apic proc 5/6 apicid 10 flags
apic proc 6/1 apicid 32 flags  (mp)
apic proc 7/7 apicid 34 flags
apic proc 8/8 apicid 36 flags
apic proc 9/9 apicid 38 flags
apic proc 10/10 apicid 40 flags
apic proc 11/11 apicid 42 flags
apic proc 12/12 apicid 1 flags
apic proc 13/13 apicid 3 flags
apic proc 14/14 apicid 5 flags
apic proc 15/15 apicid 7 flags
apic proc 16/16 apicid 9 flags
apic proc 17/17 apicid 11 flags
apic proc 18/18 apicid 33 flags
apic proc 19/19 apicid 35 flags
apic proc 20/20 apicid 37 flags
apic proc 21/21 apicid 39 flags
apic proc 22/22 apicid 41 flags
apic proc 23/23 apicid 43 flags
ioapic 8 addr fec00000 base 0 (mp)
ioapic 9 addr fec01000 base 24 (mp)
ioapic 10 addr fec40000 base 48 (mp)
apicnos: 00/00 01/01 02/02 03/03 04/04 05/05 06/06 07/07 08/08 09/09 0a/0a 0b/0b 20/20 21/21 22/22 23/23 24/24 25/25 26/26 27/27 28/28 29/29 2a/2a 2b/2b
apic: 24 machs started; phys mode vectors
ibmblade; cat /dev/mpapic
proc            0 00000000 00000000 00000000 be            0
proc            1 01000000 01000000 01000000  e           12
proc            2 02000000 02000000 02000000  e            2
proc            3 03000000 03000000 03000000  e           13
proc            4 04000000 04000000 04000000  e            3
proc            5 05000000 05000000 05000000  e           14
proc            6 06000000 06000000 06000000  e            4
proc            7 07000000 07000000 07000000  e           15
ioapic          8 00000000 00000000 00000000  e            0
proc            8 08000000 08000000 08000000  e            5
ioapic          9 00000000 00000000 00000000  e            0
proc            9 09000000 09000000 09000000  e           16
ioapic          a 00000000 00000000 00000000  e            0
proc            a 0a000000 0a000000 0a000000  e            6
proc            b 0b000000 0b000000 0b000000  e           17
proc           20 20000000 20000000 20000000  e            1
proc           21 21000000 21000000 21000000  e           18
proc           22 22000000 22000000 22000000  e            7
proc           23 23000000 23000000 23000000  e           19
proc           24 24000000 24000000 24000000  e            8
proc           25 25000000 25000000 25000000  e           20
proc           26 26000000 26000000 26000000  e            9
proc           27 27000000 27000000 27000000  e           21
proc           28 28000000 28000000 28000000  e           10
proc           29 29000000 29000000 29000000  e           22
proc           2a 2a000000 2a000000 2a000000  e           11
proc           2b 2b000000 2b000000 2b000000  e           23



  reply	other threads:[~2012-05-15  9:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 21:07 Burton Samograd
2012-05-13 21:48 ` cinap_lenrek
2012-05-14  0:22   ` Burton Samograd
2012-05-14  1:19     ` Burton Samograd
     [not found]     ` <CAM8pOuMYGKSuSMUheyWqMXaf6pKwwkb+2bb5OkfGZSK2XcEVmQ@mail.gmail.c>
2012-05-14  2:56       ` erik quanstrom
2012-05-14  3:01         ` Burton Samograd
     [not found]         ` <CAM8pOuPUrCogvgDOzi_B0XxrT8RZDQZ7fOB0HhCwtXhFLaSA1g@mail.gmail.c>
2012-05-14  3:10           ` erik quanstrom
2012-05-14 22:12             ` cinap_lenrek
2012-05-15  0:57               ` Burton Samograd
2012-05-15  2:05               ` sl
2012-05-15  2:28                 ` erik quanstrom
2012-05-15  2:48                   ` sl
2012-05-15  9:19                     ` erik quanstrom
2012-05-15  2:36                 ` Burton Samograd
2012-05-15  2:39                   ` Burton Samograd
2012-05-15  2:57                   ` sl
2012-05-15  9:11                     ` erik quanstrom [this message]
2012-05-15 15:04                       ` cinap_lenrek
2012-05-15 15:26                         ` erik quanstrom
2012-05-15 17:11                           ` cinap_lenrek
2012-05-15 19:51                             ` cinap_lenrek
2012-05-15 20:29                               ` Burton Samograd
2012-05-15 20:33                                 ` cinap_lenrek
2012-05-15 23:49                               ` cinap_lenrek
2012-05-16  0:05                                 ` sl
     [not found]                   ` <CAM8pOuOtwTFjJDPYo_K3L580Zv-W24_XU-ZiBjP-6p9SFkHNkA@mail.gmail.c>
2012-05-15  9:20                     ` erik quanstrom
     [not found]                 ` <CAM8pOuMnp3xPw58g-7a7O_3HhOqf9=Z=DP-XfaGXQJdWyzrVFw@mail.gmail.c>
2012-05-15  9:31                   ` erik quanstrom
2012-05-15 12:19                     ` Burton Samograd
2012-05-15 12:40                       ` Burton Samograd
     [not found]                       ` <CAM8pOuOdLnTgqj1BOKhZe550Cc=QvfncgqgixcCAifKQSytFJA@mail.gmail.c>
2012-05-15 13:39                         ` erik quanstrom
     [not found]                     ` <CAM8pOuMbwVj0_s+SFMdT7qHe5oAg6Yux4shm189-Pd3-Gp2+mQ@mail.gmail.c>
2012-05-15 13:28                       ` erik quanstrom
2012-05-15 14:12                         ` Burton Samograd
     [not found]                         ` <D2A5C7470D67A54FACE86B838946D49D14E466F74E@NJ4MSGSCR02.markit.pa>
2012-05-15 15:02                           ` erik quanstrom
2012-05-15  2:26               ` erik quanstrom
2012-05-14  3:56     ` Ethan Grammatikidis

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=fe871afd64357b631f125edee081aa30@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.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).