From: Andreas Haumer <andreas@xss.co.at>
To: "Moore, Eric Dean" <emoore@lsil.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
mpt_linux_developer@lsil.com
Subject: Re: [PATCH] 2.4.23-pre8 driver udpate for MPT Fusion (2.05.10)
Date: Fri, 24 Oct 2003 20:09:43 +0200 [thread overview]
Message-ID: <3F996AE7.5020409@xss.co.at> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57035A944F@exa-atlanta.se.lsil.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Moore, Eric Dean wrote:
> Here's a patch for 2.4.23-pre8 kernel for MPT Fusion driver, coming from LSI
> Logic.
>
[...]
>
> (8) In a mixed device configuration (Ultra 320 and Non-Ultra
> 320 devices are present on an HBA channel), code was fixed to prevent
> negotiating for QAS on all Ultra 320 devices on that channel.
> This keeps the Ultra 320 devices from dominating the SCSI bus,
> preventing Non-Ultra 320 IO's from executing.
>
[...]
Uh Oh...
Is this a fix for the problems I reported back in June
to LKML and to Pam Delaney?
On June, 12th, I sent a mail to Pam reporting system freezes
I had on an ASUS AP 1700-S5 server with onboard 53C1030
controller. In this mail I speculated about the possibility
of a mixed device configuration beeing the source of the problem:
[...]
Another idea: is it possible that the SCSI controller
has problems with U160 and U320 SCSI disks mixed together
on the same bus? As far as I know there shouldn't be a
problem with this combination, but who knows?
I always tested with a mix of the following SCSI disks:
IBM DDYS-T18350M (18GB U160 SCA)
IBM IC35L036UCDY10-0 (36GB U320 SCA)
I'm currently running 2.4.20 with 4 U320 disks and no
U160 disk in the how swap cage. The system is now up for
about 6 hours and no SCSI timeout occured so far (this
doesn't say anything. Sometimes it takes 24 hours before
a SCSI timeout or even a freeze occurs)
[...]
I haven't got an answer to this report, but with a
all-U320 configuration I never had system freezes since.
Does the new driver now work in a U160/U320 mixed
configuration, too?
- - andreas
- --
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/mWrjxJmyeGcXPhERAowMAJ9mTHr/qLObJ/OvUodLsrILx/MnkACfTj+U
7QVE6mUMmxAEYmIfvHeDItU=
=DcTz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-10-24 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 14:53 [PATCH] 2.4.23-pre8 driver udpate for MPT Fusion (2.05.10) Moore, Eric Dean
2003-10-24 14:59 ` Matthew Wilcox
2003-10-24 15:20 ` James Bottomley
2003-10-24 18:09 ` Andreas Haumer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-24 15:12 Moore, Eric Dean
2003-10-25 19:18 ` Greg KH
2003-10-25 20:44 ` Matthew Wilcox
2003-10-25 21:05 ` Greg KH
2003-10-27 7:11 ` Christoph Hellwig
2003-10-24 16:22 Moore, Eric Dean
2003-10-24 18:46 Moore, Eric Dean
2003-10-24 22:42 Moore, Eric Dean
2003-10-25 20:22 ` Greg KH
2003-10-27 15:04 Moore, Eric Dean
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=3F996AE7.5020409@xss.co.at \
--to=andreas@xss.co.at \
--cc=emoore@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mpt_linux_developer@lsil.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