mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Linux 5.9: smartpqi: controller is offline: status code 0x6100c
@ 2020-10-14 21:47 Paul Menzel
  2020-10-15 11:02 ` Thomas Kreitler
  2020-10-16 22:31 ` Don.Brace
  0 siblings, 2 replies; 4+ messages in thread
From: Paul Menzel @ 2020-10-14 21:47 UTC (permalink / raw)
  To: Don Brace
  Cc: James E. J. Bottomley, Martin K. Petersen, esc.storagedev,
	linux-scsi, LKML, it+linux-scsi

Dear Linux folks,


With Linux 5.9 and


     $ lspci -nn -s 89:
     89:00.0 Serial Attached SCSI controller [0107]: Adaptec Smart 
Storage PQI 12G SAS/PCIe 3 [9005:028f] (rev 01)
     $ more 
/sys/devices/pci0000:88/0000:88:00.0/0000:89:00.0/host15/scsi_host/host15/driver_version
     1.2.8-026
     $ more 
/sys/devices/pci0000:88/0000:88:00.0/0000:89:00.0/host15/scsi_host/host15/firmware_version
     2.62-0

the controller went offline with status code 0x6100c.

> Oct 14 14:54:01 done.molgen.mpg.de kernel: smartpqi 0000:89:00.0: controller is offline: status code 0x6100c
> Oct 14 14:54:01 done.molgen.mpg.de kernel: smartpqi 0000:89:00.0: controller offline
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:2:0: [sdu] tag#709 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:15:0: [sdah] tag#274 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:4:0: [sdw] tag#516 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:4:0: [sdw] tag#516 CDB: Write(10) 2a 00 0d e6 9e 88 00 00 01 00
> Oct 14 14:54:01 done.molgen.mpg.de kernel: blk_update_request: I/O error, dev sdw, sector 1865741376 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#529 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#529 CDB: Write(10) 2a 00 29 4e e8 ff 00 00 01 00
> Oct 14 14:54:01 done.molgen.mpg.de kernel: blk_update_request: I/O error, dev sds, sector 5544298488 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#627 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#627 CDB: Read(10) 28 00 5d df 2c 04 00 00 04 00
> Oct 14 14:54:01 done.molgen.mpg.de kernel: blk_update_request: I/O error, dev sds, sector 12599255072 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:5:0: [sdx] tag#567 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:5:0: [sdx] tag#567 CDB: Write(10) 2a 00 21 4e ce 04 00 00 04 00

How can the status code 0x6100c be deciphered?


Kind regards,

Paul

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Linux 5.9: smartpqi: controller is offline: status code 0x6100c
  2020-10-14 21:47 Linux 5.9: smartpqi: controller is offline: status code 0x6100c Paul Menzel
@ 2020-10-15 11:02 ` Thomas Kreitler
  2020-10-16 22:31 ` Don.Brace
  1 sibling, 0 replies; 4+ messages in thread
From: Thomas Kreitler @ 2020-10-15 11:02 UTC (permalink / raw)
  To: Paul Menzel; +Cc: linux-kernel

Hello Paul,

The meaning behind 0x6100c can be found rather easily.

 From drivers/scsi/smartpqi/smartpqi.h comes the main part

   #define PQI_DATA_IN_OUT_PCIE_COMPLETION_TIMEOUT  0x61

the rest looks like additional status bytes reported whilst the error is 
processed.

My conclusion is that something happened on the PCIe bus.

Best,
	Thomas


P.S.. Maybe it's worth mentioning, that the machine in question is 
fitted with two Microsemi HBA-1100 controllers.

On 2020-10-14 23:47, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> With Linux 5.9 and
> 
> 
>      $ lspci -nn -s 89:
>      89:00.0 Serial Attached SCSI controller [0107]: Adaptec Smart 
> Storage PQI 12G SAS/PCIe 3 [9005:028f] (rev 01)
>      $ more 
> /sys/devices/pci0000:88/0000:88:00.0/0000:89:00.0/host15/scsi_host/host15/driver_version 
> 
>      1.2.8-026
>      $ more 
> /sys/devices/pci0000:88/0000:88:00.0/0000:89:00.0/host15/scsi_host/host15/firmware_version 
> 
>      2.62-0
> 
> the controller went offline with status code 0x6100c.
> 
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: smartpqi 0000:89:00.0: 
>> controller is offline: status code 0x6100c
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: smartpqi 0000:89:00.0: 
>> controller offline
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:2:0: [sdu] tag#709 
>> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:15:0: [sdah] 
>> tag#274 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 
>> cmd_age=6s
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:4:0: [sdw] tag#516 
>> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:4:0: [sdw] tag#516 
>> CDB: Write(10) 2a 00 0d e6 9e 88 00 00 01 00
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: blk_update_request: I/O 
>> error, dev sdw, sector 1865741376 op 0x1:(WRITE) flags 0x0 phys_seg 1 
>> prio class 0
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#529 
>> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#529 
>> CDB: Write(10) 2a 00 29 4e e8 ff 00 00 01 00
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: blk_update_request: I/O 
>> error, dev sds, sector 5544298488 op 0x1:(WRITE) flags 0x0 phys_seg 1 
>> prio class 0
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#627 
>> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#627 
>> CDB: Read(10) 28 00 5d df 2c 04 00 00 04 00
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: blk_update_request: I/O 
>> error, dev sds, sector 12599255072 op 0x0:(READ) flags 0x1000 phys_seg 
>> 1 prio class
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:5:0: [sdx] tag#567 
>> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s
>> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:5:0: [sdx] tag#567 
>> CDB: Write(10) 2a 00 21 4e ce 04 00 00 04 00
> 
> How can the status code 0x6100c be deciphered?
> 
> 
> Kind regards,
> 
> Paul

-- 
Thomas Kreitler - Information Retrieval
kreitler@molgen.mpg.de
49/30/8413 1702

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Linux 5.9: smartpqi: controller is offline: status code 0x6100c
  2020-10-14 21:47 Linux 5.9: smartpqi: controller is offline: status code 0x6100c Paul Menzel
  2020-10-15 11:02 ` Thomas Kreitler
@ 2020-10-16 22:31 ` Don.Brace
  2020-11-08  8:11   ` Paul Menzel
  1 sibling, 1 reply; 4+ messages in thread
From: Don.Brace @ 2020-10-16 22:31 UTC (permalink / raw)
  To: pmenzel, don.brace
  Cc: jejb, martin.petersen, esc.storagedev, linux-scsi, linux-kernel,
	it+linux-scsi

The 6100C lockup is the result of the controller running out of commands to process new incoming requests from the driver.

We are actively looking into this issue.

We will keep you posted,
Thanks,
Don

-----Original Message-----
From: Paul Menzel [mailto:pmenzel@molgen.mpg.de] 
Sent: Wednesday, October 14, 2020 4:47 PM
To: Don Brace <don.brace@microsemi.com>
Cc: James E. J. Bottomley <jejb@linux.ibm.com>; Martin K. Petersen <martin.petersen@oracle.com>; esc.storagedev@microsemi.com; linux-scsi@vger.kernel.org; LKML <linux-kernel@vger.kernel.org>; it+linux-scsi@molgen.mpg.de
Subject: Linux 5.9: smartpqi: controller is offline: status code 0x6100c

EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

Dear Linux folks,


With Linux 5.9 and


     $ lspci -nn -s 89:
     89:00.0 Serial Attached SCSI controller [0107]: Adaptec Smart Storage PQI 12G SAS/PCIe 3 [9005:028f] (rev 01)
     $ more
/sys/devices/pci0000:88/0000:88:00.0/0000:89:00.0/host15/scsi_host/host15/driver_version
     1.2.8-026
     $ more
/sys/devices/pci0000:88/0000:88:00.0/0000:89:00.0/host15/scsi_host/host15/firmware_version
     2.62-0

the controller went offline with status code 0x6100c.

> Oct 14 14:54:01 done.molgen.mpg.de kernel: smartpqi 0000:89:00.0: 
> controller is offline: status code 0x6100c Oct 14 14:54:01 
> done.molgen.mpg.de kernel: smartpqi 0000:89:00.0: controller offline 
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:2:0: [sdu] tag#709 
> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s 
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:15:0: [sdah] 
> tag#274 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 
> cmd_age=6s Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:4:0: 
> [sdw] tag#516 FAILED Result: hostbyte=DID_NO_CONNECT 
> driverbyte=DRIVER_OK cmd_age=6s Oct 14 14:54:01 done.molgen.mpg.de 
> kernel: sd 15:0:4:0: [sdw] tag#516 CDB: Write(10) 2a 00 0d e6 9e 88 00 
> 00 01 00 Oct 14 14:54:01 done.molgen.mpg.de kernel: 
> blk_update_request: I/O error, dev sdw, sector 1865741376 op 
> 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Oct 14 14:54:01 
> done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#529 FAILED Result: 
> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s Oct 14 
> 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#529 CDB: 
> Write(10) 2a 00 29 4e e8 ff 00 00 01 00 Oct 14 14:54:01 
> done.molgen.mpg.de kernel: blk_update_request: I/O error, dev sds, 
> sector 5544298488 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Oct 
> 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#627 
> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s 
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:0:0: [sds] tag#627 
> CDB: Read(10) 28 00 5d df 2c 04 00 00 04 00 Oct 14 14:54:01 
> done.molgen.mpg.de kernel: blk_update_request: I/O error, dev sds, 
> sector 12599255072 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:5:0: [sdx] tag#567 
> FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=6s 
> Oct 14 14:54:01 done.molgen.mpg.de kernel: sd 15:0:5:0: [sdx] tag#567 
> CDB: Write(10) 2a 00 21 4e ce 04 00 00 04 00

How can the status code 0x6100c be deciphered?


Kind regards,

Paul

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Linux 5.9: smartpqi: controller is offline: status code 0x6100c
  2020-10-16 22:31 ` Don.Brace
@ 2020-11-08  8:11   ` Paul Menzel
  0 siblings, 0 replies; 4+ messages in thread
From: Paul Menzel @ 2020-11-08  8:11 UTC (permalink / raw)
  To: Don.Brace, don.brace
  Cc: jejb, martin.petersen, esc.storagedev, linux-scsi, linux-kernel,
	it+linux-scsi, Donald Buczek

Dear Don,


Am 17.10.20 um 00:31 schrieb Don.Brace@microchip.com:
> The 6100C lockup is the result of the controller running out of
> commands to process new incoming requests from the driver.
> 
> We are actively looking into this issue.

Unfortunately, there has not been any further reply by the Microsemi 
support, and the driver 1.2.14-016 does not built against Linux 5.9 or 
master.

Were you able to reproduce the issue? What is the timeline to getting 
this fixed?

Linux 5.10 is going to be a long-term support release, so it would be 
great to have the problems fixed as soon as possible.


Kind regards,

Paul

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-11-08  8:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-14 21:47 Linux 5.9: smartpqi: controller is offline: status code 0x6100c Paul Menzel
2020-10-15 11:02 ` Thomas Kreitler
2020-10-16 22:31 ` Don.Brace
2020-11-08  8:11   ` Paul Menzel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®