Bug 179341 - mpt3sas: LSISAS3008 don't see Intel 540s SSD
Summary: mpt3sas: LSISAS3008 don't see Intel 540s SSD
Status: RESOLVED OBSOLETE
Alias: None
Product: SCSI Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: Tejun Heo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-20 20:09 UTC by Badalyan Vyacheslav
Modified: 2016-12-27 23:08 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.8.9-1.el7.elrepo.x86_64
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Dmes wiyh loh (208.81 KB, application/octet-stream)
2016-11-20 00:17 UTC, Badalyan Vyacheslav
Details

Description Badalyan Vyacheslav 2016-10-20 20:09:39 UTC
Intel SSD 540s work on another PC ok! I flash firmware on SSD in last version. Try another port. Not work. Intel SSD 535 work ok!


[root@nas ~]# dmesg | grep LSI
[    3.366259] mpt3sas_cm0: LSISAS3008: FWVersion(13.00.00.00), ChipRevision(0x02), BiosVersion(08.31.00.00)
[   19.670940] mpt3sas_cm1: LSISAS3008: FWVersion(13.00.00.00), ChipRevision(0x02), BiosVersion(08.31.00.00)


This if i plug and unplug in dmesg

[  190.653903] mpt3sas_cm0: removing handle(0x0009), sas_addr(0x4433221100000000)
[  190.655213] mpt3sas_cm0: removing : enclosure logical id(0x500062b201056c80), slot(3)
[  190.656483] mpt3sas_cm0: removing enclosure level(0x0000), connector name(     )
[  192.435163] mpt3sas_cm1: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  193.935316] mpt3sas_cm1: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  195.435267] mpt3sas_cm1: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  196.935569] mpt3sas_cm1: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  196.937801] mpt3sas_cm1: removing handle(0x0010), sas_addr(0x4433221103000000)
[  196.937803] mpt3sas_cm1: removing enclosure logical id(0x500062b201056cc0), slot(1)
[  196.937804] mpt3sas_cm1: removing enclosure level(0x0000), connector name(     )
[  258.440317] mpt3sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  259.940595] mpt3sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  261.440619] mpt3sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  262.940703] mpt3sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[  262.943371] mpt3sas_cm0: removing handle(0x0009), sas_addr(0x4433221100000000)
[  262.945337] mpt3sas_cm0: removing enclosure logical id(0x500062b201056c80), slot(3)
[  262.947297] mpt3sas_cm0: removing enclosure level(0x0000), connector name(     )



[root@nas ~]# lsscsi
[0:0:0:0]    disk    ATA      INTEL SSDSC2CW24 400i  /dev/sda
[0:0:2:0]    disk    ATA      INTEL SSDSC2BW24 DC32  /dev/sdb
[0:0:3:0]    disk    ATA      INTEL SSDSC2BW24 DC32  /dev/sdc
[0:0:4:0]    disk    ATA      INTEL SSDSC2BW24 DC32  /dev/sdd
[0:0:5:0]    disk    ATA      INTEL SSDSC2CW24 400i  /dev/sde
[0:0:6:0]    disk    ATA      INTEL SSDSC2CW24 400i  /dev/sdf
[0:0:7:0]    disk    ATA      INTEL SSDSC2CW24 400i  /dev/sdg
[1:0:0:0]    cd/dvd  MATSHITA DVD-ROM UJ890AC  1.00  /dev/sr0
[5:0:0:0]    disk    ATA      ST3000DM001-1CH1 CC27  /dev/sdh
[5:0:1:0]    disk    ATA      ST2000DM001-1ER1 CC26  /dev/sdi
[5:0:2:0]    disk    ATA      ST2000DM001-1ER1 CC26  /dev/sdj
[5:0:3:0]    disk    ATA      ST2000NC001-1DY1 CN01  /dev/sdk
[5:0:4:0]    disk    ATA      ST2000NC001-1DY1 CN01  /dev/sdl
[5:0:5:0]    disk    ATA      ST3000DM001-1CH1 CC27  /dev/sdm
[5:0:6:0]    disk    ATA      ST3000DM001-1CH1 CC27  /dev/sdn
Comment 1 Badalyan Vyacheslav 2016-10-21 01:07:28 UTC
I was change product and component
Comment 2 Badalyan Vyacheslav 2016-10-21 01:13:27 UTC
        Adapter Selected is a Avago SAS: SAS3008(C0)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS3008(C0)  13.00.00.00    0b.02.00.03    08.31.00.00     00:0a:00:00
1  SAS3008(C0)  13.00.00.00    0b.02.00.03    08.31.00.00     00:08:00:00
Comment 3 Badalyan Vyacheslav 2016-11-20 00:17:15 UTC
Created attachment 245171 [details]
Dmes wiyh loh
Comment 4 Badalyan Vyacheslav 2016-11-20 13:38:52 UTC
I was attach log in BZ
Comment 5 Badalyan Vyacheslav 2016-11-22 04:31:58 UTC
   13.434720] mpt3sas_cm0: device status change: (internal device reset)
        handle(0x0009), sas address(0x4433221100000000), tag(65535)

[   13.464810] scsi 0:0:1:0: tag#0 CDB: Inquiry 12 00 00 00 24 00
[   13.464844] mpt3sas_cm0:     sas_address(0x4433221100000000), phy(0)
[   13.464846] mpt3sas_cm0:     enclosure_logical_id(0x500062b201056c80),slot(3)
[   13.464847] mpt3sas_cm0:     enclosure level(0x0000), connector name(     ^E)
[   13.464849] mpt3sas_cm0:     handle(0x0009), ioc_status(scsi ioc terminated)(0x004b), smid(1)
[   13.464850] mpt3sas_cm0: Device Status Change
[   13.464852] mpt3sas_cm0:     request_len(36), underflow(0), resid(36)
[   13.464854] mpt3sas_cm0:     tag(0), transfer_count(0), sc->result(0x000b0000)
[   13.464855] mpt3sas_cm0:     scsi_status(good)(0x00), scsi_state(state terminated no status )(0x0c)
[   13.464861] mpt3sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000)
[   13.464867] mpt3sas_cm0: device status change: (internal device reset complete)
        handle(0x0009), sas address(0x4433221100000000), tag(65535)
Comment 6 Chaitra P B 2016-11-22 10:46:57 UTC
Badalyan,
 From attached driver logs, I could see FW is issuing internal device reset many times for the drive with handle (0x0009) and also Inquiry command for this particular drive is getting terminated.

There are many reasons for which Fimware sends internal device reset. 
And hence we need Firmware logs to find out reason for internal device reset, also Inquiry command is getting terminated because it is issued during device reset is in progress.

Please share Firmware logs to debug/analyse this issue further.
Comment 7 Badalyan Vyacheslav 2016-11-22 11:11:19 UTC
Help is needed. How to get a log FW? 

This is "SAS 9300-16i Host Bus Adapter" and not have any HW RAID. 

[root@nas sas3ircu_linux_x64_rel]# ./sas3ircu 0 LOGIR
Avago Technologies SAS3 IR Configuration Utility.
Version 14.00.00.00 (2016.07.21)
Copyright (c) 2009-2016 Avago Technologies. All rights reserved.

SAS3IRCU: The LOGIR command is not supported by the firmware currently loaded on controller 0.

[root@nas sas3ircu_linux_x64_rel]# ./sas3ircu list
Avago Technologies SAS3 IR Configuration Utility.
Version 14.00.00.00 (2016.07.21)
Copyright (c) 2009-2016 Avago Technologies. All rights reserved.


         Adapter      Vendor  Device                       SubSys  SubSys
 Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
 -----  ------------  ------  ------  -----------------    ------  ------
   0     SAS3008       1000h   97h    00h:0ah:00h:00h      1000h   3130h

         Adapter      Vendor  Device                       SubSys  SubSys
 Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
 -----  ------------  ------  ------  -----------------    ------  ------
   1     SAS3008       1000h   97h    00h:08h:00h:00h      1000h   3130h
SAS3IRCU: Utility Completed Successfully.
Comment 8 Chaitra P B 2016-11-23 06:09:59 UTC
(In reply to Badalyan Vyacheslav from comment #7)
> Help is needed. How to get a log FW? 
> 
> This is "SAS 9300-16i Host Bus Adapter" and not have any HW RAID. 
> 
> [root@nas sas3ircu_linux_x64_rel]# ./sas3ircu 0 LOGIR
> Avago Technologies SAS3 IR Configuration Utility.
> Version 14.00.00.00 (2016.07.21)
> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
> 
> SAS3IRCU: The LOGIR command is not supported by the firmware currently
> loaded on controller 0.
> 
> [root@nas sas3ircu_linux_x64_rel]# ./sas3ircu list
> Avago Technologies SAS3 IR Configuration Utility.
> Version 14.00.00.00 (2016.07.21)
> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
> 
> 
>          Adapter      Vendor  Device                       SubSys  SubSys
>  Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
>  -----  ------------  ------  ------  -----------------    ------  ------
>    0     SAS3008       1000h   97h    00h:0ah:00h:00h      1000h   3130h
> 
>          Adapter      Vendor  Device                       SubSys  SubSys
>  Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
>  -----  ------------  ------  ------  -----------------    ------  ------
>    1     SAS3008       1000h   97h    00h:08h:00h:00h      1000h   3130h
> SAS3IRCU: Utility Completed Successfully.

Badalyan,

Connect UART to controller, then open Teraterm window & use below commands: 
"iop show diag" -> outputs ring buffer and trace buffer.
"pl dbg" -> outputs other debug info.
Comment 9 Badalyan Vyacheslav 2016-12-27 23:07:13 UTC
Its production server. You can close bug. I move to nvme ssd.

Note You need to log in before you can comment on or make changes to this bug.