public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bolke de Bruin <bdbruin@aub.nl>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.5 - Compaq Fibre Channel 64-bit/66Mhz HBA
Date: Thu, 11 Aug 2005 17:46:38 +0200	[thread overview]
Message-ID: <42FB72DE.8000703@aub.nl> (raw)

Hello,

The company I work for is investigating a switch from Windows 2000 to a 
Linux based setup for its databases. Because of a dependancy on a third 
party we need to settle on kernel 2.6.5. Although the database servers 
will be moved to x86_64, we would like stay using our raid array 
(StorageWorks 4100) as it has been quite a tremendous investment for the 
size of our company and it still works.

However it is unclear if the current controller "Compaq Fibre Channel 
64-bit/66Mhz HBA" is actually supported. This controller has been marked 
broken from kernel 2.6.7 and onwards with a "This is too much stack" 
(drivers/scsi/cpqfcTScontrol.c). Any additional documentation I cannot find.

So the basic question is. Does this controller work on kernel 2.6.5?

and if not and someone wants to give some advice, is it possible to 
replace the controller without having to move to a different raid array 
setup or is a fix pretty easy to create?

Kind regards and thanks in advance,

B. de Bruin




             reply	other threads:[~2005-08-11 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 15:46 Bolke de Bruin [this message]
2005-08-11 15:51 ` Kernel 2.6.5 - Compaq Fibre Channel 64-bit/66Mhz HBA Arjan van de Ven
2005-08-11 16:19 ` Rolf Eike Beer
2005-08-11 16:41   ` Bolke de Bruin
2005-08-11 16:58     ` Rolf Eike Beer
2005-08-11 17:58 ` Kernel 2.6.5 - Compaq Fibre Channel 64-bit/66Mhz HBA [PATCH] Rolf Eike Beer
     [not found] ` <200508160955.49133@bilbo.math.uni-mannheim.de>
     [not found]   ` <4301A6BB.3020403@aub.nl>
2005-08-16  8:58     ` Rolf Eike Beer

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=42FB72DE.8000703@aub.nl \
    --to=bdbruin@aub.nl \
    --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