On Sun May 19 00:34:14 EDT 2013, aris...@ar.aichi-u.ac.jp wrote:
> Hello,
>
> yesterday day I had error messages below:
>
> automatic dump Fri May 17 05:00:07 2013
> automatic dump Sat May 18 05:00:08 2013
> command 30
> data f7aea8a0 limit f7aec0a0 dlen 16384 status 0 error 0
> lba 163565804 ->
9front uses a (older) variant of the 9atom ide driver.
from arisawas's output, it seems that the write command times out
in atagenio():
iowait(drive, 30*1000, 0);
if(!ctlr->done){
/*
* What should the above timeout b
> i doubt this is missed interrupts. iowait() calls the interrupt handler
> itself before giving up. you can even check, as the driver keeps statistics
> about missed interrupts in the ctl file.
it can be. previously, on e.g. intel devices, we did not properly
handle dma interrupts. this lead to
> the (9atom) ahci driver should directly handle ALPM, PUIS and
> other power-saving bits added in ahci 1.3, so i prefer to run ahci
> whenever possible.
that is, so one doesn't have to worry about power-savings techniques
messing things up.
- erik
I installed 9atom downloaded from Erik's site on 5/12 on a
Gigabyte GA-D525TUD
(http://www.gigabyte.com/products/product-page.aspx?pid=3549#ov).
When I have *nomp=1 in plan9.ini, I am able to log in and
things work OK (except the mouse wheel scroll direction is
opposite to what I would expect),
> I installed 9atom downloaded from Erik's site on 5/12 on a
> Gigabyte GA-D525TUD
> (http://www.gigabyte.com/products/product-page.aspx?pid=3549#ov).
>
> When I have *nomp=1 in plan9.ini, I am able to log in and
> things work OK (except the mouse wheel scroll direction is
> opposite to what I wou
> I installed 9atom downloaded from Erik's site on 5/12 on a
> Gigabyte GA-D525TUD
> (http://www.gigabyte.com/products/product-page.aspx?pid=3549#ov).
>
> When I have *nomp=1 in plan9.ini, I am able to log in and
> things work OK (except the mouse wheel scroll direction is
> opposite to what I wou
