From: Thomas Kreitler <kreitler@molgen.mpg.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 5.9: smartpqi: controller is offline: status code 0x6100c
Date: Thu, 15 Oct 2020 13:02:49 +0200 [thread overview]
Message-ID: <c896f44d-637b-58ff-46ab-efb1891ca16c@molgen.mpg.de> (raw)
In-Reply-To: <bc10fad1-2353-7326-c782-7a45882fd791@molgen.mpg.de>
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
next prev parent reply other threads:[~2020-10-15 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 21:47 Paul Menzel
2020-10-15 11:02 ` Thomas Kreitler [this message]
2020-10-16 22:31 ` Don.Brace
2020-11-08 8:11 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c896f44d-637b-58ff-46ab-efb1891ca16c@molgen.mpg.de \
--to=kreitler@molgen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®