From: Tejun Heo <htejun@gmail.com>
To: sam song <sam_song@usish.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Issuing a vendor specific ATA cmd on SATA Disk via ATA Pass Thru
Date: Tue, 04 Dec 2007 09:46:32 +0900 [thread overview]
Message-ID: <4754A368.70806@gmail.com> (raw)
In-Reply-To: <006301c83596$2e58fed0$6539a8c0@usish.com.cn>
sam song wrote:
> [USI]: ata pass through(16) cdb: 85 0b 06 00 41 00 00 00 00 00 00 00 00 e0
> fd 00
> [<unknown opcode>: 85 0b 06 00 41 00 00 00 00 00 00 00 00 e0 fd 00 ]
> scsi_status=0x2, host_status=0x0, driver_status=0x8
> info=0x1 duration=8184280 milliseconds
[--snip--]
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd fd/41:00:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 33280 out
> res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: port is slow to respond, please be patient (Status 0xd0)
> ata2: device not ready (errno=-16), forcing hardreset
> ata2: soft resetting port
> ata2.00: configured for UDMA/133
> ata2: EH complete
> sd 2:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 2:0:0:0: [sdb] Write Protect is off
> sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Hmmm... It's timeout. How long does the command take? It's a bit weird
because 36000s but the reported command duration is 136s. How long did
the command take actually?
--
tejun
next prev parent reply other threads:[~2007-12-04 0:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 10:34 Issuing a vendor specific ATA cmd on SATA Disk via ATA Pass Thru sam song
2007-11-30 1:18 ` Tejun Heo
2007-11-30 3:33 ` sam song
2007-11-30 6:12 ` Tejun Heo
2007-11-30 6:29 ` sam song
2007-11-30 6:33 ` Tejun Heo
2007-11-30 6:42 ` sam song
2007-11-30 6:47 ` Tejun Heo
2007-11-30 7:01 ` sam song
2007-11-30 8:22 ` Tejun Heo
2007-12-03 10:20 ` sam song
2007-12-04 0:46 ` Tejun Heo [this message]
2007-12-04 1:32 ` sam song
2007-12-04 2:21 ` Tejun Heo
2007-12-05 1:43 ` Tejun Heo
2007-12-05 2:39 ` sam song
2007-12-05 3:16 ` Tejun Heo
2008-03-11 3:17 ` sam song
2008-03-11 3:21 ` Tejun Heo
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=4754A368.70806@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sam_song@usish.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;
as well as URLs for NNTP newsgroup(s).