All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Krotov <kkv@clodo.ru>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: threads scsi_eh_ and scsi_tmf_ don't die when ib_srp reconnect
Date: Wed, 12 Aug 2015 08:15:32 +0300	[thread overview]
Message-ID: <55CAD674.4040104@clodo.ru> (raw)
In-Reply-To: <55CA5AD4.8080109@sandisk.com>



11.08.2015 23:28, Bart Van Assche пишет:
> On 08/11/2015 06:41 AM, Konstantin Krotov wrote:
>> Hello, thanks for reply.
>>
>> I build a package version 2.0.34, but problem is reproduced:
>> [  260.266374] scsi host15: ib_srp: REJ received
>> [  260.266383] scsi host15: ib_srp: SRP LOGIN from
>> fe80:0000:0000:0000:0002:c903:0008:c884 to
>> fe80:0000:0000:0000:0002:c903:0009:c1a0 REJECTED, reason 0x00010001
>> [  260.266588] scsi host15: ib_srp: Connection 0/8 failed
>> [  260.266700] scsi host15: ib_srp: Sending CM DREQ failed
>>
>> and increases the number of threads scsi_tmf_ and scsi_eh_ at every
>> reconnect..
>
> Hello Konstantin,
>
> I have tried to reproduce this but without success so far. Whether I
> install upstream kernel v4.2-rc6 or another kernel version +
> ib_srp-backport on the initiator system, the result is the same when I
> block SRP login on the target system: the ib_srp driver keeps trying to
> log in without creating new SCSI hosts.

> Are you using a kernel from Greg KH's stable repository or another kernel ? And to which values were the
yes, sources from upstream, 3.19.1

> ib_srp kernel module parameters set (cat /etc/modprobe.d/ib_srp.conf) ?
srp.konf missing, i load modules with the default settings:
allow_ext_sg:N
ch_count:0
cmd_sg_entries:12
dev_loss_tmo:600
enable_imm_data:Y
fast_io_fail_tmo:15
indirect_sg_entries:12
prefer_fr:N
reconnect_delay:20
register_always:N
srp_sg_tablesize:0
topspin_workarounds:1

>
> Bart.

-- 
WBR
Konstantin V. Krotov

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-08-12  5:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 15:18 threads scsi_eh_ and scsi_tmf_ don't die when ib_srp reconnect Konstantin Krotov
2015-08-10 15:30 ` Bart Van Assche
2015-08-11 13:40   ` Konstantin Krotov
2015-08-11 20:28     ` Bart Van Assche
2015-08-12  5:15       ` Konstantin Krotov [this message]
2015-08-12 16:50         ` Bart Van Assche
2015-08-14  9:06           ` Konstantin Krotov
2015-08-14 16:10             ` Bart Van Assche

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=55CAD674.4040104@clodo.ru \
    --to=kkv@clodo.ru \
    --cc=bart.vanassche@sandisk.com \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.