All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Mark Lord <liml@rtr.ca>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	jgarzik@pobox.com
Subject: Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
Date: Tue, 20 Jun 2006 23:20:38 +0100	[thread overview]
Message-ID: <449874B6.7020606@dgreaves.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606201146430.2601@p34.internal.lan>

Justin Piszcz wrote:
> Dave, what is the make/model of the drives you get errors with by the
> way?
>
> On Tue, 20 Jun 2006, David Greaves wrote:
>> [Some email archaeology later]
>>
>> Back in March I was running 2.6.16 (with the opcode patch) and I sent an
>> email with the following info:
>>
>> dmesg:
>> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
>> SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
Model Family: Maxtor DiamondMax 10 family
Device Model: Maxtor 6B200M0
Serial Number: B4038RRH
Firmware Version: BANC1980

this is sata_sil

Another machine has :
Device Model: SAMSUNG SP2504C
Serial Number: S09QJ10Y720963
Firmware Version: VT100-33
User Capacity: 250,059,350,016 bytes

running through sata_via

that's running 2.6.16.18 and just gives:
ata1: PIO error
ata1: status=0x50 { DriveReady SeekComplete }


David

-- 


  reply	other threads:[~2006-06-20 22:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 12:17 LibPATA/ATA Errors Continue - Will there be a fix for this? Justin Piszcz
2006-06-20 13:01 ` Mark Lord
2006-06-20 13:03   ` Justin Piszcz
2006-06-20 14:23   ` David Greaves
2006-06-20 15:45     ` David Greaves
2006-06-20 15:46       ` Justin Piszcz
2006-06-20 22:20         ` David Greaves [this message]
2006-06-20 22:22           ` Justin Piszcz
2006-06-21 11:39           ` Justin Piszcz
  -- strict thread matches above, loose matches on Subject: below --
2006-06-20 15:15 Al Boldi
2006-06-20 15:48 ` Justin Piszcz
2006-06-20 16:25 ` Mark Lord

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=449874B6.7020606@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=jgarzik@pobox.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --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.