:> ahci0.0: CMD TIMEOUT state=5 slot=22
:> cmd-reg=0x4d617<HPCP,CR,FR,FRE,POD,SUD,ST>
:> sactive=00400000 active=00000000
:> [...]
:> STS=40
:> ahci0.0: disk_rw: timeout
:
:With hint.ahci.force150, results are identical.
:
:--
:Francois Tigeot
Hmm. I'm a bit at a loss.
Update again. I added some defensive bzero()ing of the FIS to the AHCI
driver. Maybe there was some cruft in the read command it tried to
construct.
Do any other disks work there (get past boot)? Looking on Google
those 4000YS's had firmware issues. It's worth a shot. Maybe they
are expecting some field to be set in the command that I'm not setting.
-Matt
Matthew Dillon
<[email protected]>
