From: peter <pbog@us.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"Wu, Gilbert" <Gilbert_Wu@adaptec.com>,
Alexis Bruemmer <alexisb@us.ibm.com>,
tom_white@adaptec.com
Subject: Re: Bug in aic94xx driver in 2.6.25-rc3
Date: Wed, 27 Feb 2008 14:39:06 -0800 [thread overview]
Message-ID: <1204151946.7281.23.camel@gnattop> (raw)
In-Reply-To: <1203992592.26232.79.camel@alexis>
My original post was user error and not acutally a bug. I didn't
realize that there was another patch I need to apply to rc3 to get the
latest scsi drivers and error handler code. Alexis clued me in. Now
the error handler appears to be working properly. I included a sample
at the bottom of this email.
I am still seeing the disk go offline if I run i/o performance tests on
sas disks connected to the aic94xx (sequencer version 32). It doesn't
happen right away. The i/o tests will run for several hours before it
fails. Eventually you see the filesystem abort and then be remounted as
read only.
Peter Bogdanovic
IBM
sas: command 0xffff810142569200, task 0xffff81022ad27980, timed out:
EH_NOT_HANDLED^M
sas: Enter sas_scsi_recover_host^M
sas: trying to find task 0xffff81022ad27980^M
sas: sas_scsi_find_task: aborting task 0xffff81022ad27980^M
aic94xx: tmf tasklet complete^M
aic94xx: tmf resp tasklet^M
aic94xx: tmf came back^M
aic94xx: task not done, clearing nexus^M
aic94xx: asd_clear_nexus_tag: PRE^M
aic94xx: asd_clear_nexus_tag: POST^M
aic94xx: asd_clear_nexus_tag: clear nexus posted, waiting...^M
aic94xx: task 0xffff81022ad27980 done with opcode 0x23 resp 0x0 stat
0x8d but aborted by upper layer!^M
aic94xx: asd_clear_nexus_tasklet_complete: here^M
aic94xx: asd_clear_nexus_tasklet_complete: opcode: 0x0^M
aic94xx: came back from clear nexus^M
aic94xx: task 0xffff81022ad27980 aborted, res: 0x0^M
sas: sas_scsi_find_task: task 0xffff81022ad27980 is done^M
sas: sas_eh_handle_sas_errors: task 0xffff81022ad27980 is done^M
sd 0:0:3:0: [sdd] Result: hostbyte=DID_ABORT
driverbyte=DRIVER_OK,SUGGEST_OK^M
end_request: I/O error, dev sdd, sector 27106623^M
sas: --- Exit sas_scsi_recover_host^M
next parent reply other threads:[~2008-02-27 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1203987834.6909.17.camel@gnattop>
[not found] ` <1203992592.26232.79.camel@alexis>
2008-02-27 22:39 ` peter [this message]
2008-02-27 23:37 ` Bug in aic94xx driver in 2.6.25-rc3 James Bottomley
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=1204151946.7281.23.camel@gnattop \
--to=pbog@us.ibm.com \
--cc=Gilbert_Wu@adaptec.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alexisb@us.ibm.com \
--cc=djwong@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tom_white@adaptec.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