From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] vmware installation problems
Date: Mon, 27 Jul 2009 17:08:25 -0400 [thread overview]
Message-ID: <f9a8edb80db17b4708c1b7ee8f6e810c@coraid.com> (raw)
In-Reply-To: <df49a7370907271321x324d6817xf05fc72d31d6d542@mail.gmail.com>
> there was then a long pause and then i got lots and lots more i/o
> error messages, and it failed to boot.
sounds like missed irqs.
> init: starting /bin/rc
> ndb/dns: can't read my ip address
> 2009/0728 00:53:27 err 4: write /dev/sdC0/isect offset 0xb0a4000 count
> 65536 buf 1dc6000 returned -1: i/o error
> /boot/venti: part /dev/sdC0/isect addr 0xaf24000: icachewritesect
> writepart: write /dev/sdC0/isect offset 0xb0a4000 count 65536 buf
> 1dc6000 returned -1: i/o error
a few things that might differ between the intaller
and the installed image that might cause lost irqs or
other problems, maybe in likelyhood order:
- the mp irq state,
- the dma state,
- the lba settings.
contrib quanstro/sd might have some extra debugging
that may help. it also has some defense against missed
irqs. it will log them and soldier on. i know it's a
gruesome hack, but missed ide interrupts have been
a common disease and the easiest way to debug them
is to have a bootable system.
- erik
next prev parent reply other threads:[~2009-07-27 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 20:21 roger peppe
2009-07-27 21:08 ` erik quanstrom [this message]
[not found] <df49a7370907290157u44aa95ebv588fcbd6b023c404@mail.gmail.com>
[not found] ` <832c87e4aa20e86ae6651751b91821b3@quanstro.net>
[not found] ` <df49a7370907290727m438abc4bx82dc6b0345d64731@mail.gmail.com>
2009-07-29 14:49 ` roger peppe
2009-07-29 16:07 ` Rodolfo (kix)
2009-07-29 16:28 ` roger peppe
2009-07-29 17:12 ` Tim Newsham
2009-07-29 17:34 ` roger peppe
2009-07-29 17:54 ` drivers
2009-07-30 16:32 ` Tim Newsham
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=f9a8edb80db17b4708c1b7ee8f6e810c@coraid.com \
--to=quanstro@coraid.com \
--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).