From: Roberto Nibali <ratz@drugphish.ch>
To: Andreas Haumer <andreas@xss.co.at>
Cc: Willy Tarreau <willy@w.ods.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.4.31 + aic79xx] SCSI error: Infinite interrupt loop, INTSTAT = 0
Date: Sat, 26 Nov 2005 17:32:12 +0100 [thread overview]
Message-ID: <43888E0C.8070806@drugphish.ch> (raw)
In-Reply-To: <438882C6.20402@xss.co.at>
Hello,
> Yesterday the new LSI Logic hostadapters arrived. I replaced the
> Adaptec 29320 controllers with the new LSI boards and did various
> tests.
>
> Executive summary: with the LSI controllers everything works fine!
During the past 2 years we have also changed our HW configuration
regarding SCSI from Adaptec to LSI. Always patching the kernel (2.2.x
and 2.4.x) with gibbs' code was too cumbersome and on top of that we
experienced similar interrupts and I/O aborts. Not being too familiar
with indepth SCSI technology we had to go with what proved (seemed) to
work more reliable in the long term, which were LSI based SCSI controllers.
> 01:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08)
> 01:03.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08)
[...]
> Fusion MPT base driver 2.05.16
> Copyright (c) 1999-2004 LSI Logic Corporation
> mptbase: Initiating ioc0 bringup
> ioc0: 53C1030: Capabilities={Initiator}
> mptbase: Initiating ioc1 bringup
> ioc1: 53C1030: Capabilities={Initiator}
> mptbase: 2 MPT adapters found, 2 installed.
> Fusion MPT SCSI Host driver 2.05.16
> scsi2 : ioc0: LSI53C1030, FwRev=01030a00h, Ports=1, MaxQ=222, IRQ=28
> scsi3 : ioc1: LSI53C1030, FwRev=01030a00h, Ports=1, MaxQ=222, IRQ=29
> Vendor: IFT Model: A16U-G2421 Rev: 342A
> Type: Direct-Access ANSI SCSI revision: 03
> blk: queue f7ae9018, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
> Vendor: IFT Model: A16U-G2421 Rev: 342A
> Type: Direct-Access ANSI SCSI revision: 03
> blk: queue f723de18, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
[...]
> I will have this particular hardware setup available for
> testing for about two or three days (until end of next Tuesday).
> If anyone wants me to try any patches for the aic79xx driver in
> this timeframe I'm willing to do so if time permits.
More related to LSI, but would you be willing to try following for me
and report back (in private, since this is getting off-topic), please:
http://www.drugphish.ch/~ratz/mpt-status/mpt-status-1.1.4.tar.bz2
And if it does not compile on your 2.4.x system, use the following patch:
http://www.drugphish.ch/~ratz/mpt-status/mpt-status-1.1.4-fix-compilation-on-2.4.x-1.diff
It should allow you to do basic HW raid monitoring on LSI-53C1030 chipsets.
Thanks and good luck,
Roberto Nibali, ratz
--
echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
prev parent reply other threads:[~2005-11-26 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 21:34 [2.4.31 + aic79xx] SCSI error: Infinite interrupt loop, INTSTAT = 0 Andreas Haumer
2005-11-24 5:39 ` Willy Tarreau
2005-11-24 13:05 ` Andreas Haumer
2005-11-24 23:22 ` Willy Tarreau
2005-11-26 15:44 ` Andreas Haumer
2005-11-26 16:32 ` Roberto Nibali [this message]
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=43888E0C.8070806@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=andreas@xss.co.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@w.ods.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