Skip to contentSkip to conversation

mpt3sas: LSISAS3008 don't see Intel 540s SSD

Bug 179341 [email protected] 2 participants 12 messages Oct 21, 2016 – Dec 27, 2016 1 message not in the archive SCSI

lore
Share & tools
lore
#2 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=179341

--- Comment #2 from Badalyan Vyacheslav <[email protected]> ---
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
Signature · 2 lines
You are receiving this mail because:
You are watching someone on the CC list of the bug.
#3 lore raw

Hi,
Please share driver logs with logging_level set to "0x3f8".

If driver cannot be unloaded and loaded,then the module parameter has to be passed as kernel command line in the boot loader as “mpt3sas.logging_level=0x3F8” else if driver module can be unloaded and loaded then simply give logging_level=0x3F8 for insmod or modprobe.

Thanks,
Chaitra

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Friday, October 21, 2016 6:43 AM
To: [email protected]
Subject: [Bug 179341] mpt3sas: LSISAS3008 don't see Intel 540s SSD

https://bugzilla.kernel.org/show_bug.cgi?id=179341

--- Comment #2 from Badalyan Vyacheslav <[email protected]> ---
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

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html

#6 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=179341

--- Comment #5 from Badalyan Vyacheslav <[email protected]> ---
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)
Signature · 2 lines
You are receiving this mail because:
You are watching someone on the CC list of the bug.
#8 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=179341

Chaitra P B <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
                   |                            |m

--- Comment #6 from Chaitra P B <[email protected]> --- 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.

Signature · 2 lines
You are receiving this mail because:
You are watching someone on the CC list of the bug.
#9 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=179341

--- Comment #7 from Badalyan Vyacheslav <[email protected]> --- 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.

Signature · 2 lines
You are receiving this mail because:
You are watching someone on the CC list of the bug.
#10 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=179341

--- Comment #8 from Chaitra P B <[email protected]> --- (In reply to Badalyan Vyacheslav from comment #7)

Quoted 23 lines

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
Quoted 5 lines
         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.

Signature · 2 lines
You are receiving this mail because:
You are watching someone on the CC list of the bug.