linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arun Easi <aeasi@marvell.com>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: Saurav Kashyap <skashyap@marvell.com>,
	Nilesh Javali <njavali@marvell.com>,
	<GR-QLogic-Storage-Upstream@marvell.com>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<regressions@lists.linux.dev>
Subject: Re: [REGRESSION] qla2xxx: tape drive not removed after unplug FC cable
Date: Fri, 27 May 2022 17:27:27 -0700	[thread overview]
Message-ID: <alpine.LRH.2.21.9999.2205271524460.4730@mvluser05.qlc.com> (raw)
In-Reply-To: <baef87c3-5dad-3b47-44c1-6914bfc90108@cybernetics.com>

[-- Attachment #1: Type: text/plain, Size: 2590 bytes --]

Hi Tony,

Thanks for reporting the issue. We are trying to recreate this issue in 
house. I will reach out to you for logs, if we cannot repro. Typically, we 
get sufficient context to the issue when the problem is reproduced with 
module parameter "ql2xextended_error_logging=1".

Anyway, I will let you know the status.

Regards,
-Arun

On Wed, 25 May 2022, 3:03pm, Tony Battersby wrote:

> #regzbot introduced: 44c57f205876
> 
> I have several different QLogic FC HBAs (8, 16, 32 Gbps) and several
> different FC LTO tape drives (IBM Ultrium 8 & 9).  When I plug in the FC
> cable, the tape drive shows up as a SCSI device as expected.  With older
> kernels, when I unplug the FC cable, the tape drive SCSI device would
> disappear after about 30 seconds.  But with newer kernels (including
> 5.18), when I unplug the FC cable, the tape drive SCSI device never
> disappears.  I have bisected the change in behavior to the following
> commit in kernel 5.15:
> 
> 44c57f205876 ("scsi: qla2xxx: Changes to support FCP2 Target")
> 
> This commit has been backported to various -stable kernels, so they are
> also affected.
> 
> When testing with two different tape drives:
> 1) Plug FC cable into tape drive A.  Tape drive A shows up as a SCSI device.
> 2) Unplug FC cable; wait 60 seconds.  Tape drive A does not disappear.
> 3) Plug FC cable into tape drive B.  Tape drive A disappears 30 seconds
> later, but tape drive B does not show up.
> 4) Unplug FC cable and plug it back into tape drive B.  Tape drive B
> shows up as a SCSI device.
> 
> So I can actually make a tape drive disappear by plugging the cable into
> a different tape drive, but then I have to reseat the cable again to
> make the new tape drive show up.
> 
> lspci -n
> 83:00.0 0c04: 1077:2031 (rev 02)
> 83:00.1 0c04: 1077:2031 (rev 02)
> 
> When plugging in cable:
> qla2xxx [0000:83:00.1]-500a:7: LOOP UP detected (8 Gbps).
> 
> When unplugging cable with old kernel:
> qla2xxx [0000:83:00.1]-500b:7: LOOP DOWN detected (2 7 0 0).
> rport-7:0-2: blocked FC remote port time out: removing target and saving binding
> 
> When unplugging cable with new kernel:
> qla2xxx [0000:83:00.1]-500b:7: LOOP DOWN detected (2 7 0 0).
> 
> /sys/class/fc_remote_ports/rport-*/
> dev_loss_tmo: 30
> supported_classes: Class 3
> port_state: Online
> (port_state remains Online even when FC cable unplugged)
> 
> /proc/scsi/scsi
> Host: scsi7 Channel: 00 Id: 01 Lun: 00
>   Vendor: IBM      Model: ULTRIUM-HH8      Rev: K4K1
>   Type:   Sequential-Access                ANSI  SCSI revision: 06
> 
> Tony Battersby
> Cybernetics
> 
> 

  reply	other threads:[~2022-05-28  0:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 22:03 [REGRESSION] qla2xxx: tape drive not removed after unplug FC cable Tony Battersby
2022-05-28  0:27 ` Arun Easi [this message]
2022-06-20  6:56   ` Thorsten Leemhuis
2022-06-20 14:33     ` Tony Battersby
2022-06-21 22:05       ` [EXT] " Arun Easi
2022-06-22 14:56         ` Tony Battersby
2022-06-22 23:03           ` Arun Easi
2022-07-04 12:06             ` Thorsten Leemhuis
2022-07-06 17:29               ` Arun Easi

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=alpine.LRH.2.21.9999.2205271524460.4730@mvluser05.qlc.com \
    --to=aeasi@marvell.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=njavali@marvell.com \
    --cc=regressions@lists.linux.dev \
    --cc=skashyap@marvell.com \
    --cc=tonyb@cybernetics.com \
    /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;
as well as URLs for NNTP newsgroup(s).