From: Tejun Heo <htejun@gmail.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: translated ATA stat/err 0x51/0c to ... PDC20376 (FastTrak 376) related cold freezes
Date: Sun, 27 Aug 2006 18:37:04 +0900 [thread overview]
Message-ID: <44F167C0.6020903@gmail.com> (raw)
In-Reply-To: <1156440866.29118.14.camel@localhost>
Soeren Sonnenburg wrote:
> Dear all,
>
> I just upgraded to using 2 sata disks (both seagate drives
> ST3400832AS and ST3750640AS) on this asus a7v8x on-board promise fastrak
> 376 (PDC20376) controller. However, as soon as I do a lot of io (cp some
> G of files) I get swamped in
>
> ata1: translated ATA stat/err 0x51/0c to SCSI SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x0c { DriveStatusError }
> ata2: translated ATA stat/err 0x51/0c to SCSI SK/ASC/ASCQ 0xb/00/00
> ata2: status=0x51 { DriveReady SeekComplete Error }
> ata2: error=0x0c { DriveStatusError }
> ...
Is the system usable after these messages?
> messages. For that it is enough to do it on a single drive or copy from
> drive to drive. This is on kernel 2.6.17.4, but I remember (when I was
> still using a single drive) this very same output to happen on 2.6.15.
>
> Can anyone translate these dubious error messages to me ?
>
> Here are more details about the system:
>
> - the sata_promise driver version 1.04 is used
Can you give a shot at 2.6.18-rc4?
--
tejun
next prev parent reply other threads:[~2006-08-27 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 17:34 translated ATA stat/err 0x51/0c to ... PDC20376 (FastTrak 376) related cold freezes Soeren Sonnenburg
2006-08-27 9:37 ` Tejun Heo [this message]
2006-08-27 15:33 ` Soeren Sonnenburg
2006-08-27 16:18 ` Tejun Heo
2006-08-27 16:24 ` 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=44F167C0.6020903@gmail.com \
--to=htejun@gmail.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@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