similar to: [Bug 59242] New: some mesa demos start to segfault after "nouveau: improve buffer transfers" on nv43

Hello there, tl;dr: Is it a known behaviour that using llvm-3.4 and llvm-3.6 at the same time in the same process (while llvm-3.6 is used from a linked shared library and llvm-3.4 is dlopen'ed - with a strange detail: Especially if -rdynamic is used when linking the program). If so, is there a workaround? If not, can it be fixed in llvm-3.6? Long story: I am writing a program that creates

I have been compiling my own wine RPMs using the fedora extras .spec file for a while now. Normally after very little editing of the .spec, the wine RPMs build and I am running the latest & greatest wine. Now I am having problems building *any* wine rpms ( including some of the 0.9.3x versions) on my yum updated Fedora core 6 box. Even when I extract a fresh copy of wine-0.9.42.tar.bz2

Hi, I use two nv34 cards and I would like to test / try out / use the Gallium driver without drawbacks. Unfortunately this has not been working since I decided to install / compile nouveau drivers. My system is Debian Squeeze, my kernel is 2.6.34-rc1. The problem is: Every time I load nouveau_dri.so into RAM existing applications are broken / unusable (Example: gnome-games). It does not

http://bugs.freedesktop.org/show_bug.cgi?id=25806 Summary: NV40 vertex corruption (kernel BO deletion too early?) Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org

It seems that Noveau is assuming that once the FIFO pointer is past a command, that command has finished executing, and all the buffers it used are no longer needed. However, this seems to be false at least on G71. In particular, the card may not have even finished reading the input vertex buffers when the pushbuffer "fence" triggers. While Mesa does not reuse the buffer object itself,

Hi, I've been playing with nouveau/mesa branch gallium-0.1, trying to get trivial/tri working on nv20 (with nv10 code). When ever I resize the window, it ends up in an assert failure: #0 0xf790744f in _debug_assert_fail (expr=0xf791908f "0", file=0xf7919050 "nv20_state_emit.c", line=139, function=0xf7919034 "nv20_state_emit_framebuffer") at p_debug.c:335

I'm trying to run Wine 0.9.20 under OS X x86 and I'm getting nothing but "Bus Error" when I run any win32 program via Wine. Here is some relevant environment info: OS: Mac OS X 10.4.7 Xcode: Xcode 2.4 X11: XFree86 Version 4.4.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) gcc -v: Using built-in specs. Target: i686-apple-darwin8 Configured with:

I only got offered a few choices - I think I clicked yes to all of them. I read in one post that the answer is to uninstall and re-install the graphics drivers - not sure how that will help, but how do I uninstall nVidia's drivers? I have a vague memory of someone posting about lib32 paths and simlinks or something.

Multilingual Rails v0.5 is just released with lots of new features. Here is the changelog: v0.5: New charset conversion string-methods. Multilingual Rails always use UTF-8 internally. iconv_to(charset) # Return string as charset iconv_from(charset) # Return string as UTF-8, converted from charset iconv_from!(charset) # Convert string from charset to UTF-8

I'm willing to pay shipping in North America. Any takers? -Robyn

https://bugs.freedesktop.org/show_bug.cgi?id=70452 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Graphical corruption after |[NV43] Graphical corruption |resume from suspend or |after resume from suspend

https://bugs.freedesktop.org/show_bug.cgi?id=70452 Moi Jaiunvelo <moijaiunvelo at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.debian.org/7258 | |71 -- You are receiving this

https://bugs.freedesktop.org/show_bug.cgi?id=70452 --- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> --- Was your libdrm compiled with gcc-4.8? If so, make sure to get libdrm 2.4.48 or later. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=70452 --- Comment #5 from Moi Jaiunvelo <moijaiunvelo at gmail.com> --- Hi, I ignore against which gcc version my libdrm was compiled but my libdrm version is 2.4.46-3 (I run debian/testing) : Versions of packages xserver-xorg-video-nouveau depends on: ii libc6 2.17-93 ii libdrm-nouveau2

https://bugs.freedesktop.org/show_bug.cgi?id=70452 --- Comment #6 from Moi Jaiunvelo <moijaiunvelo at gmail.com> --- I tried to backport libdrm from debian/sid and it fixed the graphical corruption. More precisely for users who would like to reproduce it, I backported libdrm2, libdrm-intel1, libdrm-radeon1 and libdrm-nouveau2 from debian/sid to have them in 2.4.49-1 version. Start-Date:

https://bugs.freedesktop.org/show_bug.cgi?id=70452 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #7 from Martin Peres

http://bugs.freedesktop.org/show_bug.cgi?id=25639 Summary: NV43 (6600GT): Monitor goes blank during boot Product: xorg Version: 7.5 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=92386 Bug ID: 92386 Summary: Integrated sensor on nv43 doesn't work (wrong vbios parsing?) Product: xorg Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=57484 Priority: medium Bug ID: 57484 Assignee: nouveau at lists.freedesktop.org Summary: NV43: fail resume after suspend QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: xoddark at gmail.com

The inst variable (and thus engctx) will not be properly populated for pre-NV44 cards. The dma setter method didn't need it anyways, so call it directly instead of the nv_call indirection. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Tested on NV42. Ben, I'm going to guess that you hate this patch, since it gets rid of the beautiful nv_call stuff. However I wasn't