From: "Eris Discordia" <eris.discordia@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Serious Problem Running Plan 9 on Virtual PC
Date: Fri, 1 Feb 2008 08:14:53 +0000 [thread overview]
Message-ID: <op.t5t6i3uic6yvfe@computer> (raw)
In-Reply-To: <b3efa585a5b35af42ed7ef7872cbd820@quanstro.net>
On Fri, 01 Feb 2008 02:37:12 -0000, erik quanstrom <quanstro@quanstro.net>
wrote:
>> (long, almost 5 minute, pause here)
>> command 30
>> data f07613b0 limit f07263b0 dlen 8192 status 0 error 0
>> lba 231760 -> 231760, count 16 -> 16 (16)
>> [0] 0x00 0x07 0x59 0x89 0x03 0xE0 0x58
> data err lba lba lba lba obs Status
>> 0x40: E307 0x42: C0000x48: 00
>> 0x4A: 0000
>> fossil: diskWriteRaw failed: /dev/sdC0/fossil: score 0x00000006: date
>> Thu
>> Jan
>> 31 16:45:44 EST 2008
>> part=data block 6: i/o error
>>
>
> quick reparse of the data you've given. ata command 0x30 (write
> sectors) timed out after 1 minute at lba 231760 which is safely under
> 8GB. the status (register 7) is 0x58 which is
> 0x08 Drq /* waiting on your data */
> 0x10 Serv
> 0x40 Drdy
>
> but the lba read back (assuming it's correct) is 231769. so some
> progress has been made -- indicating we're getting some interrupts,
> but somehow we've missed one and stalled out.
>
> the real problem is that data > limit by 236kb. i'm not sure how this
> could happen. something looks very wrong.
>
> - erik
>
First of all, lots of thanks for taking the time to help.
Then, I really understand very little, if any, of computer hardware and/or
systems programming. Given that, I dare ask a naive question: Could the
problem be because of running a "32-bit virtual machine" on a "64-bit OS?"
The version of VPC I am using is supposed to be 64-bit. Microsoft's
website says so. And the 32-bit version I had would not even install on
Windows XP x64. In spite of these facts, Windows task manager adds a *32
to the image name of the VPC process which effectively means it is a
32-bit process running in compatibility mode. The emulated machines are
surely 32-bit.
On the other hand, my (32-bit) FreeBSD installation is running prefectly
OK on this same platform.
Right now, I think one way to test any ideas is for me to boot into the
live system and somehow try to access the virtual hard disk. I would be
grateful if someone would instruct me on any diagnostic procedures and/or
various access methods from the live system. Things equivalent to the
UNIX/Linux mount, mkfs, and fsck.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next prev parent reply other threads:[~2008-02-01 8:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 17:27 Eris Discordia
2008-02-01 2:37 ` erik quanstrom
2008-02-01 8:14 ` Eris Discordia [this message]
2008-02-01 12:34 ` erik quanstrom
2008-02-01 15:17 ` Eris Discordia
2008-02-01 15:43 ` erik quanstrom
2008-02-01 17:07 ` Juan M. Mendez
2008-02-01 17:44 ` Eris Discordia
2008-02-01 17:42 ` Eris Discordia
2008-02-01 17:54 ` erik quanstrom
[not found] <20080201180331.DBFB55B52@mail.bitblocks.com>
2008-02-02 22:22 ` Eris Discordia
2008-02-02 23:49 ` Steve Simon
2008-02-04 10:24 ` Eris Discordia
2008-02-04 10:58 ` Filipp Andronov
2008-02-04 11:23 ` Juan M. Mendez
2008-02-04 11:50 ` Filipp Andronov
2008-02-04 11:54 ` Juan M. Mendez
2008-02-04 12:56 ` Filipp Andronov
2008-02-04 13:29 ` Eris Discordia
2008-02-04 14:47 ` Martin Neubauer
2008-02-04 15:56 ` Filipp Andronov
2008-02-04 16:55 ` Gorka Guardiola
2008-02-05 10:46 ` Filipp Andronov
2008-02-04 13:52 ` Eris Discordia
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=op.t5t6i3uic6yvfe@computer \
--to=eris.discordia@gmail.com \
--cc=9fans@cse.psu.edu \
/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).