From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 196543] Adaptec 6405H can not understand Queue full message
from Disks.
Date: Mon, 31 Jul 2017 06:03:41 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Return-path:
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:33372 "EHLO
mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1751307AbdGaGDm (ORCPT
);
Mon, 31 Jul 2017 02:03:42 -0400
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id ABA3E28573
for ; Mon, 31 Jul 2017 06:03:41 +0000 (UTC)
In-Reply-To:
Sender: linux-scsi-owner@vger.kernel.org
List-Id: linux-scsi@vger.kernel.org
To: linux-scsi@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=196543
--- Comment #1 from James.Bottomley@HansenPartnership.com ---
On Mon, 2017-07-31 at 02:26 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196543
>
> Bug ID: 196543
> Summary: Adaptec 6405H can not understand Queue full
> message
> from Disks.
> Product: IO/Storage
> Version: 2.5
> Kernel Version: 4.11.11(Fedora26 Kernel)/3.10.0(RHEL 7.3)
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: SCSI
> Assignee: linux-scsi@vger.kernel.org
> Reporter: kiyomi.kakitsubata@gmail.com
> Regression: No
>
> Hi
>
> I happened something different caused by SAS HBA.
> Adaptec 6405H can not understand Queue full message send by Disks.
>
> Perhaps, normally, any other HBA receive Queue full message from SAS
> disks, it will wait send some command to disks. But Adaptec 6405H is
> not wait send command to disks, so, happen disk time out.
>
> I think driver or firmware's bug,because other HBA like using
> mpt3sas, is not happened.
>
> If you need,perhaps I will give SAS bus trace.
A bus trace might help. The problem with the analysis above is that
QUEUE_FULL isn't handled in the driver or the transport, it's handled
at the scsi mid-layer level since it's a SCSI status return. There
doesn't seem to be anywhere in the 94xx driver where it intercepts
queue full, so for what you theorise to be the problem, the intercept
would either have to be in firmware, or there would have to be some
generic problem in the mid-layer. We might be able to track it down,
but we'd need more data.
James
--
You are receiving this mail because:
You are the assignee for the bug.