From: Keith Whitwell <keith@tungstengraphics.com>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: Keith Packard <keithp@keithp.com>,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)
Date: Fri, 20 Oct 2006 19:09:10 +0100 [thread overview]
Message-ID: <453910C6.4000102@tungstengraphics.com> (raw)
In-Reply-To: <20061020180354.GB29810@tau.solarneutrino.net>
Ryan Richter wrote:
> On Fri, Oct 20, 2006 at 06:51:01PM +0100, Keith Whitwell wrote:
>> Ryan Richter wrote:
>>> On Fri, Oct 20, 2006 at 12:43:44PM +0100, Keith Whitwell wrote:
>>>> Ryan Richter wrote:
>>>>> On Wed, Oct 18, 2006 at 07:54:41AM +0100, Keith Whitwell wrote:
>>>> All of your other wierd problems, like the assert failures, etc, make me
>>>> wonder if there just hasn't been some sort of build problem that can
>>>> only be resolved by clearing it out and restarting.
>>>>
>>>> It wouldn't hurt to just nuke your current Mesa and libdrm builds and
>>>> start from scratch - you'll probably have to do that to get debug
>>>> symbols for gdb anyway.
>>> I had heard something previously about i965_dri.so maybe getting
>>> miscompiled, but I hadn't followed up on it until now. I rebuilt it
>>> with an older gcc, and now it's all working great! Sorry for the wild
>>> goose chase.
>> Out of interest, can you try again with the original GCC and see if the
>> problem comes back? Which versions of GCC are you using?
>
> The two gcc versions are the 4.1 (miscompiles) and 3.4 (OK) from Debian
> unstable. I had originally compiled it myself with gcc-4.1 because the
> Debian libgl1-mesa-dri package didn't build i965_dri.so until I
> submitted a build patch to them to have it built. They released a new
> package a few days ago with i965_dri.so included, presumably built with
> the same gcc-4.1, the default cc on Debian unstable.
>
> I had exactly the same problems with my own version and theirs. I
> rebuilt it again today with CC=gcc-3.4 and now everything works great.
> I saved a copy of the old i965_dri.so, so I can verify in the next few
> days that replacing it breaks things again. Let me know if you want
> copies of these files to examine.
Sure, email me the 4.1 version offline. I'll also see about installing
4.1 here.
Keith
next prev parent reply other threads:[~2006-10-20 18:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 19:45 Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2) Ryan Richter
2006-10-14 8:55 ` Keith Whitwell
2006-10-14 9:49 ` Arjan van de Ven
2006-10-14 9:58 ` Keith Whitwell
2006-10-14 10:55 ` Avi Kivity
2006-10-14 18:15 ` Keith Packard
2006-10-17 17:40 ` Ryan Richter
2006-10-17 22:27 ` Keith Packard
2006-10-17 23:56 ` Ryan Richter
2006-10-18 6:54 ` Keith Whitwell
2006-10-18 7:01 ` Dave Airlie
2006-10-19 17:31 ` Ryan Richter
2006-10-20 11:43 ` Keith Whitwell
2006-10-20 16:40 ` Ryan Richter
2006-10-20 17:51 ` Keith Whitwell
2006-10-20 18:03 ` Ryan Richter
2006-10-20 18:09 ` Keith Whitwell [this message]
2006-10-24 12:21 ` Avi Kivity
2006-10-24 14:07 ` Ryan Richter
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=453910C6.4000102@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@tau.solarneutrino.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