linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gshan <gshan@alcatel-lucent.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org,
	Linux IDE mailing list <linux-ide@vger.kernel.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: PIIX4: DMA timeout issue
Date: Thu, 31 Jul 2008 09:00:10 +0800	[thread overview]
Message-ID: <48910E9A.9060103@alcatel-lucent.com> (raw)
In-Reply-To: <200807302143.37693.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 30 July 2008, gshan wrote:
>
> [...]
>  
>   
>> The IRQ routing issue has been fixed. IRQ routing system
>> on my board is somewhat complicated: i8259->mlba (FPGA based
>> PCI device)->MV64460(system controller). I forgot to set MV64460
>> IRQ pin to level sensitive and edge sensitive was used, which caused
>> interrupt lost finally. After changing this to level sensitive, everything
>> seems fine. Now, the problem isn't interrupt lost, but suspending DMA
>> operations.
>>     
>
> Thanks for explaining this.
>
>   
>>> Also is the problem still present in 2.6.26 or 2.6.27-rc1?
>>>
>>> [ I don't see an information about the kernel version that is
>>>   being used in either of threads? ]
>>>   
>>>       
>> Sorry, I'm using 2.6.21 kernel.
>>     
>
> Would be great to try with some recent one, the issue may have been
> fixed already (which is quite likely given a number of bugfixes that
> went in recent kernels).
>   
I tried to searched in bugzilla.kernel.org and didn't find
there has fix on this issue. Yesterday, Jeff suggested me
to turn to ata driver for PIIX4. I tried this yesterday but still
have some problems to make PIIX4 workable under ata
driver. I will continue working on this today.

Gavin

> Thanks,
> Bart
>   


  reply	other threads:[~2008-07-31  1:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <488ED837.2060509@alcatel-lucent.com>
2008-07-29 13:34 ` PIIX4: DMA timeout issue Jeff Garzik
     [not found]   ` <200807291713.29580.bzolnier@gmail.com>
2008-07-30  0:57     ` gshan
2008-07-30 19:43       ` Bartlomiej Zolnierkiewicz
2008-07-31  1:00         ` gshan [this message]
2008-07-30  0:58   ` gshan
2008-07-30  9:04   ` gshan
2008-07-30 10:49     ` Alan Cox
2008-07-31  4:30       ` gshan
2008-08-01  7:43         ` Tejun Heo
2008-08-01  8:38           ` gshan
2008-08-01  8:54           ` gshan
2008-08-03 14:10             ` Gavin Shan
2008-08-05  3:41               ` gshan
2008-10-24  6:09           ` gshan

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=48910E9A.9060103@alcatel-lucent.com \
    --to=gshan@alcatel-lucent.com \
    --cc=bzolnier@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.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;
as well as URLs for NNTP newsgroup(s).