9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: fernanbolando@mailc.net
Cc: 9fans@9fans.net
Subject: Re: [9fans] oh, no! (again)
Date: Wed, 12 Aug 2009 08:40:47 -0400	[thread overview]
Message-ID: <47809b4840d7f2e7468f27c753fec6b5@quanstro.net> (raw)
In-Reply-To: <1d5d51400908120512y3f0d156ahde257a0d4cac500e@mail.gmail.com>

> > judging from past email, i'm guessing that your ide device
> > is 27c4, which was missing from 9load.  i put up a corrected cd.
> > if you can ftpfs from your mostly-installed machine and
> > get just 9load.bz2, it's in the same directory.
> >
> > ; i=9atom.iso.bz2 sha1sum $i && ls -l $i
> > cb7bdb9bcaebaf5e54d5a76c672dba52f90eb55a        9atom.iso.bz2
> > --rw-r--r-- M 176 quanstro quanstro 88211681 Aug 11 17:13 9atom.iso.bz2
> >
> thanks erik!!!  I can now boot. I am now at the
> init starting /bin/rc     stage it seems to stall there. I think its
> just the ip/ipconfig issue should be easy to fix.

> just a note.  i am getting
> ide: caught missed irq   several times shoul i be concerned?

what's going on:
i replaced the sleep in sdata.c with a loop that checks for i/o
completion every second.  i/o should never be outstanding for
1 second, so this will never fire unless your disk is very sick,
or you're missing interrupts.  after 10 missed irqs, it has mercy
on you and checks every 50ms.  this will seem very slow.

the pureists are probablly going to choke at this trick.
i don't blame them.  but on the other hand, i want to give
folks a chance to recover their systems if ide acts up.

this is something to be concerned about.

once you boot up, there are a number of things to try.
/dev/irqalloc for your kernel should have an extra final
entry that counts the number of interrupts on each vector.
i would expect that number would be 0, given your symptoms.

here are a few things you can look at
- is your southbridge recognized?

- you might want to try turning dma on, on the wild
theory that it worked well enough during installation.

- you might want to try turning mp interrupts on.
unfortunately, i forgot to add the nomp device which
allow one to inspect the mp interrupts before trying
them.

failing any of those things, send me your pci output.
this setup should work.

- erik



  reply	other threads:[~2009-08-12 12:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 13:28 cej
2009-08-11 13:55 ` erik quanstrom
2009-08-11 14:17 ` erik quanstrom
2009-08-11 16:12   ` cej
2009-08-11 16:26     ` erik quanstrom
2009-08-11 17:57       ` erik quanstrom
2009-08-11 19:04         ` David Leimbach
2009-08-11 19:25           ` erik quanstrom
2009-08-11 20:51             ` Fernan Bolando
2009-08-11 21:17               ` erik quanstrom
     [not found]               ` <7ed7d1dd2bafb28e91ed462c526409e6@quanstro.net>
2009-08-12 12:12                 ` Fernan Bolando
2009-08-12 12:40                   ` erik quanstrom [this message]
     [not found]                   ` <5e44a853596c9d4a4a751c14d0878855@quanstro.net>
2009-08-12 14:06                     ` Fernan Bolando
2009-08-13 14:10         ` Fernan Bolando
2009-08-13 14:33           ` erik quanstrom
     [not found]           ` <855df96e3e51a2f75d1bce104eddda2f@quanstro.net>
2009-08-13 14:49             ` Fernan Bolando
2009-08-13 14:54               ` 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=47809b4840d7f2e7468f27c753fec6b5@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=fernanbolando@mailc.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).