linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Darcy <kernel-lists@projecthugo.co.uk>
To: PFC <lists@peufeu.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [git patch] 2.6.x libata fix
Date: Fri, 13 Jan 2006 09:26:03 +0000	[thread overview]
Message-ID: <43C7722B.2060408@projecthugo.co.uk> (raw)
In-Reply-To: <op.s29h2nbncigqcu@apollo13>

PFC wrote:

>
>     Hello,
>
>     I've had a lot of problems with nv_sata (nforce3) and Maxtor 
> harddrives.  Basically it always boils down to :
>
> Dec 24 23:04:34 apollo13 ata3: command 0x35 timeout, stat 0xd0 
> host_stat  0x21
> Dec 24 23:04:34 apollo13 ata3: translated ATA stat/err 0x35/00 to 
> SCSI  SK/ASC/ASCQ 0x4/00/00
> Dec 24 23:04:34 apollo13 ata3: status=0x35 { DeviceFault SeekComplete  
> CorrectedError Error }
> Dec 24 23:04:34 apollo13 sd 2:0:0:0: SCSI error: return code = 0x8000002
> Dec 24 23:04:34 apollo13 sdc: Current: sense key=0x4
> Dec 24 23:04:34 apollo13 ASC=0x0 ASCQ=0x0
> Dec 24 23:04:34 apollo13 end_request: I/O error, dev sdc, sector 
> 490223295
> Dec 24 23:04:34 apollo13 raid5: Disk failure on sdc1, disabling 
> device.  Operation continuing on 3 devices
>
>     Plugging the Maxtor drives on the not-nv SATA sockets solved it 
> (thanks  god I have 2 maxtor and 2 seagate drives)...
>
>

Thanks for the message,

I'm not using nv_sata, I'm using sata_mv,

just to clarify.

Could we please try to keep this thread on topic.

Regards,

Matt




  reply	other threads:[~2006-01-13  9:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 17:11 [git patch] 2.6.x libata fix Jeff Garzik
2006-01-11 10:18 ` Matt Darcy
2006-01-12 10:01   ` Matt Darcy
2006-01-12 10:57     ` PFC
2006-01-13  9:26       ` Matt Darcy [this message]
2006-01-12 11:46     ` Matt Darcy
2006-01-13 11:26       ` [git patch] 2.6.x libata fix more information (sata_mv problems continued) Matt Darcy
2006-01-13 11:42         ` Jens Axboe
2006-01-13 17:14         ` Sebastian Kuzminsky
2006-01-13 19:51           ` Matt Darcy
2006-01-13 21:06             ` [git patch] 2.6.x libata fix more information DEBUG INFO !!! Matt Darcy
  -- strict thread matches above, loose matches on Subject: below --
2005-12-04  1:57 [git patch] 2.6.x libata fix Jeff Garzik
2005-08-30  4:49 Jeff Garzik
2005-07-29  6:31 Jeff Garzik
2005-06-27 12:21 Jeff Garzik
2005-05-26 16:56 Jeff Garzik

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=43C7722B.2060408@projecthugo.co.uk \
    --to=kernel-lists@projecthugo.co.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@peufeu.com \
    /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).