public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Samuel Masham" <samuel.masham@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Cc: "Mauro Tassinari" <mtassinari@cmanet.it>, lkml@societasilluminati.org
Subject: Re: libata/sata errors on ich[?]/maxtor
Date: Wed, 22 Mar 2006 18:59:21 +0900	[thread overview]
Message-ID: <93564eb70603220159wd03a48du@mail.gmail.com> (raw)
In-Reply-To: <93564eb70603170635s4d3c8c3o@mail.gmail.com>

Hi Again All, Alan,

On 17/03/06, Samuel Masham <samuel.masham@gmail.com> wrote:
> Hi Alan,
>
> On 17/03/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Gwe, 2006-03-17 at 13:37 +0900, Samuel Masham wrote:
> > > As you can see from the printk's here this error continues and the for
> > > every access (write?) to the drive you just have to wait for a
> > > timeout.
> >
> > Eventually the drive will be offlined.
>
> really? I can test that easily enough if nothing else :)

When is it (should it) going to offline the drive? its been spitting
out these messages (about set per min?) for 4 hours at the moment with
no change bar the sector number increasing by 2 each time...

> > > ata1: command 0x35 timeout, stat 0xd1 host_stat 0x61
> > > ata1: translated ATA stat/err 0xd1/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> > > ata1: status=0xd1 { Busy }
> > > SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8000002
> > > Current sd08:12: sense key Aborted Command
> > > Additional sense indicates Scsi parity error
> >
> > It thinks there is a communication (eg cable problem), at least that is
> > how it has mapped the error report. Not something I'd expect to see in
> > the SATA case on several machines so it could be some kind of setup
> > error or timing incompatibility in the driver.
>
> Well Its cheep enough to get another cable and test that.

Done. The new short cable showed no difference in behavior.

So left with the timing/setup error... Anyone with any ideas?

> > What is attached to that controller (SATA and PATA items)

as I said before there are two hardisks

> Ata Maxtor 6Y080M0  SCSI  sda 0
> Ata Maxtor 6V250F0   SCSI  sdb 0

(Remember the problem is ONLY with the second drive... and according
to others any in the 6Vxxx series shows this same issue?)

  ...and there is a cdrom drive attached via pata

(I think its on the same controller... the 6300ESB seems to do just
about everything...)

hdparm -I /dev/hda

/dev/hda:

ATAPI CD-ROM, with removable media
        Model Number:       SAMSUNG CD-ROM SN-124
        Serial Number:
        Firmware Revision:  N103
Standards:
        Likely used CD-ROM ATAPI-1
Configuration:
        DRQ response: 50us.
        Packet size: 12 bytes
Capabilities:
        LBA, IORDY(can be disabled)
        DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns

As Ian mentioned maxtor have release a new version of the drive
firmware ... but... The 6V250F0 drive that shows this lockup IS
running the latest drive firmware  which I discovered after a rather
long exchange with Maxtor...

I have had a bit of a look at the sata spec and would just like to
confirm that the drive is configured to disable the NCQ (as the Maxtor
support seemed to stress this point). From what i can see this is done
in the Device Configuration Overlay...

>From the spec

  4.8. Device Configuration Overlay
    4.8.1. Definition

WORD 8: Serial ATA command / feature sets supported
       This word enables configuration of command sets and feature sets.
       Bit 0 indicates whether native command queuing shall be
supported by the device. When
       set to one, the drive shall support native command queuing.
When cleared to zero, drive
       support for native command queuing shall be disabled ....

So anyone got any ideas how to read this?

Or anything else to check / try...

Samuel

  parent reply	other threads:[~2006-03-22  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16 23:02 libata/sata errors on ich[?]/maxtor Mauro Tassinari
2006-03-17  4:37 ` Samuel Masham
2006-03-17  6:01   ` Samuel Masham
2006-03-17  9:55     ` R: " mtassinari
2006-03-17 11:34   ` Alan Cox
2006-03-17 14:35     ` Samuel Masham
2006-03-17 15:10       ` R: " Mauro Tassinari
2006-03-22  9:59       ` Samuel Masham [this message]
2006-03-22 11:27         ` mtassinari
2006-03-25 23:13         ` Ian Young
  -- strict thread matches above, loose matches on Subject: below --
2006-03-18 16:17 Ian Young

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=93564eb70603220159wd03a48du@mail.gmail.com \
    --to=samuel.masham@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@societasilluminati.org \
    --cc=mtassinari@cmanet.it \
    /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