[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090428184431Z.fujita.tomonori@lab.ntt.co.jp>
Date: Tue, 28 Apr 2009 18:43:49 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: optimusgd@...il.com
Cc: fujita.tomonori@....ntt.co.jp, rjw@...k.pl,
linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
grundler@...gle.com
Subject: Re: [Bug #13001] PCI-DMA: Out of IOMMU space
On Tue, 28 Apr 2009 14:18:57 +0500
**UNKNOWN CHARSET** <optimusgd@...il.com> wrote:
> No, it is regression. I can reproduce that without allowdac and any
> other unnecessary boot options.
Hmm, in the bug repport, you said that you can't reproduce the problem:
http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15
I can't find your comment like, "I can reproduce that without
allowdac".
> In later discussion Grant Grundler ask
> me apply patch that show 32 bit dma devices in my system. Results I
> attached to bugreport. Looks like only one 32 bit dma device in my
> system is ata controller, sata-nv.
Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
said that pata_amd and sata_nv use 32bit dma mask.
> I can stable reproduce IOMMU out of space when I write data to sata
> drive.
Ok, let's figure out what's wrong.
First, can you test v2.6.30-rc3 with the following patch?
http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff
Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
don't use any kernel option).
When the kernel is out of IOMMU space, it prints some useful
information.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists