From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73781] [r600g] SIGFPE at ../../../../../src/gallium/drivers/r600/r600_state.c:3109
Date: Mon, 05 May 2014 20:44:52 +0000 [thread overview]
Message-ID: <bug-73781-502-LvsAHoTr8k@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73781-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73781
--- Comment #10 from Florent Rougon <f.rougon@free.fr> ---
(In reply to comment #9)
> Is this still an issue with current Git master? There have been a few
> changes to the DMA code.
Hello,
Many thanks for your reply. As you suggested, I've tried with Mesa from Git
master, dated May 1st (10.2-branchpoint-2-g829cb04). FlightGear 3.0.0 has been
running for a significant amount of time (I'd say 6 to 8 hours), with quality 5
for several hours and I haven't seen any bug from the graphic stack (well,
there are weird rainbow-like textures in a few places, but I've been seeing
them for several months already and haven't been able to investigate yet; it's
probably unrelated to the bug being discussed here).
I'd like to say that the performance is also much better than with the graphic
stack available in Debian wheezy. Yay!
Part of the actual testing in FlightGear is done by my nephews on weekends,
therefore I can report with a longer testing period in 1 to 3 weeks
approximately if you wish.
I have two little questions:
- is there a performance impact if mesa has been compiled with
--enable-debug?
- when it is rebuilt, is it necessary to restart X.org in order to have
everything using the new libraries (I have used the method outlined at
http://pkg-xorg.alioth.debian.org/howto/build-mesa.html to test the new mesa
without messing with the system installation---in short: LD_LIBRARY_PATH,
LIBGL_DRIVERS_PATH and EGL_DRIVERS_PATH)?
Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2558 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-05 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 2:07 [Bug 73781] New: [r600g] SIGFPE at at ../../../../../src/gallium/drivers/r600/r600_state.c:3109 bugzilla-daemon
2014-01-19 2:11 ` [Bug 73781] [r600g] SIGFPE " bugzilla-daemon
2014-01-19 20:03 ` bugzilla-daemon
2014-01-23 6:25 ` bugzilla-daemon
2014-01-23 7:50 ` bugzilla-daemon
2014-01-23 8:22 ` bugzilla-daemon
2014-01-23 8:23 ` bugzilla-daemon
2014-02-17 14:08 ` bugzilla-daemon
2014-02-17 15:28 ` bugzilla-daemon
2014-03-01 14:03 ` bugzilla-daemon
2014-04-28 11:49 ` bugzilla-daemon
2014-05-02 3:43 ` bugzilla-daemon
2014-05-05 20:44 ` bugzilla-daemon [this message]
2014-05-05 21:51 ` bugzilla-daemon
2014-05-06 14:30 ` bugzilla-daemon
2019-09-18 19:13 ` bugzilla-daemon
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=bug-73781-502-LvsAHoTr8k@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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