linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe@lineo.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Qlogic Fiber Channel
Date: Fri, 29 Jun 2001 15:19:10 +0200	[thread overview]
Message-ID: <20010629151910.C27847@pc8.lineo.fr> (raw)
In-Reply-To: <061801c10089$a5e89fd0$e1de11cc@csihq.com>
In-Reply-To: <061801c10089$a5e89fd0$e1de11cc@csihq.com>; from mblack@csihq.com on Fri, Jun 29, 2001 at 12:52:53 +0200

The qlogicfc driver is based on the chris loveland work.
You can find outdated information here :
	http://www.iol.unh.edu/consortiums/fc/linux/qlogic.html

>From my point of view, this driver is sadly broken. The fun part is that
the qlogic driver is certainly based on this one too (look at the code, the
drivers differs not so much). 
If you don't need IP support then keep using the qlogic driver which is far
better. I'm pretty sure that they have a working IP enhanced version but
for an unknow reason this one is not released. And without the IP-enhanced
firmware we can do nothing.

I've unsuccessfully tried to get information from qlogic and others a few
weeks ago. 
IMHO the qlogicfc driver should be removed from the kernel tree and perhaps
replaced by the last qlogic one. We then lost the IP support but this is a
broken support.

The qlogicfc driver blocks the kernel each time a FC event occured and is
know to failed under heavy load (not so heavy, under load IMHO).

Christophe

On Fri, 29 Jun 2001 12:52:53 Mike Black wrote:
> I have been running successfully with qla2x00src-4.15Beta.tgz for several
> months now over several kernel versions up to 2.4.5.
> When I tested 2.4.6-pre6 I decided to use the qlogicfc driver -- BAD
> MISTAKE!!!
> 
> #1 - My system had crashed (for a different reason) and when the raid5
> was
> resyncing and e2fsck happening at the same time the kernel locked with
> messages from qlogicfc.o:
> qlogicfc0: no handle slots, this should not happen.
> hostdata->queue  is 2a, inptr: 74
> I was able to repeat this several times so it's a consistent error.
> Waiting for the raid resync to finish did allow this complete -- but now
> when I come in the next morning the console is locked up and no network
> access either.  So I reset it.  Checked the logs and here it is again:
> Jun 29 03:39:21 yeti kernel: qlogicfc0 : no handle slots, this should not
> happen.
> Jun 29 03:39:21 yeti kernel: hostdata->queued is 36, in_ptr: 13
> This was during a tape backup.
> 
> So I'm switching back to qla2x00src-4.15Beta.tgz -- which does the resync
> and e2fsck just fine together BTW.
> Jun 29 06:22:47 yeti kernel: qla2x00: detect() found an HBA
> Jun 29 06:22:47 yeti kernel: qla2x00: VID=1077 DID=2100 SSVID=0 SSDID=0
> 
> Only problem is I don't see this package on qlogic's website anymore and
> their "beta" directory is empty now.  I'm waiting to see what their tech
> support says.
> 
> ________________________________________
> Michael D. Black   Principal Engineer
> mblack@csihq.com  321-676-2923,x203
> http://www.csihq.com  Computer Science Innovations
> http://www.csihq.com/~mike  My home page
> FAX 321-676-2355
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-- 
Christophe Barbé
Software Engineer - christophe.barbe@lineo.fr
Lineo France - Lineo High Availability Group
42-46, rue Médéric - 92110 Clichy - France
phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01
http://www.lineo.com

  reply	other threads:[~2001-06-29 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 10:52 Qlogic Fiber Channel Mike Black
2001-06-29 13:19 ` christophe barbé [this message]
2001-06-29 15:09   ` Alan Cox
2001-06-29 15:36     ` christophe barbé
2001-06-29 15:38       ` Alan Cox
2001-06-29 15:48       ` Matthew Jacob
2001-06-29 20:44   ` David S. Miller
2001-06-29 20:51     ` Matthew Jacob
2001-06-29 20:54     ` David S. Miller
2001-06-29 15:17 conway, heather

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=20010629151910.C27847@pc8.lineo.fr \
    --to=christophe.barbe@lineo.fr \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).