lkml.org 
[lkml]   [2006]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: libata/sata errors on ich[?]/maxtor
    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 :)

    > > 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. But as the
    failure is repeatable in nearly (but not quite) down to the block for
    a given build then i don't have so much hope.

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

    It being the weekend here i don't now have access to the box... but
    from the rhn page (linked in the bugzilla entry if anyone can follow
    that) it says

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

    I thought they had a ide (normal ata) cddrive on board as well but
    cant see that on the hardware info page...

    I will check on Monday and report back.

    Since posting this i have tried one more thing

    I had a look at the data sheet for the sata control er and it said
    that it supported the SATA 1 (150) mode and the drive supports SATA 2
    (300) i think (names maybe confused here).

    So I tried moving the jumper on the drive to the 150 mode position but
    this made no difference.

    Could the drive have some functions (NCQ?) enabled by default that the
    controller cant handle? (and we dont turn off when we initialise the
    drive as we have no support yet?)... ok that's reaching...

    Any ideas of what I can check or tryout would be great!

    Thanks

    Samuel

    ps Mauro, yep I am quite convinced we are seeing the same thing
    here... I will let you know how it turns out for us
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-03-17 15:38    [W:3.275 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site