All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Espen M. Rutger" <espen@rutger.no>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide.c and compactFlash
Date: Thu, 30 Aug 2007 12:47:47 +0200	[thread overview]
Message-ID: <46D6A053.3020600@rutger.no> (raw)
In-Reply-To: <20070829132653.GA11130@csclub.uwaterloo.ca>

Lennart Sorensen wrote:
> On Thu, Aug 23, 2007 at 01:56:35PM +0200, Espen M. Rutger wrote:
>   
>> I got problems with the IDE code which causes the kernel to freez after 
>> printing out:
>>
>> hda: status timeout: status=0xd0 { Busy }
>>
>> kernel used: 2.4.18 crosscompiled with Montavista tools (ppc_82xx-gcc 
>> (GCC) 3.2.1 20020930 (MontaVista))
>>
>> The ide interface chip is a PD6729 configured to ATA mode.
>>
>> CompactFlash cards: winsys 1GB industrial grade and simpleTech 1GB 
>> industrial grade.
>>
>> I beleive this is a timing issue and have tried to increase a udelay () 
>> to 2 microseconds (instead of 1 microsecond) in the ide_wait_stat() 
>> function - it took longer time to freez, but it still freezes...
>>     
>
> Try booting with 'ide=nodma'.  Some compact flash cards support DMA
> mode, and of course most IDE controllers support DMA mode, and if both
> support it the kernel tends to try and enable it but if you don't have
> the DMA lines connected it will fail and give annoying errors similar to
> that one.  The DMA part of compact flash was a fairly recent addition
> and the two affected lines used to be reserved on compact flash.  The
> product I work on did not have the DMA lines on the previous board
> design but we have it on the latest board revision.  On the old boards
> we had to disable DMA support for IDE since otherwise certain types of
> compact flash would have annoying timeouts trying to enable DMA.  On our
> new board with the DMA lines, everything just works and the DMA access
> gives about twice the read/write speed to the compact flash cards we are
> using.
>
> --
> Len Sorensen
>
>   

Thank you very much for your response Lennart, but unfortunately this 
did not solve my problem - the system (got four machines in my test 
setup) still generate the error and make the kernel wait forever.

regards
Espen M. Rutger


      reply	other threads:[~2007-08-30 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 11:56 ide.c and compactFlash Espen M. Rutger
2007-08-29 13:26 ` Lennart Sorensen
2007-08-30 10:47   ` Espen M. Rutger [this message]

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=46D6A053.3020600@rutger.no \
    --to=espen@rutger.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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.