From: "conway, heather" <conway_heather@emc.com>
To: "'Mike Black'" <mblack@csihq.com>,
"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: RE: Qlogic Fiber Channel
Date: Fri, 29 Jun 2001 11:17:17 -0400 [thread overview]
Message-ID: <2CE33F05597DD411AAE800D0B769587C01D59A40@sryoung.lss.emc.com> (raw)
Hi Mike,
Looks like QLogic up-rev'd the driver versions on their website. They have
the source code for both v4.25 and v4.27 posted now and rpm's for v4.25.
Hope that helps.
Heather
> -----Original Message-----
> From: Mike Black [mailto:mblack@csihq.com]
> Sent: Friday, June 29, 2001 6:53 AM
> To: linux-kernel@vger.kernel.or
> Subject: Qlogic Fiber Channel
>
>
> 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/
>
next reply other threads:[~2001-06-29 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 15:17 conway, heather [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-29 10:52 Qlogic Fiber Channel Mike Black
2001-06-29 13:19 ` christophe barbé
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
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=2CE33F05597DD411AAE800D0B769587C01D59A40@sryoung.lss.emc.com \
--to=conway_heather@emc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.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;
as well as URLs for NNTP newsgroup(s).