From: "Mat Loikkanen" <Mat.Loikkanen@synopsys.com>
To: linux-ide@vger.kernel.org
Subject: scsi error -> hang
Date: Thu, 27 Jan 2005 10:07:26 -0800 [thread overview]
Message-ID: <007901c5049b$0eedbab0$5015040a@internal.synopsys.com> (raw)
I'm trying to track down why Libata/SCSI is hanging after an error -- in
this case a result from a ATAPI device to a "test unit ready" packet cmd.
The sequence of events are as follows (HSATA is my driver). My ISR gets
called when the error (status=0x51/error=0x64) is received by my host
controller; my ISR ends up calling qc_complete. An error is reported by
the scsi error handler kernel thread. I'm using 2.6.9
ata_scsi_queuecmd
ata_scsi_dump_cdb: CDB (1:0,0,0) 00 00 00 00 00 00 00 00 00
ata_scsi_translate
atapi_xlat
HSATA : <6>hsata_qc_prep: not doing DMA - exiting
ata_qc_issue_prot: ATA_PROT_ATAPI_NODATA
ata_tf_load_mmio: feat 0x0 nsect 0x0 lba 0x0 0x0 0x20
ata_tf_load_mmio: device 0xA0
ata_exec_command_mmio: ata1: cmd 0xA0 <<ATAPI PACKET cmd>>
ata_scsi_translate: EXIT
atapi_packet_task: ENTER
atapi_packet_task: send cdb <<"test unit ready" (0x00)
cmd>>
HSATA : hsata_isr: <3>STATUS ERROR (0x51)
HSATA : hsata_isr: <3>ERROR REG = 0x64
HSATA : <6>hsata_isr: INTERRUPT ISR NODATA irq=21
ata_qc_complete <<called as result of interrupt>>
HSATA : <4>hsata_scsi_error WARNING: uid=1 tid=-1
ata_scsi_error: ENTER <<.eh_strategy_handler>>
HSATA : <4>hsata_eng_timeout WARNING: id=1 magic=13
HSATA : <3>hsata_eng_timeout ERROR: ata1: BUG: timeout without command,
exiting
ata_scsi_error: EXIT
Any ideas to point me in the right direction? I saw another thread on scsi
errors and hanging and decrementing ->host_failed in ata_scsi_error(), which
my version of libata-scsi does.
Thanks!
-mat
Mat Loikkanen
Synopsys, Inc.
reply other threads:[~2005-01-27 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='007901c5049b$0eedbab0$5015040a@internal.synopsys.com' \
--to=mat.loikkanen@synopsys.com \
--cc=linux-ide@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).