From: Matt Turner <mattst88@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
rth@twiddle.net, ink@jurassic.park.msu.ru, mcree@orcon.net.nz,
jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
dri-devel@lists.freedesktop.org, airlied@gmail.com,
alexdeucher@gmail.com, jglisse@redhat.com
Subject: Re: Problems with alpha/pci + radeon/ttm
Date: Sun, 27 Jun 2010 00:58:07 -0400 [thread overview]
Message-ID: <AANLkTim0JbmNLY1yG5MIWhcjM34h4HHVjS58jEobmPO0@mail.gmail.com> (raw)
In-Reply-To: <20100627130717M.fujita.tomonori@lab.ntt.co.jp>
On Sun, Jun 27, 2010 at 12:20 AM, FUJITA Tomonori
<fujita.tomonori@lab.ntt.co.jp> wrote:
> On Thu, 24 Jun 2010 10:53:52 -0400
> Matt Turner <mattst88@gmail.com> wrote:
>
>> > Seems that the IOMMU can't find 128 pages. It's likely due to:
>> >
>> > - out of the IOMMU space (possibly someone doesn't free the IOMMU
>> > space).
>> >
>> > or
>> >
>> > - the mapping parameters (such as align) aren't appropriate so the
>> > IOMMU can't find space.
>> >
>> >
>> >> Is this the cause of the bug we're seeing in the report [1]?
>> >>
>> >> Anyone know what's going wrong here?
>> >
>> >
>> > I've attached a patch to print the debug info about the mapping
>> > parameters.
>> >
>> >
>> > diff --git a/arch/alpha/kernel/pci_iommu.c b/arch/alpha/kernel/pci_iommu.c
>> > index d1dbd9a..17cf0d8 100644
>> > --- a/arch/alpha/kernel/pci_iommu.c
>> > +++ b/arch/alpha/kernel/pci_iommu.c
>> > @@ -187,6 +187,10 @@ iommu_arena_alloc(struct device *dev, struct pci_iommu_arena *arena, long n,
>> > /* Search for N empty ptes */
>> > ptes = arena->ptes;
>> > mask = max(align, arena->align_entry) - 1;
>> > +
>> > + printk("%s: %p, %p, %d, %ld, %lx, %u\n", __func__, dev, arena, arena->size,
>> > + n, mask, align);
>> > +
>> > p = iommu_arena_find_pages(dev, arena, n, mask);
>> > if (p < 0) {
>> > spin_unlock_irqrestore(&arena->lock, flags);
>>
>> Using this patch, I log the attached output.
>
> Your system has 1GB iommu address space. I guess that it's enough for
> KSM?
I would definitely think so. The video card I'm using here is a 64MB
Radeon 9100 PCI, with a 128MB BAR.
> The parameters in the log looks good. But you got this log before you
> started X?
Yes, that's right.
I'll see if I can isolate where the first -ENOMEM is coming from.
Thanks Fujita for helping with this!
Matt
next prev parent reply other threads:[~2010-06-27 4:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 21:19 Problems with alpha/pci + radeon/ttm Matt Turner
2010-06-22 5:59 ` FUJITA Tomonori
2010-06-22 8:32 ` Dave Airlie
2010-06-24 9:51 ` Michael Cree
2010-06-24 15:02 ` Matt Turner
2010-06-27 4:20 ` FUJITA Tomonori
2010-06-27 10:46 ` Michael Cree
2010-06-27 23:14 ` Dave Airlie
2010-06-28 9:03 ` Michael Cree
2010-06-28 16:08 ` Richard Henderson
2010-06-24 14:53 ` Matt Turner
2010-06-27 4:20 ` FUJITA Tomonori
2010-06-27 4:58 ` Matt Turner [this message]
2010-06-30 18:43 ` Konrad Rzeszutek Wilk
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=AANLkTim0JbmNLY1yG5MIWhcjM34h4HHVjS58jEobmPO0@mail.gmail.com \
--to=mattst88@gmail.com \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=ink@jurassic.park.msu.ru \
--cc=jbarnes@virtuousgeek.org \
--cc=jglisse@redhat.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=rth@twiddle.net \
/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).