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@xxxxxxxxxxxxx] Sent: Wednesday, October 14, 2020 4:47 PM To: Don Brace <don.brace@xxxxxxxxxxxxx> Cc: James E. J. Bottomley <jejb@xxxxxxxxxxxxx>; Martin K. Petersen <martin.petersen@xxxxxxxxxx>; esc.storagedev@xxxxxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx; LKML <linux-kernel@xxxxxxxxxxxxxxx>; it+linux-scsi@xxxxxxxxxxxxx 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
