All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>
Subject: Re: hdparm-9.17 released, with experimental trim/wiper scripts for SSDs
Date: Wed, 29 Jul 2009 19:39:49 -0400	[thread overview]
Message-ID: <4A70DDC5.3000607@rtr.ca> (raw)
In-Reply-To: <4A70DCB8.9000909@rtr.ca>

Mark Lord wrote:
> hdparm-9.17 is now available from sourceforge.net.
> 
> New in this release:
>        - added wiper/ subdirectory with preliminary SSD-wiper (TRIM) 
..

Tejun:  on a related note, my Sil-3132 PCIe SATA controller doesn't
seem to like DSM/TRIM commands passing through it.

[ 3479.010001] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3479.010008] ata4.00: irq_stat 0x00020002, protocol mismatch
[ 3479.010019] ata4.00: cmd 06/01:01:00:00:00/00:00:00:00:00/e0 tag 0 dma 512 out
[ 3479.010021]          res dc/33:00:00:00:00/00:00:00:00:dc/00 Emask 0x2 (HSM violation)
[ 3479.010025] ata4.00: status: { Busy }
[ 3479.010029] ata4.00: error: { IDNF }
[ 3479.010041] ata4: hard resetting link
[ 3481.193102] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[ 3481.197043] ata4.00: configured for UDMA/100
[ 3481.197082] ata4: EH complete

I haven't taken time to dig further yet, but perhaps somebody here
might know if they've hardcoded all of the ATA opcodes in silicon or
something, and now get confused by DSM/TRIM ?

I'll dig further into that later this summer.

  reply	other threads:[~2009-07-29 23:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 23:35 hdparm-9.17 released, with experimental trim/wiper scripts for SSDs Mark Lord
2009-07-29 23:39 ` Mark Lord [this message]
2009-07-30  7:20   ` Robert Hancock
2009-07-30  8:24     ` Jeff Garzik
2009-07-30 12:54     ` Mark Lord
2009-07-30 18:27       ` Robert Hancock
2009-07-30 18:43         ` Mark Lord
2009-07-30 19:15           ` Mark Lord
2009-07-30 19:30         ` Mark Lord
2009-07-30 19:57           ` Robert Hancock

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=4A70DDC5.3000607@rtr.ca \
    --to=liml@rtr.ca \
    --cc=htejun@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.