All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Gregory Brauer <greg@wildbrain.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete }
Date: Thu, 26 Oct 2006 12:35:29 +0200	[thread overview]
Message-ID: <45408F71.1030909@anagramm.de> (raw)
In-Reply-To: <453FD6B5.9080205@wildbrain.com>

Hello, Gregory!

Gregory Brauer wrote:
> 
> I have a new Promise SATA300 TX4 4-port SATA controller
> to which I have attached two older WD2500JD hard drives
> and two brand new WD2500KS hard drives.  The older drives
> seem to work fine, but both of the brand new hard drives
> trigger the following errors every few seconds during
> i/o:
> 
> Oct 25 13:57:18 gleep kernel: ata3: no sense translation for status: 0x50
> Oct 25 13:57:18 gleep kernel: ata3: translated ATA stat/err 0x50/00 to 
> SCSI SK/ASC/ASCQ 0xb/00/00
> [...]
> 00:0b.0 Mass storage controller: Promise Technology, Inc. PDC20718 (SATA 
> 300 TX4) (rev 02)

Hummm... Well, first, can you try another kernel?
Second, the same chip on a board from a different manufacturer.
I am a hardware engineer working with the Promise PDC20775.
SATA Chips are pretty sensitive to bad board layout, coming up
with strange errors. :-/

Best greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19


  reply	other threads:[~2006-10-26 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 21:27 SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete } Gregory Brauer
2006-10-26 10:35 ` Clemens Koller [this message]
2006-12-19 11:26 ` Roel Teuwen
  -- strict thread matches above, loose matches on Subject: below --
2006-12-19 14:24 Mikael Pettersson
2006-12-19 17:52 ` Gregory Brauer

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=45408F71.1030909@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=greg@wildbrain.com \
    --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 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.