Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Andrew Vasquez <praka@users.sourceforge.net>
To: linux-scsi@vger.kernel.org
Subject: Re: What's the "right" qla2100 driver?
Date: Wed, 21 Jan 2004 21:22:19 -0800	[thread overview]
Message-ID: <20040122052218.GA2405@praka.local.home> (raw)
In-Reply-To: <F888C30C3021D411B9DA00B0D0209BE8038F9BD1@cvo-exchange.cvo.roguewave.com>

On Wed, 21 Jan 2004, Poul Petersen wrote:

> I've got a Qlogic qla2100 card connected via copper to an array of
> 28 ~18GB disks. I'm trying to create two raid level 5 md devices
> with 13disk+1spare each. What I'm experiencing is a lot of hangs and
> strange disk failures that appear to be related to the drivers for
> the 2100. As there seems to be many different drivers to choose from
> for the qla2100, I've tried them all and collected my (all bad)
> experiences, a summary of which I have attached below. 
> 
> What I am wondering is if anyone else is using this card with Linux
> and if so what driver are they using? More importantly, which driver
> is actively being worked on (if any) so that I might contribute some
> failure information? 
> 

For 2.4, you could try another driver -- 6.06.10 (available at the
QLogic website).  This driver has support for the 2100 (though it's
not actually documented).  The makefile will not build the driver
though, try something similiar to the following:

	# make qla2100.o

For 2.6, why don't we start out with the default qla2xxx driver in
2.6.2-rc1.  

> It's possible that I am experiencing a hardware problem, since these
> disks and controller are a few years old now, but I doubt it since
> most of the errors seem inconsistent with bad hardware (all disks
> failing, etc). If nothing else, if I get feedback saying that
> someone else is successfully using a certain driver, then I can
> start playing with hardware using the same driver and maybe get to
> the bottom of this...
> 

>From there let's see how far you get with the drivers.  We may need to
enable some extra debugging for additional information.

> ---
> Test #5
> 2.6.1 with sourceforge qlogic driver 8.00.00.b8 (
> http://sourceforge.net/projects/linux-qla2xxx/ )
> ---
> 
> # modprobe qla2xxx
> # mkraid /dev/md0
> # mkraid /dev/md1
> # mkfs.ext3 /dev/md0
> 
>  	After awhile, the mkfs hung and when I tried to reboot the machine,
> I got a bunch of errors like the following for all 28 disks:
> 
> qla2xxx_eh_abort scsi(1:0:12:0) cmd_timeout_in_sec=0x1e.
> qla2xxx_eh_abort Exiting: status=Failed
> 

Interesting...

Regards,
Andrew Vasquez

  reply	other threads:[~2004-01-22  5:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  0:32 What's the "right" qla2100 driver? Poul Petersen
2004-01-22  5:22 ` Andrew Vasquez [this message]
     [not found] <F888C30C3021D411B9DA00B0D0209BE8038F9BD1@cvo-exchange.cvo. roguewave.com>
2004-01-22  0:40 ` Lincoln Dale
     [not found] <47F3C2BE74738E4683574107469DFA201DF5BF@XYUSEX01.xyus.xyrat ex.com>
2004-01-22  5:06 ` Lincoln Dale
  -- strict thread matches above, loose matches on Subject: below --
2004-01-22 22:54 Poul Petersen
2004-05-27  0:25 Poul Petersen

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=20040122052218.GA2405@praka.local.home \
    --to=praka@users.sourceforge.net \
    --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