From: Tejun Heo <htejun@gmail.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA HSM error
Date: Wed, 01 Nov 2006 11:56:27 +0900 [thread overview]
Message-ID: <45480CDB.3050407@gmail.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B0189DFF9@ismail.innsys.innovsys.com>
Hello,
Rune Torgersen wrote:
> I get the followin gerros once in a while on 2.6.18, running on a
> Freescale 8260 PPC.
> The controller is Silicon Image SiI3124 , and the drive a seagate
> NL35.2 drive
>
> Any idea if this is hardware or software?
>
> ata2: illegal qc_active transition (00000002->000001f8)
The driver says that the attached device is setting spurious command
active bits. I have never seen this before.
> ata2.00: exception Emask 0x2 SAct 0x2 SErr 0x0 action 0x2 frozen
> ata2.00: tag 1 cmd 0x61 Emask 0x2 stat 0x50 err 0x0 (HSM violation)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: qc timeout (cmd 0xec)
> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
> ata2.00: revalidation failed (errno=-5)
> ata2: failed to recover some devices, retrying in 5 secs
> ata2: hard resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/100
> ata2: EH complete
> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
SRST doesn't really recover the device but hardreset does.
As it's the first report of this kind, I'm more inclined to hw problem.
Can you test with different drive?
Thanks.
--
tejun
next prev parent reply other threads:[~2006-11-01 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 22:53 SATA HSM error Rune Torgersen
2006-11-01 2:56 ` Tejun Heo [this message]
2006-11-01 14:22 ` Rune Torgersen
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=45480CDB.3050407@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=runet@innovsys.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).