[Bug 229745] ahcich: CAM status: Command timeout

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745

--- Comment #3 from Alexey <fbsd98816551 at avksrv.org> ---
Yes, it possibe problem related to disk. We have 8 servers Supermicro X10DRW-i,
4 of them are with HGST HUS722T1TALA604 and another 4 with ТOSHIBA DT01ACA100
MS2OA750 HDDs. All of them use to be installed near half year ago to Fbsd
11.1-stable, all of them use to works fine. now we have upgraded to 11.2 two
and two server with each disk type and we got problem with servers who use HGST
and still do not have problem with Toshiba based servers.. I'll try to replace
disks to different model. Bot if problem in disk itself, why it work under
11.1? 

If we compare camcontrol identify under 11.1 and 11.2 for same model we will
see no differences (in 11.2 new line Zoned-Device Commands no line).

protocol              ATA/ATAPI-10 SATA 3.x
device model          HGST HUS722T1TALA604
firmware revision     RAGNWA07
cylinders             16383
heads                 16
sectors/track         63
sector size           logical 512, physical 512, offset 0
LBA supported         268435455 sectors
LBA48 supported       1953525168 sectors
PIO supported         PIO4
DMA supported         WDMA2 UDMA6
media RPM             7200
Zoned-Device Commands no

Feature                      Support  Enabled   Value           Vendor
read ahead                     yes      yes
write cache                    yes      yes
flush cache                    yes      yes
overlap                        no
Tagged Command Queuing (TCQ)   no       no
Native Command Queuing (NCQ)   yes              32 tags
NCQ Queue Management           no
NCQ Streaming                  no
Receive & Send FPDMA Queued    yes
SMART                          yes      yes
microcode download             yes      yes
security                       yes      no
power management               yes      yes
advanced power management      yes      no      0/0x00
automatic acoustic management  no       no
media status notification      no       no
power-up in Standby            yes      no
write-read-verify              no       no
unload                         yes      yes
general purpose logging        yes      yes
free-fall                      no       no
Data Set Management (DSM/TRIM) no
Host Protected Area (HPA)      no

and Toshiba disk looks different

pass0: <TOSHIBA DT01ACA100 MS2OA750> ATA8-ACS SATA 3.x device
pass0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)

protocol              ATA/ATAPI-8 SATA 3.x
device model          TOSHIBA DT01ACA100
firmware revision     MS2OA750
cylinders             16383
heads                 16
sectors/track         63
sector size           logical 512, physical 4096, offset 0
LBA supported         268435455 sectors
LBA48 supported       1953525168 sectors
PIO supported         PIO4
DMA supported         WDMA2 UDMA6
media RPM             7200
Zoned-Device Commands no

Feature                      Support  Enabled   Value           Vendor
read ahead                     yes      yes
write cache                    yes      yes
flush cache                    yes      yes
overlap                        no
Tagged Command Queuing (TCQ)   no       no
Native Command Queuing (NCQ)   yes              32 tags
NCQ Queue Management           no
NCQ Streaming                  no
Receive & Send FPDMA Queued    no
SMART                          yes      yes
microcode download             yes      yes
security                       yes      no
power management               yes      yes
advanced power management      yes      no      0/0x00
automatic acoustic management  no       no
media status notification      no       no
power-up in Standby            yes      no
write-read-verify              no       no
unload                         no       no
general purpose logging        yes      yes
free-fall                      no       no
Data Set Management (DSM/TRIM) no
Host Protected Area (HPA)      yes      no      1953525168/1953525168
HPA - Security                 no

-- 
You are receiving this mail because:
You are the assignee for the bug.