public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Smith <asmith@tranquility.fsbusiness.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Corruption problems in pata_via for Via NanoBook owners (Cloudbook, EasyNote XS etc.)
Date: Sun, 17 Feb 2008 15:40:36 +0000	[thread overview]
Message-ID: <20080217154036.185bb11a@core> (raw)
In-Reply-To: <5BDDEEF9-D2AC-4112-83EB-43D02E8C4E6C@tranquility.fsbusiness.co.uk>

> In 2.24 the device ID 0x581 for Vendor VIA was added to the pata_via  
> driver causing some problems.

Actually we've had the CX700 supported for a while and as Tejun has
fixed other bugs related to it we know its being used and tested. The
slave port is a bit quirky but that is purely in the way it seems to mess
up the snooping of mode changes. Yours is the first bug report of this
type so more information about the precise combination of devices used
and the actual logs would be useful.

> It builds fine and seems to start up OK, however, on large IOs then  
> the kernel starts to throw errors about MULTICMDs (I think that was  
> the term) returning an invalid response.

No thats not a term I can guess at - do you have any logs with the exact
error reports in them ?

Also unfortunately you've compared 2.6.23 with 2.6.24 which means a bug
anywhere else could be causing the behaviour you see. It would be very
interesting to know if 2.6.24 built with old IDE rather than pata_via
(which is just config options) shows a difference in behaviour on your
box.

Alan

  reply	other threads:[~2008-02-17 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 14:21 PROBLEM: Corruption problems in pata_via for Via NanoBook owners (Cloudbook, EasyNote XS etc.) Andrew Smith
2008-02-17 15:40 ` Alan Cox [this message]
2008-02-17 16:59 ` Bartlomiej Zolnierkiewicz

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=20080217154036.185bb11a@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=asmith@tranquility.fsbusiness.co.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