All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Andrew Hall <andrew.a.hall@gmail.com>
Cc: 'Alan Cox' <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, 'Jeff Garzik' <jeff@garzik.org>
Subject: Re: CF flash IDE failure to attach with 2.6.20+
Date: Thu, 21 Jun 2007 12:02:27 +0900	[thread overview]
Message-ID: <4679EA43.4040002@gmail.com> (raw)
In-Reply-To: <4679cefc.06d7720a.0280.ffff9cce@mx.google.com>

Andrew Hall wrote:
>> I suppose you were using ata_piix too in older kernel, right?  Can you
>> post the boot dmesg of 2.6.19?  We used to ignore mwdma mode before and
>> enabled it at some point after that.  That may be the cause here.
>>
>> Also, please try the attached patch on top of 2.6.20.
> 
> Sorry guys, I've actually got it wrong. The hardware that I have been
> testing on has a different chipset: Intel ICH8, to what I was using
> previously with success with 2.6.19 (this was ICH4 based hardware) - so the
> driver is actually different now. 
> 
> Tejun, your patch for 2.6.20 failed with the same errors.
> 
> For completeness I have tested the newer ICH8 hardware with everything from
> 2.6.15 through to 2.6.21.5 using the ata_piix drivers and it (the Compact
> Flash) fails in all kernels. Here is the (relevant) dmesg from 2.6.21.5
> showing the CF being disabled:

Does piix driver work?  If so, can you post boot dmesg and the result of
'hdparm -I /dev/hdX'?

-- 
tejun

  reply	other threads:[~2007-06-21  3:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 10:02 CF flash IDE failure to attach with 2.6.20+ Andrew_hall
2007-06-18 11:26 ` Tejun Heo
2007-06-18 11:57   ` Alan Cox
2007-06-18 23:01     ` Andrew Hall
2007-06-19  5:00       ` Tejun Heo
2007-06-21  1:05         ` Andrew Hall
2007-06-21  3:02           ` Tejun Heo [this message]
2007-06-21  7:19             ` Andrew Hall
2007-06-21 14:45               ` Mark Lord
2007-06-21 15:09                 ` Andrew Hall
2007-06-26  8:51                 ` CF flash PATA on libata failure to attach Andrew Hall
2007-06-26 18:50                   ` Mark Lord
2007-06-27  3:57                     ` Andrew Hall
2007-06-27 14:08                       ` Mark Lord
2007-06-27 23:49                         ` Andrew Hall
2007-06-28 17:37                           ` Mark Lord
2007-06-29  0:35                             ` Andrew Hall
2007-06-29  1:10                               ` Mark Lord
2007-06-29  1:36                                 ` Tejun Heo
2007-06-29  2:26                                   ` Mark Lord
2007-06-29  2:15                                 ` Andrew Hall
2007-06-29  2:28                                   ` Mark Lord
2007-06-29  3:24                                     ` Andrew Hall
2007-06-29  7:34                                     ` Andrew Hall
2007-06-29 10:17                                       ` Alan Cox
2007-07-02 10:58                                         ` Tejun Heo
2007-07-03  6:13                                         ` Albert Lee
2007-06-29 10:06                                 ` Alan Cox
2007-06-25  9:05             ` CF flash IDE failure to attach with 2.6.20+ Andrew Hall
2007-06-18 23:23   ` Andrew Hall

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=4679EA43.4040002@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.a.hall@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.