linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-fsdevel@vger.kernel.org
Subject: WRITE DMA EXT failures with JM20330 based sata2ide
Date: Mon, 06 Jun 2011 18:16:05 +0200	[thread overview]
Message-ID: <isiunc$807$1@dough.gmane.org> (raw)

Hello,

I've converted a 1,5TB SATA drive to IDE to run it on a UDMA100 IDE controller.

Low traffic applications work well. I'm able to create a xfs or ext4 filesystem 
and even a fsck runs without problems and without causing error messages on dmesg.

If I start to copy a file with some gigabytes in size to the new disc, then 
errors like the following keep coming on dmesg:

ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: failed command: WRITE DMA EXT
ata2.00: cmd 35/00:00:30:07:8a/00:04:57:00:00/e0 tag 0 dma 524288 out
          res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2: link is slow to respond, please be patient (ready=0)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting link
ata2.00: configured for UDMA/25
ata2.00: device reported invalid CHS sector 0
ata2: EH complete

The error repeats many times.

Copying a big file from this disc to another location on the disc, then this 
also works without errors (maybe because of the slow down of the mixed 
read/write access). This copy from disc to same disc also failed before I 
switched the disc to SATA I mode. This is done now, but doesn't seem to fix copy 
from another disc to the new one.

Interesting thing is that always WRITE DMA EXT seems to fail. Is there any way 
to fix this? Maybe it would be a option to increase the timeout, that gets 
triggered here, so the driver waits longer for the result?

What I definetly need is some workaround to stop the kernel from speeding down 
until UDMA/25 is reached. This speed is totally unacceptable for such a big 
drive... :-(

Are there configuration parameters that change how the driver behaves in such 
situations and how to set them to get around this problem?

Thank you very much in advance for any help...

Yours

Manuel


                 reply	other threads:[~2011-06-06 16:25 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='isiunc$807$1@dough.gmane.org' \
    --to=manuel.spam@nurfuerspam.de \
    --cc=linux-fsdevel@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).