All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: QLA2200 driver
@ 2002-04-25 13:40 berthiaume_wayne
  2002-04-25 13:56 ` Jes Sorensen
  0 siblings, 1 reply; 12+ messages in thread
From: berthiaume_wayne @ 2002-04-25 13:40 UTC (permalink / raw)
  To: ttonino; +Cc: linux-scsi

	The qla2x00 driver is not in the Linus tree; however, if you pull
down a Red Hat tree you'll find it is in there. QLogic maintains the driver
and, perhaps, just hasn't gotten around to submitting it to Marcello, Linus,
et al for inclusion in the LSB. Duane ol' buddy are you listening????  =;^)

-----Original Message-----
From: Thomas Tonino [mailto:ttonino@corp.home.nl]
Sent: Thursday, April 25, 2002 7:35 AM
To: linux-scsi@vger.kernel.org
Subject: QLA2200 driver


We're setting up a server with a 14 Seagate Cheetah fibre JBOD attached 
to a single QLA2200 controller.

The Qlogic fibre driver in 2.4.18 crashes very quickly in this setup, 
with the message "qlogicfc0 : no handle slots, this should not happen". 
This crash happens after writing less than 100GB of data to the JBODs.

I've seen that message before with an older drive and kernel (around 
2.4.5?) version. At the time, I observed the same problem while  syncing 
a software raid5.

I found Feral's GPL'd driver (available at ftp://ftp.feral.com/pub/isp/) 
to work correctly so far (~ 1 TB).

Is there a reason why Feral's driver is not in the kernel? Having a 
driver that is so non-functional is really bad, IMO.

Who is using the in-kernel driver without problems? Could a connection 
be made between the problem and, say, the number of drives, or the 
achieved throughput?


Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: QLA2200 driver
@ 2002-04-26 13:09 berthiaume_wayne
  0 siblings, 0 replies; 12+ messages in thread
From: berthiaume_wayne @ 2002-04-26 13:09 UTC (permalink / raw)
  To: arun.mittal; +Cc: linux-scsi, ttonino

	Arun, the problem is the qla2x00 driver never makes it out to the
Linux base so the community at large is not always aware of it or the need
to go to your website to obtain the correct driver for the QLA2200 and
QLA2300. BTW: It's nice to see you are out there and listening. =;^)

-----Original Message-----
From: Arun Mittal [mailto:arun.mittal@qlogic.com]
Sent: Thursday, April 25, 2002 2:15 PM
To: berthiaume_wayne@emc.com; ttonino@corp.home.nl
Cc: linux-scsi@vger.kernel.org
Subject: RE: QLA2200 driver


The 6.0beta20 driver
(http://www.qlogic.com/support/home_resources.asp?id=57) maintained by
QLogic (QLA2200 and QLA23xx) includes the changes made by Arjan in RH3
version + other robustness changes. Please download and use this driver.

Arun

-----Original Message-----
From: berthiaume_wayne@emc.com [mailto:berthiaume_wayne@emc.com]
Sent: Thursday, April 25, 2002 6:41 AM
To: ttonino@corp.home.nl
Cc: linux-scsi@vger.kernel.org
Subject: RE: QLA2200 driver


	The qla2x00 driver is not in the Linus tree; however, if you pull
down a Red Hat tree you'll find it is in there. QLogic maintains the driver
and, perhaps, just hasn't gotten around to submitting it to Marcello, Linus,
et al for inclusion in the LSB. Duane ol' buddy are you listening????  =;^)

-----Original Message-----
From: Thomas Tonino [mailto:ttonino@corp.home.nl]
Sent: Thursday, April 25, 2002 7:35 AM
To: linux-scsi@vger.kernel.org
Subject: QLA2200 driver


We're setting up a server with a 14 Seagate Cheetah fibre JBOD attached 
to a single QLA2200 controller.

The Qlogic fibre driver in 2.4.18 crashes very quickly in this setup, 
with the message "qlogicfc0 : no handle slots, this should not happen". 
This crash happens after writing less than 100GB of data to the JBODs.

I've seen that message before with an older drive and kernel (around 
2.4.5?) version. At the time, I observed the same problem while  syncing 
a software raid5.

I found Feral's GPL'd driver (available at ftp://ftp.feral.com/pub/isp/) 
to work correctly so far (~ 1 TB).

Is there a reason why Feral's driver is not in the kernel? Having a 
driver that is so non-functional is really bad, IMO.

Who is using the in-kernel driver without problems? Could a connection 
be made between the problem and, say, the number of drives, or the 
achieved throughput?


Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: QLA2200 driver
@ 2002-04-25 18:14 Arun Mittal
  0 siblings, 0 replies; 12+ messages in thread
From: Arun Mittal @ 2002-04-25 18:14 UTC (permalink / raw)
  To: berthiaume_wayne, ttonino; +Cc: linux-scsi

The 6.0beta20 driver (http://www.qlogic.com/support/home_resources.asp?id=57) maintained by QLogic (QLA2200 and QLA23xx) includes the changes made by Arjan in RH3 version + other robustness changes. Please download and use this driver.

Arun

-----Original Message-----
From: berthiaume_wayne@emc.com [mailto:berthiaume_wayne@emc.com]
Sent: Thursday, April 25, 2002 6:41 AM
To: ttonino@corp.home.nl
Cc: linux-scsi@vger.kernel.org
Subject: RE: QLA2200 driver


	The qla2x00 driver is not in the Linus tree; however, if you pull
down a Red Hat tree you'll find it is in there. QLogic maintains the driver
and, perhaps, just hasn't gotten around to submitting it to Marcello, Linus,
et al for inclusion in the LSB. Duane ol' buddy are you listening????  =;^)

-----Original Message-----
From: Thomas Tonino [mailto:ttonino@corp.home.nl]
Sent: Thursday, April 25, 2002 7:35 AM
To: linux-scsi@vger.kernel.org
Subject: QLA2200 driver


We're setting up a server with a 14 Seagate Cheetah fibre JBOD attached 
to a single QLA2200 controller.

The Qlogic fibre driver in 2.4.18 crashes very quickly in this setup, 
with the message "qlogicfc0 : no handle slots, this should not happen". 
This crash happens after writing less than 100GB of data to the JBODs.

I've seen that message before with an older drive and kernel (around 
2.4.5?) version. At the time, I observed the same problem while  syncing 
a software raid5.

I found Feral's GPL'd driver (available at ftp://ftp.feral.com/pub/isp/) 
to work correctly so far (~ 1 TB).

Is there a reason why Feral's driver is not in the kernel? Having a 
driver that is so non-functional is really bad, IMO.

Who is using the in-kernel driver without problems? Could a connection 
be made between the problem and, say, the number of drives, or the 
achieved throughput?


Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: QLA2200 driver
@ 2002-04-25 16:28 berthiaume_wayne
  0 siblings, 0 replies; 12+ messages in thread
From: berthiaume_wayne @ 2002-04-25 16:28 UTC (permalink / raw)
  To: jes; +Cc: ttonino, linux-scsi

	No. I'll admit it is quite a hack but it does work.

-----Original Message-----
From: Jes Sorensen [mailto:jes@wildopensource.com]
Sent: Thursday, April 25, 2002 11:53 AM
To: berthiaume_wayne@emc.com
Cc: ttonino@corp.home.nl; linux-scsi@vger.kernel.org
Subject: Re: QLA2200 driver


>>>>> ">" == berthiaume wayne <berthiaume_wayne@emc.com> writes:

>> 	Actually, we have been using the latest off the QLogic site
>> and referencing EMC customers to that driver as the one of
>> choice. They are referred to the EMC approved driver link. The
>> Rawhide is way out of date, thus one of the reasons to use what is
>> on the Qlogic site. The only modification we've had to make is to
>> the qlavendor.c to contain the definitions for EMC's unique SCSI
>> command set.

Sorry, but thats really scary to hear, unless of course you have a
special version thats totally rewamped compared to the one that Red
Hat has been shipping.

Please note that I am referring to Arjan's work on qla2200.c not
qla2x00.c!

Jes

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: QLA2200 driver
@ 2002-04-25 15:48 berthiaume_wayne
  2002-04-25 15:53 ` Jes Sorensen
  0 siblings, 1 reply; 12+ messages in thread
From: berthiaume_wayne @ 2002-04-25 15:48 UTC (permalink / raw)
  To: jes; +Cc: ttonino, linux-scsi

	Actually, we have been using the latest off the QLogic site and
referencing EMC customers to that driver as the one of choice. They are
referred to the EMC approved driver link. The Rawhide is way out of date,
thus one of the reasons to use what is on the Qlogic site. The only
modification we've had to make is to the qlavendor.c to contain the
definitions for EMC's unique SCSI command set.

-----Original Message-----
From: Jes Sorensen [mailto:jes@wildopensource.com]
Sent: Thursday, April 25, 2002 9:56 AM
To: berthiaume_wayne@emc.com
Cc: ttonino@corp.home.nl; linux-scsi@vger.kernel.org
Subject: Re: QLA2200 driver


>>>>> ">" == berthiaume wayne <berthiaume_wayne@emc.com> writes:

>> 	The qla2x00 driver is not in the Linus tree; however, if you
>> pull down a Red Hat tree you'll find it is in there. QLogic
>> maintains the driver and, perhaps, just hasn't gotten around to
>> submitting it to Marcello, Linus, et al for inclusion in the
>> LSB. Duane ol' buddy are you listening????  =;^)

Or maybe the driver you're referring to is such a mess that it would
never be included in the official kernel.

Arjan is trying to clean it up (similarly to what I did to the qla1280
driver) but it's still got some way to go. If you want to play with
it, your best bet is to pull Arjan's qla2200 driver out of the Red Hat
Rawhide .src.rpm.

Jes

^ permalink raw reply	[flat|nested] 12+ messages in thread
* QLA2200 driver
@ 2002-04-25 11:34 Thomas Tonino
  2002-04-25 16:03 ` Matthew Jacob
                   ` (3 more replies)
  0 siblings, 4 replies; 12+ messages in thread
From: Thomas Tonino @ 2002-04-25 11:34 UTC (permalink / raw)
  To: linux-scsi

We're setting up a server with a 14 Seagate Cheetah fibre JBOD attached 
to a single QLA2200 controller.

The Qlogic fibre driver in 2.4.18 crashes very quickly in this setup, 
with the message "qlogicfc0 : no handle slots, this should not happen". 
This crash happens after writing less than 100GB of data to the JBODs.

I've seen that message before with an older drive and kernel (around 
2.4.5?) version. At the time, I observed the same problem while  syncing 
a software raid5.

I found Feral's GPL'd driver (available at ftp://ftp.feral.com/pub/isp/) 
to work correctly so far (~ 1 TB).

Is there a reason why Feral's driver is not in the kernel? Having a 
driver that is so non-functional is really bad, IMO.

Who is using the in-kernel driver without problems? Could a connection 
be made between the problem and, say, the number of drives, or the 
achieved throughput?


Thomas

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2002-06-13 11:53 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-25 13:40 QLA2200 driver berthiaume_wayne
2002-04-25 13:56 ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2002-04-26 13:09 berthiaume_wayne
2002-04-25 18:14 Arun Mittal
2002-04-25 16:28 berthiaume_wayne
2002-04-25 15:48 berthiaume_wayne
2002-04-25 15:53 ` Jes Sorensen
2002-04-25 11:34 Thomas Tonino
2002-04-25 16:03 ` Matthew Jacob
2002-04-25 16:30 ` Mike Anderson
2002-04-25 18:27 ` Andrew Patterson
     [not found] ` <1019754409.2413.2.camel@lvadp.fc.hp.com>
2002-06-13 11:53   ` Thomas Tonino

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.