[Bug 212914] CAM: SATA drives are getting deleted and then re-added after controller rescan

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 212914
           Summary: CAM: SATA drives are getting deleted and then re-added
                    after controller rescan
           Product: Base System
           Version: 11.0-RC1
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: kashyap.desai at broadcom.com

This issue is even common for LSI/Broadcom IT HBA (mpr driver), so looks to be
a common issue. 

If you have SATA drive and just do "camcontrol rescan all", SATA disc is added
and removed back by CAM layer.


On FreeBSD11.0 RC1, we are facing an issue where SATA drives connected behind
LSI's MegaRAID controller getting deleted and added back after controller
reset.
I am using Broadcom/Avago/LSI's  MegaRAID Invader controller(device ID-
0x005d). The point to note here is- this behavior is not observed with SAS
drives on FreeBSD11.0-RC1.
Also on FreeBSD10.3 this behavior is not at all observed on SATA as well.
We are debugging the issue but it would be much helpful if we can get quick
inputs/pointers.

Please find below the detailed information-

OS: FreeBSD 11.0 RC1
Controller: LSI's MegaRAID invader controller

Connected devices list:

root at freeBSD11:~ # camcontrol devlist
<ST500NM0011 PA09>                 at scbus5 target 0 lun 0 (pass0,ada0)
<AHCI SGPIO Enclosure 1.00 0001>   at scbus6 target 0 lun 0 (ses0,pass1)
<ATA ST9250610NS SN01>             at scbus8 target 51 lun 0
(da9,pass11)----------------------------------------->this is SATA drive which
is getting deleted and re-added post controller reset
<SEAGATE ST9300605SS 0004>         at scbus8 target 163 lun 0 (da8,pass10)
<LSI Default 5.00>                 at scbus9 target 0 lun 0 (da6,pass8)
<LSI Default 5.00>                 at scbus9 target 1 lun 0 (da2,pass4)
<LSI Default 5.00>                 at scbus9 target 2 lun 0 (da0,pass2)
<LSI Default 5.00>                 at scbus9 target 3 lun 0 (da7,pass9)
<LSI Default 5.00>                 at scbus9 target 4 lun 0 (da3,pass5)
<LSI Default 5.00>                 at scbus9 target 5 lun 0 (da1,pass3)
<SEAGATE ST600MP0005 VS09>         at scbus10 target 48 lun 0 (da4,pass6)
<SEAGATE ST600MP0005 VS09>         at scbus10 target 54 lun 0 (da5,pass7)


Relevant dmesg logs snippet(da9 is SATA drive which is getting deleted and
added back):

================================
mrsas0: Initiaiting OCR because of FW fault!
mrsas0: Waiting for FW to come to ready state
mrsas0: Jbod map is supported
mrsas0: Reset successful
da9 at mrsas0 bus 1 scbus8 target 51 lun 0
da9: <ATA ST9250610NS SN01> s/n 9XE02AR2 detached
(da9:mrsas0:1:51:0): Periph destroyed
(da9:mrsas0:1:51:0): UNMAPPED
(da9:mrsas0:1:51:0): fatal error, could not acquire reference count
g_access(918): provider da9 has error
g_access(918): provider da9 has error
g_access(918): provider da9 has error
(da9:mrsas0:1:51:0): UNMAPPED
da9 at mrsas0 bus 1 scbus8 target 51 lun 0
da9: <ATA ST9250610NS SN01> Fixed Direct Access SPC-4 SCSI device
da9: Serial Number 9XE02AR2
da9: 150.000MB/s transfers
da9: 238475MB (488397168 512 byte sectors) =================================

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