From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Prakash, Sathya" <Sathya.Prakash@lsi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Moore, Eric" <Eric.Moore@lsi.com>,
linux-scsi@vger.kernel.org
Subject: Re: Strange mptbase / mptscsih kernel messages
Date: Thu, 5 Jun 2008 15:58:00 +0200 [thread overview]
Message-ID: <e2e108260806050658r3fb8b3b2gaf486c2647271e69@mail.gmail.com> (raw)
In-Reply-To: <5AE055B67BB5764693E2900C7E3699BE0110FAEB@pamail.ad.lsil.com>
On Thu, May 8, 2008 at 10:33 AM, Prakash, Sathya <Sathya.Prakash@lsi.com> wrote:
> The meaning of 1 message is some fram transmit error encountered by
> hardware and the I/O request is aborted by firmware because of the
> error,
> The second message indicates, some I/O got timed out and the SML tries
> to abort the request and the firmware completes the I/O before aborting
> that. Hence returns IO executed message and the driver completes the
> abort as success.
> Suspecting some bad hardware in the topology(cables?)
Hello Sathya,
It took some time before I could have a closer look at the system on
which I observed the strange kernel messages. Apparently the RAID
controller (LSISAS3081E ?) is not connected directly to the 16 disks
but via a SAS expander (Super Micro SC836 SAS Backplane with two LSI
SASX28 Expander Chips --
http://www.supermicro.com/products/chassis/3U/836/SC836E2-R800.cfm).
It will be a challenge to find out which component triggered the
kernel messages and how to make the storage subsystem work perfectly.
Any hint is welcome.
Bart.
next prev parent reply other threads:[~2008-06-05 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 8:33 Strange mptbase / mptscsih kernel messages Prakash, Sathya
2008-06-05 13:58 ` Bart Van Assche [this message]
[not found] <e2e108260805072336p6b29f11o287ac3c5cab9295a@mail.gmail.com>
2008-05-08 8:27 ` Andrew Morton
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=e2e108260806050658r3fb8b3b2gaf486c2647271e69@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).