public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: James.Smart@Emulex.Com, linux-scsi@vger.kernel.org
Subject: Re: lpfc: System freezing if fiber is broken
Date: Tue, 26 Jul 2005 11:48:00 -0700	[thread overview]
Message-ID: <20050726184800.GA19810@us.ibm.com> (raw)
In-Reply-To: <42E679A2.1060408@fujitsu-siemens.com>

Bodo Stroesser [bstroesser@fujitsu-siemens.com] wrote:
> Hi James,
> 
> disrupting a working FC connection makes my i386 SMP server
> (2.6.12.2) freeze just one or two seconds after this.
> I'm normally using lpfc_nodev_tmo = 1. When I change this to the
> default value of 35, the system stalls about 36 seconds after
> disruption. So I guess, the problem is caused by nodev_tmo
> expiring.
> I activated the nmi_watchdog, but no output.
> 
> What can I do to analyze this problem?

Does changing the timeout for a scsi device also alter the problem. In the
past people have seen issues of the nodev_tmo expiring near the scsi
timeout. This past cases lead to devices being offlined, but may this
could be causing a different symptom on your system.

You can change the timeout for the device by echoing a higher value into
/sys/bus/scsi/devices/${nexus}/timeout.

Is this a full system freeze or only the controlling console?

-andmike
--
Michael Anderson
andmike@us.ibm.com

  reply	other threads:[~2005-07-26 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 17:57 lpfc: System freezing if fiber is broken Bodo Stroesser
2005-07-26 18:48 ` Mike Anderson [this message]
2005-07-27 13:45   ` Bodo Stroesser

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=20050726184800.GA19810@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Smart@Emulex.Com \
    --cc=bstroesser@fujitsu-siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox