From: David Woodhouse <dwmw2@infradead.org>
To: "schnitzelkuchen@googlemail.com" <schnitzelkuchen@googlemail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>
Subject: Re: [regression] [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Date: Tue, 17 Nov 2009 23:26:41 +0000 [thread overview]
Message-ID: <1258500401.6132.88.camel@macbook.infradead.org> (raw)
In-Reply-To: <200911151048.13777.schnitzelkuchen@googlemail.com>
On Sun, 2009-11-15 at 01:48 -0800, Michael wrote:
>
> After bisecting i got to the following commit:
>
> 176616814d700f19914d8509d9f65dec51a6ebf7 is the first bad commit
> commit 176616814d700f19914d8509d9f65dec51a6ebf7
> Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
> Date: Mon Jul 27 12:59:57 2009 +0100
>
> intel_agp: Use PCI DMA API correctly on chipsets new enough to
> have IOMMU
There are later commits which fixed some handling of addresses >4GiB --
it's not _entirely_ unexpected that that particular point in time didn't
work. It'll be using swiotlb instead of just addressing the page
directly.
Can you apply the patch in commit 135cbc4e (just the second part; the
addition) and check whether it still fails?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
prev parent reply other threads:[~2009-11-17 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 9:48 Michael
2009-11-15 9:55 ` David Woodhouse
2009-11-15 10:17 ` Michael
[not found] ` <1258280722.1496.185.camel@macbook.infradead.org>
2009-11-15 10:41 ` Michael
2009-11-17 23:26 ` David Woodhouse [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=1258500401.6132.88.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schnitzelkuchen@googlemail.com \
--cc=zhenyu.z.wang@intel.com \
/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
all inboxes | Powered by JetHome®