public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Pepper <tpepper@vato.org>
To: Mark Bellon <mbellon@mvista.com>
Cc: sdake@mvista.com, Chris Worley <cworley@lnxi.com>,
	linux-scsi@vger.kernel.org
Subject: Re: Qlogic driver hang
Date: Thu, 2 Oct 2003 12:24:39 -0700	[thread overview]
Message-ID: <20031002122439.A17312@jose.vato.org> (raw)
In-Reply-To: <3F7C6D9C.2000205@mvista.com>; from mbellon@mvista.com on Thu, Oct 02, 2003 at 11:25:32AM -0700

On Thu 02 Oct at 11:25:32 -0700 mbellon@mvista.com done said:
> >
> >
> >At one point some code was added to enable parity on the chip.  This may
> >be the cause of the hang.  Try disabling parity checking in the driver.

I think too that different bios flash version have different settings for
enabling/disabling parity (and other things) that can make a difference.
The latest on their webpage is 1.34.  I understand the firmware which the
driver downloads at load time still uses certain bits from the version
flashed to the card.  Somewhere around bios 1.2x (where x was something
high..it's been a while) I had some hangs go away.  All the new cards
I've gotten appear to ship with ancient BIOS's and sorely need flashing.

Tim
-- 
*********************************************************
*  tpepper@vato dot org             * Venimus, Vidimus, *
*  http://www.vato.org/~tpepper     * Dolavimus         *
*********************************************************

  reply	other threads:[~2003-10-02 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B179AE41C1147041AA1121F44614F0B060ED34@AVEXCH02.qlogic.org>
2003-10-02 15:45 ` Qlogic driver hang Chris Worley
2003-10-02 18:16   ` Steven Dake
2003-10-02 18:25     ` Mark Bellon
2003-10-02 19:24       ` Tim Pepper [this message]
2003-10-02 19:43         ` Mark Bellon
2003-10-03  5:53   ` Andrew Vasquez
2003-10-03 18:15   ` Andrew Vasquez

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=20031002122439.A17312@jose.vato.org \
    --to=tpepper@vato.org \
    --cc=cworley@lnxi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mbellon@mvista.com \
    --cc=sdake@mvista.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