public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mike Black" <mblack@csi-inc.com>
To: "Austin Gonyou" <austin@digitalroadkill.net>,
	"Chaoyang Deng" <cdeng@io.iol.unh.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG
Date: Fri, 28 Jun 2002 10:00:58 -0400	[thread overview]
Message-ID: <02f501c21eac$3a701f70$f6de11cc@black> (raw)
In-Reply-To: 1025243932.2956.3.camel@UberGeek

FYI...6.0.27 is only for QLA2200 and QLA23XX.  I'm using 4.0.27beta for the QLA2100

It's hard to find on their website though (took a quick look just now and couldn't find it again).

----- Original Message ----- 
From: "Austin Gonyou" <austin@digitalroadkill.net>
To: "Chaoyang Deng" <cdeng@io.iol.unh.edu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, June 28, 2002 1:58 AM
Subject: Re: kernel BUG


> My recommendation for this is to *not* use the in-kernel qla2xxx driver.
> Not that it's necessarily bad mind you, but much new hardware doesn't
> seem to like it. I've locked up a box several times using it. Instead, I
> recommend that you go to qlogic's site and get 6.0.27 and try it. It's
> much faster than the previous drivers, and has been very stable and
> compile's with no warnings ever, at least in my scenario. 
> 
> I recently had an issue with a QL2xxx driver, some storage, and LUNs. My
> issue turned out to be a blacklist issue, but, I got a lot of info from
> the Qlogic folks as well, regarding which driver should be used today.
> 
> Hope this helps. 
> 
> On Thu, 2002-06-27 at 14:23, Chaoyang Deng wrote:
> > Hi,
> > 
> > I am working on an iSCSI target driver with a Fibre Channel disk. After I
> > updated my OS to linux7.3 with kernel 2.4.18-3, I got problem: my driver
> > will crash my box. I am not sure if it is a bug in my code or in the
> > Qlogic Fibre Channel driver or in the kernel. Could anyone give me a hint?
> 
> -- 
> Austin Gonyou <austin@digitalroadkill.net>
> -
> 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/


  reply	other threads:[~2002-06-28 13:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 19:23 kernel BUG Chaoyang Deng
2002-06-28  5:58 ` Austin Gonyou
2002-06-28 14:00   ` Mike Black [this message]
     [not found] <200907311139.55095.christoph.thielecke@gmx.de>
2009-07-31 16:01 ` kernel bug Linus Torvalds
2009-07-31 16:26   ` Eric Paris
  -- strict thread matches above, loose matches on Subject: below --
2008-09-10 20:35 Todor Gyumyushev
2008-09-11  3:21 ` Aaron Straus
2008-04-13 16:06 monte
2008-04-13 18:20 ` Jesper Juhl
2008-04-13 18:33 ` Alan Cox
2008-03-29  9:05 Olver Eduardo Ramos
2008-03-30  1:06 ` Rafael J. Wysocki
2007-09-19 21:43 Kernel bug Branislav Bozgai
2007-09-24 15:33 ` Mel Gorman
2007-08-19 18:33 kernel bug Costas Sismanis
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2005-11-26  1:23 Kernel bug Vympel
2005-11-27 12:51 ` Hugh Dickins
2005-11-03 18:10 Kernel BUG Mark Fortescue
2005-11-03 18:59 ` Trond Myklebust
2005-11-03 23:15   ` Mark Fortescue
2005-11-04 10:08   ` Mark Fortescue
2003-03-26 23:57 Perez-Gonzalez, Inaky
2003-03-27 14:23 ` Hugh Dickins
2003-03-26 13:13 kasper_k_jensen
2003-01-25 22:56 Kernel bug Massimiliano C. - Uf0On|in3
2003-01-19 18:01 Christophe Dupre
2003-01-07  9:17 kernel BUG Sönke Ruempler
2002-12-07 10:09 Kernel BUG Henrik Steffen
2002-12-08  1:47 ` Alan Cox
2002-11-27 11:31 kernel bug sanket rathi
2002-11-27 10:45 sanket rathi
2002-11-27  9:50 sanket rathi
2002-11-27 10:10 ` Arjan van de Ven
2002-06-28 19:54 kernel BUG Eric Weiss
2002-06-28 19:26 ew
2002-05-21 14:01 kernel bug Chen Hao
2001-11-25 18:03 Kernel Bug gonzalo.ab
2001-11-25 23:59 ` Adam Schrotenboer
2001-03-06 19:55 kernel bug ernte23

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='02f501c21eac$3a701f70$f6de11cc@black' \
    --to=mblack@csi-inc.com \
    --cc=austin@digitalroadkill.net \
    --cc=cdeng@io.iol.unh.edu \
    --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