https://bugs.freedesktop.org/show_bug.cgi?id=48305
Bug #: 48305 Summary: llpp gets segfault in r600g_dri.so Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: myxolmyxmyx@yopmail.com
Loading any pdf with llpp produces segfault. Message in dmesg: [115638.669260] llpp[15916] general protection ip:b64f6d84 sp:bfe416dc error:0 in r600g_dri.so[b62d3000+a72000]
mupdf that is used by llpp works flawlessly on r600g. And llpp works on fglrx. I'm using Radeon 2600 PRO AGPx4.
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #2 from myxol myxolmyxmyx@yopmail.com 2012-04-04 13:40:19 UTC --- Created attachment 59491 --> https://bugs.freedesktop.org/attachment.cgi?id=59491 gdb output and xorg.log
gdb didn't produce any good backtrace. Could it be because llpp written in ocaml?
https://bugs.freedesktop.org/show_bug.cgi?id=48305
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Drivers/DRI/R600 |Drivers/Gallium/r600
--- Comment #1 from Alex Deucher agd5f@yahoo.com 2012-04-04 11:06:35 PDT --- Can you get a proper backtrace with gdb? Can you also include your xorg log and dmesg output?
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #3 from myxol myxolmyxmyx@yopmail.com 2012-04-04 13:42:36 PDT --- Created attachment 59492 --> https://bugs.freedesktop.org/attachment.cgi?id=59492 dmesg output
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #4 from Alex Deucher agd5f@yahoo.com 2012-04-04 13:45:21 PDT --- Make sure you install the debugging symbols for the 3D driver/mesa. Most distros package these separately. Then when you hit the crash type "bt" in gdb to get the backtrace.
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #6 from Michel Dänzer michel@daenzer.net 2012-04-05 06:48:04 UTC --- (In reply to comment #5)
After playing with compilation flags to get meaningful backtrace I found that this segfault happens only with -O3… Dunno if this is considered as a bug.
It's a bug *somewhere*, but it looks like it could be in the compiler... Maybe you can try isolating which specific option implied by -O3 but not by -O2 makes the difference.
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #5 from myxol myxolmyxmyx@yopmail.com 2012-04-05 05:54:49 PDT --- Created attachment 59519 --> https://bugs.freedesktop.org/attachment.cgi?id=59519 mesa backtrace
After playing with compilation flags to get meaningful backtrace I found that this segfault happens only with -O3… Dunno if this is considered as a bug. Anyway, bt full attached. Mesa compiled with "-march=native -O3 -ggdb -pipe".
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #7 from myxol myxol@lavabit.com 2012-04-05 17:49:05 PDT ---
Maybe you can try isolating which specific option implied by -O3 but not by -O2 makes the difference.
I tried. It is -ftree-vectorize
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #8 from Michel Dänzer michel@daenzer.net 2012-04-06 04:11:52 PDT --- Smells more like a compiler bug then. Which version of gcc is this? Does it also happen with an older one?
https://bugs.freedesktop.org/show_bug.cgi?id=48305
--- Comment #9 from myxol myxol@lavabit.com 2012-04-07 07:28:42 PDT --- I tried 3 gcc versions. Flags: -march=native -O2 -ftree-vectorize -ggdb -pipe 4.4.7 - build fails 4.5.3 - original bugreport 4.6.2 - same problem as with 4.5.3
https://bugs.freedesktop.org/show_bug.cgi?id=48305
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #10 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/407.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org