Re: SATA2 mode on SATA3 SSD (marvell controller) after boot

On 20.04.2014 22:31, Andrey Fesenko wrote:
> On Thu, Apr 17, 2014 at 2:10 PM, Andrey Fesenko <f0andrey_at_gmail.com> wrote:
>> if disconnect ssd
>> pr 17 14:07:08 desktop kernel: ahcich3: DISCONNECT requested
>> Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset...
>> Apr 17 14:07:08 desktop kernel: ahcich3: SATA connect timeout
>> time=10000us status=00000000
>> Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset: device not found
>> Apr 17 14:07:08 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 lun 0
>> Apr 17 14:07:08 desktop kernel: pass3: <PLEXTOR PX-128M5S 1.05> s/n
>> P02411112921 detached
>> Apr 17 14:07:08 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
>> Apr 17 14:07:08 desktop kernel: ada3: <PLEXTOR PX-128M5S 1.05> s/n
>> P02411112921 detached
>> Apr 17 14:07:08 desktop kernel: (pass3:ahcich3:0:0:0): Periph destroyed
>> Apr 17 14:07:08 desktop kernel: (ada3:ahcich3:0:0:0): Periph destroyed
>> Apr 17 14:07:18 desktop kernel: ahcich3: CONNECT requested
>> Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset...
>> Apr 17 14:07:18 desktop kernel: ahcich3: SATA connect time=8000us
>> status=00000133
>> Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device found
>> Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device ready after 0ms
>> Apr 17 14:07:18 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
>> Apr 17 14:07:18 desktop kernel: GEOM: new disk ada3
>> Apr 17 14:07:18 desktop kernel: ada3: <PLEXTOR PX-128M5S 1.05> ATA-8
>> SATA 3.x device
>> Apr 17 14:07:18 desktop kernel: ada3: Serial Number P02411112921
>> Apr 17 14:07:18 desktop kernel: ada3: 600.000MB/s transfers (SATA 3.x,
>> UDMA6, PIO 8192bytes)
>> Apr 17 14:07:18 desktop kernel: ada3: Command Queueing enabled
>> Apr 17 14:07:18 desktop kernel: ada3: 122104MB (250069680 512 byte
>> sectors: 16H 63S/T 16383C)
>> Apr 17 14:07:18 desktop kernel: ada3: Previously was known as ad10
>> Apr 17 14:07:18 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 lun 0
>> Apr 17 14:07:18 desktop kernel: pass3: <PLEXTOR PX-128M5S 1.05> ATA-8
>> SATA 3.x device
>> Apr 17 14:07:18 desktop kernel: pass3: Serial Number P02411112921
>> Apr 17 14:07:18 desktop kernel: pass3: 600.000MB/s transfers (SATA
>> 3.x, UDMA6, PIO 8192bytes)
>> Apr 17 14:07:18 desktop kernel: pass3: Command Queueing enabled
>>
>>
>> # uname -a
>> FreeBSD desktop.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r263932:
>> Sun Mar 30 15:43:01 MSK 2014
>> root_at_desktop.local:/usr/obj/usr/src/sys/MY_DES  amd64
>
> Is it possible camcontrol repeat behavior as physical disable/enable
> or enable SATA 3.x mode?
> camcontrol negotiate only report not set new mode.
>
> # camcontrol negotiate pass2
> Current parameters:
> (pass2:ahcich3:0:0:0): SATA revision: 2.x
> (pass2:ahcich3:0:0:0): ATA mode: UDMA6
> (pass2:ahcich3:0:0:0): ATAPI packet length: 0
> (pass2:ahcich3:0:0:0): PIO transaction length: 8192
> (pass2:ahcich3:0:0:0): PMP presence: 0
> (pass2:ahcich3:0:0:0): Number of tags: 32
> (pass2:ahcich3:0:0:0): SATA capabilities: 00000030
> (pass2:ahcich3:0:0:0): tagged queueing: enabled

camcontrol negotiate can limit maximal SATA mode, but not specify it 
exactly. Unless you limited it previously, there should be no limitation 
set and HBA should negotiate it freely. The limitations could be 
read/set with `camcontrol negotiate pass2 -U`, and affect operation 
after following `camcontrol reset ...`.

-- 
Alexander Motin