public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Tonino <ttonino@users.sf.net>
To: Paul Jakma <paulj@alphyra.ie>
Cc: GrandMasterLee <masterlee@digitalroadkill.net>,
	Thomas Tonino <ttonino@users.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with Qlogic 2200 and 2.4.20
Date: Fri, 24 Jan 2003 11:54:42 +0100	[thread overview]
Message-ID: <3E311B72.9060508@users.sf.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301231851080.31406-100000@dunlop.admin.ie.alphyra.com>

Paul Jakma wrote:

>>Just to chime in, are you using the qlogicfc driver that comes with
>>the kernel? If so, Try using qlogic's 6.01 driver set instead and
>>see if your problem goes away. I've had other problems, mostly stack
>>related, but I've since found my fixes
> 
> hmm.. i'd be very interested in them. I have found the qlogic v6 
> driver to dreadfully unstable under heavy load (eg multiple 
> bonnie++'s) on SMP.

I was planning to go use the qlogic 6.x driver, but only after a test.

For me, the in-kernel driver with the patch from Andrew Patterson is very stable 
on SMP. We'll have to see how the 6.x driver works out.

The in-kernel driver without patch is hopeless on single processor too. Uptime 
of 15 minutes or so when doing a resync, a bit more, but not much more than an 
hour, when doing less intensive IO.

In both cases with the "no handle slots, this should not happen" message. Both 
on Broadcom PIII boards - one Dell, one IBM.


Thomas


  parent reply	other threads:[~2003-01-24 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030122094015$6b19@gated-at.bofh.it>
2003-01-22 15:31 ` Problem with Qlogic 2200 and 2.4.20 Thomas Tonino
2003-01-23  7:53   ` GrandMasterLee
2003-01-23 18:52     ` Paul Jakma
2003-01-24  1:45       ` GrandMasterLee
2003-01-25  3:03         ` Paul Jakma
2003-01-24 10:54       ` Thomas Tonino [this message]
2003-01-22  9:36 Przemysław Maciuszko

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=3E311B72.9060508@users.sf.net \
    --to=ttonino@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masterlee@digitalroadkill.net \
    --cc=paulj@alphyra.ie \
    --cc=ttonino@users.sourceforge.net \
    /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