public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: sander@humilis.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-mm1 libata pata_via
Date: Tue, 8 Nov 2005 15:21:40 +0100	[thread overview]
Message-ID: <20051108142140.GA2790@favonius> (raw)
In-Reply-To: <1131455213.25192.26.camel@localhost.localdomain>

Alan Cox wrote (ao):
> On Maw, 2005-11-08 at 13:13 +0100, Sander wrote:
> > The two pata disks are master and slave. I might try them on separate
> > channels later (especially if you want me to :-)
> 
> Would be interesting. It shouldn't change the behaviour but more info
> is good.

I'll do.

> > [42949377.130000]  sdf:<3>ata5: command error, drv_stat 0x51 host_stat 0x64
> > [42949377.210000] ata5: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
> > [42949377.210000] ata5: status=0x51 { DriveReady SeekComplete Error }
> 
> Thats the important bit. It looks as if I got the timing clock loading
> wrong for this chip. (My EPIA works nicely but all the info I need is in
> your report).

Good to know.

I see your new patch against 2.6.14-mm1 has updates for pata_via.c. It
does not address this issue I presume?

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  reply	other threads:[~2005-11-08 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 17:32 2.6.14-mm1 libata pata_via Chris Boot
2005-11-08  3:15 ` Alan Cox
2005-11-08  8:42   ` Chris Boot
2005-11-09 12:53     ` Chris Boot
2005-11-08 12:13 ` Sander
2005-11-08 13:06   ` Alan Cox
2005-11-08 14:21     ` Sander [this message]
2005-11-08 16:41       ` Alan Cox
2005-11-08 16:34     ` Alan Cox
2005-11-16 14:03       ` Sander
2005-11-16 14:48     ` Sander
2005-11-18 19:07       ` Alan Cox

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=20051108142140.GA2790@favonius \
    --to=sander@humilis.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox