mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Maxim Kozover <maximkoz@netvision.net.il>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: Re[8]: problems with scsi_transport_fc and qla2xxx
Date: Sun, 12 Mar 2006 10:28:03 +0100	[thread overview]
Message-ID: <1142155684.2882.15.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1699632492.20060312001014@netvision.net.il>

On Sun, 2006-03-12 at 00:10 +0300, Maxim Kozover wrote:
> Hi Andrew!
> Congratulations! The kernel from scsi-rc-fixes git and your patch are
> working.
> By the way, could you, please, tell me how I get only scsi patches
> from the git repository, cause I got the whole kernel by using
> cg-clone http://kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
> 
> Now the process looks like following:
> Mar 11 23:54:22 multipath kernel: qla2xxx 0000:03:01.0: LOOP DOWN detected (2).
> Mar 11 23:54:28 multipath kernel:  rport-4:0-0: blocked FC remote port time out:
>  removing target and saving binding
> Mar 11 23:54:37 multipath kernel: qla2xxx 0000:03:01.0: LIP reset occured (f7f7).
> Mar 11 23:54:37 multipath kernel: qla2xxx 0000:03:01.0: LOOP UP detected (2 Gbps).
> Mar 11 23:54:59 multipath kernel:  4:0:0:0: timing out command, waited 22s
> 
> And the disks appear.
> Could you tell me, please, where this 22sec timeout came from?

looks like your fiber fabric decided to renegotiate, and halfway it went
for a coffee and donuts break to not upset the union rules :)

I've seen LOOP negotiations take 10+ seconds before, and that is on a
really simple setup.... so nothing super special 


  reply	other threads:[~2006-03-12  9:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 12:05 Maxim Kozover
2006-02-27 18:05 ` Maxim Kozover
2006-03-01  6:14   ` Andrew Morton
2006-03-01 20:25     ` Stefan Kaltenbrunner
2006-03-01 21:08       ` Andrew Vasquez
2006-03-02 16:32         ` Maxim Kozover
2006-03-02 17:38           ` Andrew Vasquez
2006-03-02 22:15             ` Maxim Kozover
2006-03-06 19:06               ` Andrew Vasquez
2006-03-06 20:00           ` Mike Snitzer
2006-03-06 20:09             ` Maxim Kozover
2006-03-06 21:28               ` Andrew Vasquez
2006-03-06 20:57                 ` Maxim Kozover
2006-03-06 21:09                 ` Maxim Kozover
     [not found]                   ` <20060306232831.GS6278@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                     ` <1219491790.20060307124035@netvision.net.il>
     [not found]                       ` <20060307172227.GE6275@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                         ` <1343850424.20060307231141@netvision.net.il>
     [not found]                           ` <20060308080050.GF9956@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                             ` <20060308154341.GA1779@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                               ` <1502511597.20060308213247@netvision.net.il>
     [not found]                                 ` <20060310231344.GB641@andrew-vasquezs-powerbook-g4-15.local>
2006-03-11 21:10                                   ` Re[8]: " Maxim Kozover
2006-03-12  9:28                                     ` Arjan van de Ven [this message]
2006-03-12 11:46                                       ` Maxim Kozover
2006-03-13 23:19                                     ` Andrew Vasquez
2006-03-20 10:45                                       ` Maxim Kozover

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=1142155684.2882.15.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maximkoz@netvision.net.il \
    /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®