From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil:diskWriteRawFailed error with Plan 9 on Microsoft
Date: Wed, 8 Oct 2008 08:35:42 -0400 [thread overview]
Message-ID: <095369c83b441aa7ec2d18fe5a1df0b0@quanstro.net> (raw)
In-Reply-To: <48EAECEA.2080601@gmail.com>
> Hello,
> I tried to install plan 9 on virtual pc and succedded. But, once
> i boot through plan 9 errors are coming.
> Attached the screen shot of the error.
the plan 9 ide driver apparently disagrees with virtual pc.
this isn't a fossil or venti problem.
unfortunately, i have no access to virtual pc so the rest of this
email is a thought experiment ....
command 30
data f09534b0 limit f0964eb0 dlen 8192 status 0 error 0
lba 210592 -> 210592, count 16 -> 16 (16)
0x00 0x04 0xac 0x36 0x03 0xe0 0x58
0x40: e306 0x42: c0000 x48: 00
0x4a 0000
so
the command is write sectors (Cws; 0x30)
lba 0x0336a0 (according to the driver)
the registers say:
0 1 2 3 4 5 6 As
0x00 0x04 0xac 0x36 0x03 0xe0 0x58
error count lba0 lba1 lba2 stat
at lba 0x3036ac (4 sectors to go) status Bsy|Df|Drdy.
i would think you're issuing a command before the device
is ready for you. this patch may help.
minooka; diff -c /sys/src/9/pc/sdata.c /n/dump/2008/0908/sys/src/9/pc/sdata.c
/sys/src/9/pc/sdata.c:1418,1424 - /n/dump/2008/0908/sys/src/9/pc/sdata.c:1418,1424
ctlr = drive->ctlr;
cmdport = ctlr->cmdport;
ctlport = ctlr->ctlport;
- if(ataready(cmdport, ctlport, drive->dev, Bsy|Drq, Drdy, 101*1000) < 0)
+ if(ataready(cmdport, ctlport, drive->dev, Bsy|Drq, 0, 101*1000) < 0)
return -1;
ilock(ctlr);
- erik
prev parent reply other threads:[~2008-10-08 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 5:00 [9fans] fossil:diskWriteRawFailed error with Plan 9 on Microsoft Virtual PC Sasidhar Kasturi
2008-10-08 12:35 ` erik quanstrom [this message]
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=095369c83b441aa7ec2d18fe5a1df0b0@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).