9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Latchesar Ionkov <lucho@ionkov.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9atom.iso
Date: Mon,  5 Oct 2009 12:41:50 -0600	[thread overview]
Message-ID: <f158dc670910051141y4e7c0cdcob5ab17b196a3a56e@mail.gmail.com> (raw)
In-Reply-To: <2a95d8f4fa584bb893a307aeadb940c7@coraid.com>

I don't see neither /dev/mpirq nor /dev/nompirq.

Thanks,
    Lucho

On Mon, Oct 5, 2009 at 11:43 AM, erik quanstrom <quanstro@coraid.com> wrote:
> On Mon Oct  5 13:38:51 EDT 2009, lucho@ionkov.net wrote:
>> Boots fine from the CD and installs on a Shuttle X27. When booting
>> from the hard disk, I get a lot of
>>
>>     ide: caught missed irq
>>
>> and no working system. It hangs somewhere after
>>
>>     version... time...
>>
>> Thanks,
>>     Lucho
>
> it's not hung, it's just really really sloooow.  caught missed
> irq means that it's trying to forge ahead even though
> the ide irq has been somehow misrouted.  my ide driver
> tries to do its best in these cases, since this is a very common
> problem.
>
>  do you have a recognized southbridge?  there should
> be a dev file /dev/mpirq (or nompirq if mp irqs are off)
> that describes the mp table.  sometimes you'll see that there
> are two mappings from bus irq to processor irq that are
> the same except for the i/o apic output pin.  without the
> routing tables, you don't know which one is correct.
>
> it would be nice to be able to override irqs in plan9.ini.
>
> - erik
>
>



  reply	other threads:[~2009-10-05 18:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 18:21 erik quanstrom
2009-09-29 20:13 ` baux80
2009-10-01  7:55 ` baux80
2009-10-05 17:35 ` Latchesar Ionkov
2009-10-05 17:43   ` erik quanstrom
2009-10-05 18:41     ` Latchesar Ionkov [this message]
2009-10-05 19:32       ` erik quanstrom
2009-10-05 20:38         ` Latchesar Ionkov
2009-10-06  0:52           ` Fernan Bolando
     [not found] <<200910010755.n917tOTn004831@elisya.g.zucchetti.com>
2009-10-01 13:37 ` erik quanstrom
2009-10-05 16:14   ` baux80
     [not found] <<f158dc670910051035h56675cc7k920f43cc41287d62@mail.gmail.com>
2009-10-05 17:45 ` erik quanstrom
     [not found] <<1d5d51400910051752y49ab1da6qfcdaa8b338c194fe@mail.gmail.com>
2009-10-06  2:02 ` erik quanstrom
2009-10-06 15:17   ` Latchesar Ionkov
     [not found] <<f158dc670910060817y68fbb39asa5060cfc7901e2f7@mail.gmail.com>
2009-10-06 15:47 ` erik quanstrom

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=f158dc670910051141y4e7c0cdcob5ab17b196a3a56e@mail.gmail.com \
    --to=lucho@ionkov.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).