From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Lord <liml@rtr.ca>
Cc: htejun@gmail.com, michal.k.k.piotrowski@gmail.com,
bryan@arbores.ca, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Stardom SATA HSM violation
Date: Wed, 5 Sep 2007 12:38:51 -0700 [thread overview]
Message-ID: <20070905123851.a89b24b6.akpm@linux-foundation.org> (raw)
In-Reply-To: <46DEE617.4050004@rtr.ca>
> On Wed, 05 Sep 2007 13:23:35 -0400 Mark Lord <liml@rtr.ca> wrote:
> Andrew Morton wrote:
> >> please try 2.6.22.5. Even if it doesn't fix the problem, it would
> >> report error conditions better.
> >
> > Presumably in the week and a half between Bryan's report and your request,
> > Bryan has gone off and got an adaptec card. Bryan, it would be helpful if
> > you could rebuild the original systam and help us get to the bottom of this
> > bug, thanks.
>
> I reported a very similar bug back a few releases ago.
> Anyone who wants to try it themselves, can do this with hdparm-7.7 (from sourceforge):
>
> hdparm --drq-hsm-error /dev/sda
>
> Whether or not it hangs the machine does depend upon exactly which SATA LLD is used,
> and what model/revision of drive is installed. But if it hangs for you (eg. Tejun),
> then you now have a way to reproduce a HSM error "on demand" for testing. :)
>
Hey, we just found something which doesn't crash my Vaio!
sony:/home/akpm/hdparm-7.7> 0 ./hdparm --drq-hsm-error /dev/sda
/dev/sda:
triggering "stuck DRQ" host state machine error
do_drq_hsm_error: Success
ata status=0x58 ata error=0x00
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata3.00: cmd ec/00:00:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 0
res 58/00:01:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
ata3: soft resetting port
ata3.00: configured for UDMA/100
ata3: EH complete
sd 2:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
How dull. (ata_piix)
next prev parent reply other threads:[~2007-09-05 19:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46CFA08E.6090604@arbores.ca>
2007-08-26 23:10 ` Stardom SATA HSM violation Michal Piotrowski
2007-09-03 8:53 ` Tejun Heo
2007-09-05 16:53 ` Andrew Morton
2007-09-05 17:23 ` Mark Lord
2007-09-05 19:38 ` Andrew Morton [this message]
2007-09-05 23:03 ` Mark Lord
2007-09-07 0:58 ` Tejun Heo
2007-09-07 13:40 ` Mark Lord
2007-09-27 7:05 ` Tejun Heo
2007-09-27 18:37 ` Alan Cox
2007-09-27 23:32 ` Tejun Heo
2007-09-27 23:42 ` Jeff Garzik
2007-09-27 23:52 ` Tejun Heo
2007-09-28 3:56 ` [PATCH] libata drain fifo on stuck DRQ " Mark Lord
2007-09-28 9:48 ` Tejun Heo
2007-09-28 9:56 ` Andrew Morton
2007-09-28 10:01 ` Tejun Heo
2007-09-28 10:27 ` Alan Cox
2007-09-28 13:41 ` [PATCH] libata drain fifo on stuck DRQ HSM violation (try#2) Mark Lord
2007-09-29 6:24 ` Jeff Garzik
2007-09-29 1:05 ` [PATCH] libata drain fifo on stuck DRQ HSM violation Jeff Garzik
2007-09-29 6:28 ` Alan Cox
2007-09-29 12:34 ` Mark Lord
2007-09-28 3:52 ` Stardom SATA " Mark Lord
2007-09-06 15:00 ` Bryan Woods
2007-09-07 0:58 ` 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=20070905123851.a89b24b6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bryan@arbores.ca \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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).