[Bug 36318] New: r600g segfaults
https://bugs.freedesktop.org/show_bug.cgi?id=36318 Summary: r600g segfaults Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: ianmllgn at gmail.com r600g segfaults running glxgears. Here is a backtrace #0 0x75327f6e in loopback_VertexAttrib3svNV (index=1283, v=0x1e08) at main/api_loopback.c:1137 #1 0x7532800f in loopback_VertexAttribs3svNV (index=, n=, v=0x2dd) at main/api_loopback.c:1220 #2 0x7525eed6 in execute_list (ctx=0xb55960, list=) at main/dlist.c:8163 #3 0x7526130a in _mesa_CallList (list=1) at main/dlist.c:8511 #4 0x00401ce2 in draw () #5 0x004035c9 in main () -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 32402] Oops associated with radeon_unpin_work_func
https://bugzilla.kernel.org/show_bug.cgi?id=32402 --- Comment #12 from Mike Mestnik 2011-04-16 21:28:03 --- On 04/16/11 16:08, bugzilla-daemon at bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=32402 > > > > > > --- Comment #11 from Adriano 2011-04-16 > 21:08:04 --- > An update: at least in my case, the problem seems to be related to page > flipping in the radeon driver. I have disabled page flipping in my xorg.conf > file and haven't seen the problem since. > Thank you for the update I haven?t seen this problem in a while and since then I've upgraded kernel and xorg/mesa. I have another issue that I'm sure is unrelated where my system locks up(no network not I/O) if I'm not running at least 3 facebook games: deeprealms, castle_age and sororitylife. > Here's some related links: > https://bugs.freedesktop.org/show_bug.cgi?id=35452 > https://bugs.gentoo.org/show_bug.cgi?id=359569 > > I would first see the heavy screen corruption described in the second link > above, and only later the kernel oops described in this bug report. > > I'm sorry if my problem isn't directly related to this bug report, but the > oops > message is very similar to the one I was getting. > > Thank you, > > Adriano > -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 32402] Oops associated with radeon_unpin_work_func
https://bugzilla.kernel.org/show_bug.cgi?id=32402 --- Comment #11 from Adriano 2011-04-16 21:08:04 --- An update: at least in my case, the problem seems to be related to page flipping in the radeon driver. I have disabled page flipping in my xorg.conf file and haven't seen the problem since. Here's some related links: https://bugs.freedesktop.org/show_bug.cgi?id=35452 https://bugs.gentoo.org/show_bug.cgi?id=359569 I would first see the heavy screen corruption described in the second link above, and only later the kernel oops described in this bug report. I'm sorry if my problem isn't directly related to this bug report, but the oops message is very similar to the one I was getting. Thank you, Adriano -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
2.6.39-rc1 nouveau regression (bisected)
On Sun, Apr 17, 2011 at 08:12:35AM +1000, Nigel Cunningham wrote: > On 15/04/11 16:11, Dominik Brodowski wrote: > > On Thu, Apr 14, 2011 at 09:02:01PM +0200, Marcin Slusarz wrote: > >> On Thu, Apr 14, 2011 at 07:05:59PM +0200, Dominik Brodowski wrote: > >>> Thought about CCing Linus to show him that 2.6.39-rcX isn't as "calm" > >>> to everyone, but then chose to CC Maciej instead: Would you be so kind and > >>> add this to your regression list? Thanks! > >>> > >>> Since commit 38f1cff > >>> > >>> From: Dave Airlie > >>> Date: Wed, 16 Mar 2011 11:34:41 +1000 > >>> Subject: [PATCH] Merge commit > >>> '5359533801e3dd3abca5b7d3d985b0b33fd9fe8b' into dr > >>> > >>> This commit changed an internal radeon structure, that meant a new > >>> driver > >>> in -next had to be fixed up, merge in the commit and fix up the > >>> driver. > >>> > >>> Also fixes a trivial nouveau merge. > >>> > >>> Conflicts: > >>> drivers/gpu/drm/nouveau/nouveau_mem.c > >>> > >>> booting my atom/NM10/ION2 system crashes hard during boot, right after > >>> blanking the screen, and before the initramfs gets loaded. I just > >>> re-checked: both parent commits ( 5359533 and 4819d2e ) do indeed work > >>> just fine, but the merge commit ( 38f1cff ) fails, same as tip ( 85f2e68 > >>> ). > >> Can you activate netconsole and check whether kernel spits anything > >> interesting? > >> You might try to load nouveau module after boot - maybe something will be > >> saved > >> to /var/log or you could even ssh into the box and check dmesg... > > Compiling it as a module seems to work fine. When I do so, no regression is > > obvious from what gets reported in "dmesg". However, somehow I now do get > > some output: The last message I see is > > > > [drm] nouveau :01:00.0: allocated 1680x1050, fb 0x40 b0 > pointer value> > > > > Then, nothing more. However, it really is quite strange why this error only > > appears in the CONFIG_NOUVEAU=y case, not in the =m case... > Try disabling CONFIG_BOOT_LOGO. I reported on freedesktop.org that it is > causing me an oops at boot, but my bug has been ignored there so far - > perhaps I should have posted it here instead. I'm getting the exact same symptoms on my Atom + ION hardware. Crashes before it can write any logs if it's compiled in and the logo is selected, but boots fine if compiled as a module or the logo is removed. In my case I bisected and found 8969960 by Nick Piggin (change to mm/vmalloc.c) to be the first bad one in 2.6.38+. This makes me think that it's not a bug in nouveau, but maybe a bug in the order that things are initialized? Config below. (It boots as is, but if you enable CONFIG_LOGO it won't.) # # Automatically generated make config: don't edit # Linux/x86 2.6.39-rc3 Kernel Configuration # Sat Apr 16 19:39:23 2011 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf32-i386" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_ZONE_DMA=y # CONFIG_NEED_DMA_MAP_STATE is not set CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_32_LAZY_GS=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-ecx -fcall-saved-edx" CONFIG_KTIME_SCALAR=y CONFIG_ARCH_CPU_PROBE_RELEASE=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y CONFIG_HAVE_IRQ_WORK=y CONFIG_IRQ_WORK=y # # General setup # # CONFIG_EXPERIMENTAL is not set CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3
Linux 2.6.39-rc3
On Fri, Apr 15, 2011 at 12:11:28PM -0400, Jerome Glisse wrote: > Do you also got the write if you load radeon with radeon.no_wb=1 ? > I think at this address it's the wb page, or maybe the cp as wb likely > take only one page radeon.no_wb=1 makes no difference. The box still reboots. Joerg
Linux 2.6.39-rc3
On Sat, Apr 16, 2011 at 12:35 PM, Joerg Roedel wrote: > On Fri, Apr 15, 2011 at 12:11:28PM -0400, Jerome Glisse wrote: >> Do you also got the write if you load radeon with radeon.no_wb=1 ? >> I think at this address it's the wb page, or maybe the cp as wb likely >> take only one page > > radeon.no_wb=1 makes no difference. The box still reboots. > > ? ? ? ?Joerg > > If you want to go the printk way you can add printk before each test ring_test, ib_test in r600.c this 2 functions are the own that might trigger the first GPU gart activities. Cheers, Jerome
Linux 2.6.39-rc3
* Joerg Roedel wrote: > On Fri, Apr 15, 2011 at 09:06:41PM +0200, Ingo Molnar wrote: > > > > * Alexandre Demers wrote: > > > > > On 11-04-15 10:27 AM, Joerg Roedel wrote: > > > > On Fri, Apr 15, 2011 at 10:16:59AM -0400, Alexandre Demers wrote: > > > >> Ok, I'll test it today. Should I apply it on a clean rc3 without any of > > > >> the other patches? > > > > Yes, apply it just on -rc3 without any other patch. > > > > > > > >> BTW, may I suggest adding the info under bug 33012 in kernel bugzilla? > > > >> This could be useful in the future. > > > > Cool, thanks > > > > > > > > > > > > Joerg > > > The patch was applied and tested. It looks fine, I'm able to boot > > > without problem. > > > > Joerg, mind submitting it with a changelog that includes everything we > > learned > > about this bug and all the Tested-by's in place? > > Looks like I am too late, it is already applied. But the changelog > contains a link to the korg-bugzilla which has all information too. So > the information is not lost. Yeah. In this case getting the fix into -rc4 in a timely manner looked more important than waiting for an updated changelog :-) Thanks, Ingo
Linux 2.6.39-rc3
On Fri, Apr 15, 2011 at 12:18:02PM -0700, Yinghai Lu wrote: > On 04/15/2011 12:06 PM, Ingo Molnar wrote: > > > > > Joerg, mind submitting it with a changelog that includes everything we > > learned > > about this bug and all the Tested-by's in place? > > > > Is anyone of the opinion that we should try to revert the allocation > > order/alignment changes in addition to this fix? > > We should figure out what is written to 0xa0001000 (main memory) by GPU > before internal GART is setup. > > Joerg, > can you insert some dump code in the drm/radon code to find out which > function cause the problem? I am not a GPU expert, but I will see what I can find out. Joerg
Linux 2.6.39-rc3
On Fri, Apr 15, 2011 at 09:06:41PM +0200, Ingo Molnar wrote: > > * Alexandre Demers wrote: > > > On 11-04-15 10:27 AM, Joerg Roedel wrote: > > > On Fri, Apr 15, 2011 at 10:16:59AM -0400, Alexandre Demers wrote: > > >> Ok, I'll test it today. Should I apply it on a clean rc3 without any of > > >> the other patches? > > > Yes, apply it just on -rc3 without any other patch. > > > > > >> BTW, may I suggest adding the info under bug 33012 in kernel bugzilla? > > >> This could be useful in the future. > > > Cool, thanks > > > > > > > > > Joerg > > The patch was applied and tested. It looks fine, I'm able to boot > > without problem. > > Joerg, mind submitting it with a changelog that includes everything we > learned > about this bug and all the Tested-by's in place? Looks like I am too late, it is already applied. But the changelog contains a link to the korg-bugzilla which has all information too. So the information is not lost. Joerg
[PATCH] fix mesa tarball creation again
Hi The following patch fixes mesa tarball creation again -- next part -- A non-text attachment was scrubbed... Name: fix-tarball-creation.diff Type: text/x-patch Size: 446 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20110416/fa0adc27/attachment.bin>
[Bug 36236] Problems with lights in Trine game from www.humblebundle.com
https://bugs.freedesktop.org/show_bug.cgi?id=36236 --- Comment #15 from Sven Arvidsson 2011-04-16 07:02:14 PDT --- (In reply to comment #14) > Interesting, I have this with llvmpipe too, but it looks correct with nvc0, so > I'd look for a driver specific issue. This is interesting, would it be possible to track down the bug by comparing logs from llvmpipe and nvc0? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28847] Regnum Online: shader backend not rendering
https://bugs.freedesktop.org/show_bug.cgi?id=28847 Sven Arvidsson changed: What|Removed |Added Summary|[r300c, r300g] Regnum |Regnum Online: shader |Online only works in safe |backend not rendering |mode| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 2/2] drm: parse color format support for digital displays
On Sat, Apr 16, 2011 at 6:39 AM, Jesse Barnes
wrote:
> On Sat, 16 Apr 2011 06:10:07 +1000
> Dave Airlie wrote:
>
>> > -
>> > +#define DRM_COLOR_FORMAT_RGB444 ? ? ? ? ? ? ? ?(1<<0)
>> > +#define DRM_COLOR_FORMAT_YCRCB444 ? ? ?(1<<1)
>> > +#define DRM_COLOR_FORMAT_YCRCB422 ? ? ?(1<<2)
>> > ?/*
>> > ?* Describes a given display (e.g. CRT or flat panel) and its limitations.
>> > ?*/
>> > @@ -201,6 +203,7 @@ struct drm_display_info {
>> > ? ? ? ?unsigned int bpc;
>> >
>> > ? ? ? ?enum subpixel_order subpixel_order;
>> > + ? ? ? unsigned long color_formats;
>>
>> ^ wtf?
>>
>> unsigned long? its 2011.
>
> That doesn't tell me much about what you'd prefer... ?I figured a
> bitfield would be fairly extensible if new surface formats were added.
> Maybe you're thinking it's not enough to support all the misc ones out
> there though?
Its unsigned long, its a different size on 32 and 64-bit, not
something I want to fall
over when you add the 33rd bit field.
Dave.
[Bug 36256] Return to tty after leaving X problematic if using multiple cards since 2.6.32
https://bugs.freedesktop.org/show_bug.cgi?id=36256 --- Comment #1 from Connor Behan 2011-04-16 06:42:01 PDT --- I can make the consoles work if I delete /dev/vga_arbiter before starting X. This explains why 2.6.32 was the first kernel where I had this problem. Can you go back to making vga_arb a module so people can solve this properly? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 2/2] drm: parse color format support for digital displays
> -
> +#define DRM_COLOR_FORMAT_RGB444 ? ? ? ? ? ? ? ?(1<<0)
> +#define DRM_COLOR_FORMAT_YCRCB444 ? ? ?(1<<1)
> +#define DRM_COLOR_FORMAT_YCRCB422 ? ? ?(1<<2)
> ?/*
> ?* Describes a given display (e.g. CRT or flat panel) and its limitations.
> ?*/
> @@ -201,6 +203,7 @@ struct drm_display_info {
> ? ? ? ?unsigned int bpc;
>
> ? ? ? ?enum subpixel_order subpixel_order;
> + ? ? ? unsigned long color_formats;
^ wtf?
unsigned long? its 2011.
Dave.
[Bug 36295] Incorrect rendering in SPECviewperf benchmark
https://bugs.freedesktop.org/show_bug.cgi?id=36295 Jos? Fonseca changed: What|Removed |Added Product|DRI |Mesa Version|unspecified |git Component|DRM/Radeon |Mesa core AssignedTo|dri-devel at lists.freedesktop |mesa-dev at lists.freedesktop. |.org|org CC||brianp at vmware.com --- Comment #2 from Jos? Fonseca 2011-04-16 02:50:43 PDT --- This is a bug in SPECviewperf11, which relies on NV_fragment_program2 extension, even when it is not advertised. Me and Brian have a patch that workarounds this by tolerating NV_fragment_program2 's IF/ELSE/ENDIF opcodes. This is exactly the same stratergy that AMD's fglrx drivers took: not advertise NVIDIA's extension, but silently handle it. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36295] Incorrect rendering in SPECviewperf benchmark
https://bugs.freedesktop.org/show_bug.cgi?id=36295 --- Comment #1 from pelloux at gmail.com 2011-04-16 02:35:29 PDT --- Forgot to mention that tests 3/7 and 4/7 print some Mesa errors when running with ST_DEUG=fallback,mesa : test3 : Mesa: User error: GL_INVALID_OPERATION in glBegin(fragment program not valid) Mesa: User error: GL_INVALID_OPERATION in glEnd Mesa: User error: GL_INVALID_OPERATION in glProgramStringARB(invalid ARB fragment program option) test4 : Mesa: User error: GL_INVALID_OPERATION in glProgramStringARB(invalid ARB vertex program option) Mesa: User error: GL_INVALID_OPERATION in glProgramString(bad program) Mesa: User error: GL_INVALID_OPERATION in glProgramStringARB(invalid ARB fragment program option) Mesa: User error: GL_INVALID_OPERATION in glDrawElements(vertex program not valid) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36295] New: Incorrect rendering in SPECviewperf benchmark
https://bugs.freedesktop.org/show_bug.cgi?id=36295 Summary: Incorrect rendering in SPECviewperf benchmark Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: pelloux at gmail.com Created an attachment (id=45701) --> (https://bugs.freedesktop.org/attachment.cgi?id=45701) rendering comparison intel vs r600g Using mesa from GIT + r600g, 7 first tests of SPECviewperf 11 show big rendering errors (see attached image). The same tests run well using an Intel based laptop (with Ubuntu 9.10). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 35998] Artifacts under Gnome Shell
https://bugs.freedesktop.org/show_bug.cgi?id=35998 --- Comment #5 from robhae at gmail.com 2011-04-16 01:53:47 PDT --- Same artifacts here. x1250 (Gallium-Driver) on Samsung R60 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36289] Text is unreadable/completely mangled.
https://bugs.freedesktop.org/show_bug.cgi?id=36289 dnm changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #2 from dnm 2011-04-16 01:42:21 PDT --- I think you may be right. Apologies for the bug duplication; font rendering issues yields a problem in searches in that there's so many synonyms to search for, and finding the bug you speak of may prove difficult. (Do I search for distortion or mangled or unreadable or rendered incorrectly, or .. or .. or.. :) I'll give #34280 a check out tomorrow and reopen if it's not fixed, but I highly suspect that not to be the case. Thanks for your help. *** This bug has been marked as a duplicate of bug 34280 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36289] Text is unreadable/completely mangled.
https://bugs.freedesktop.org/show_bug.cgi?id=36289 --- Comment #1 from Nicolas Kaiser 2011-04-16 01:38:50 PDT --- Looks like bug 34280, which was recently fixed. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36289] New: Text is unreadable/completely mangled.
https://bugs.freedesktop.org/show_bug.cgi?id=36289 Summary: Text is unreadable/completely mangled. Product: Mesa Version: 7.10 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: freedesktop.org at datademons.com Created an attachment (id=45695) --> (https://bugs.freedesktop.org/attachment.cgi?id=45695) Example of mangled text. My card is an old Radeon 9200 (rv280). Using debian stable, w/mesa 7.7.1, text in opengl applications renders properly, but mesa is very slow, so I decided to try out mesa 7.10 from debian testing. With debian testing (mesa 7.10), and unstable (mesa 7.10.2), the text is completely mangled and unreadable. I will attach a screenshot of an xbmc screen from my htpc that shows the mangled text. Other OpenGL apps behave the same way; all the text is completely unreadable, but everything else renders beautifully (and quickly!) Running OpenGL applications with LIBGL_DEBUG=verbose yields no errors other than: libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/htpc/.drirc: No such file or directory. The relevant entries from my dpkg listing: ii libgl1-mesa-dev 7.10.2-1 A free implementation of the OpenGL API -- GLX development files ii libgl1-mesa-dri 7.10.2-1 A free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx 7.10.2-1 A free implementation of the OpenGL API -- GLX runtime ii libglu1-mesa7.10.2-1 The OpenGL utility library (GLU) ii libglu1-mesa-dev7.10.2-1 The OpenGL utility library -- development files ii mesa-common-dev 7.10.2-1 Developer documentation for Mesa ii mesa-utils 8.0.1-2 Miscellaneous Mesa GL utilities Adding the option: Option NoAccel true to xorg.conf makes the text render properly in all versions of Mesa, but as you'd imagine, makes programs unusably slow. Let me know if you require any other information from me. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 35312] r600g: Automatic mipmap generation doesn't work properly
https://bugs.freedesktop.org/show_bug.cgi?id=35312 --- Comment #4 from Francis Whittle 2011-04-16 00:08:05 PDT --- Patch is strictly a work-around and a bloody hack (dripping even). Indicates there's something should be happening in the driver code that isn't. "Fixes" was a bad word choice. Anyway, I can confirm this bug on RS880 (Radeon HD 4200). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 35312] r600g: Automatic mipmap generation doesn't work properly
https://bugs.freedesktop.org/show_bug.cgi?id=35312 --- Comment #4 from Francis Whittle fj.whit...@gmail.com 2011-04-16 00:08:05 PDT --- Patch is strictly a work-around and a bloody hack (dripping even). Indicates there's something should be happening in the driver code that isn't. Fixes was a bad word choice. Anyway, I can confirm this bug on RS880 (Radeon HD 4200). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] fix mesa tarball creation again
Hi The following patch fixes mesa tarball creation again diff --git a/Makefile b/Makefile index be95679..646e152 100644 --- a/Makefile +++ b/Makefile @@ -250,7 +250,6 @@ MAIN_FILES = \ $(DIRECTORY)/src/mesa/math/descrip.mms\ $(DIRECTORY)/src/mesa/program/*.[chly]\ $(DIRECTORY)/src/mesa/program/*.cpp\ - $(DIRECTORY)/src/mesa/program/Makefile\ $(DIRECTORY)/src/mesa/program/descrip.mms \ $(DIRECTORY)/src/mesa/swrast/*.[ch]\ $(DIRECTORY)/src/mesa/swrast/descrip.mms \ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36289] Text is unreadable/completely mangled.
https://bugs.freedesktop.org/show_bug.cgi?id=36289 --- Comment #1 from Nicolas Kaiser ni...@nikai.net 2011-04-16 01:38:50 PDT --- Looks like bug 34280, which was recently fixed. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36289] Text is unreadable/completely mangled.
https://bugs.freedesktop.org/show_bug.cgi?id=36289 dnm freedesktop@datademons.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #2 from dnm freedesktop@datademons.com 2011-04-16 01:42:21 PDT --- I think you may be right. Apologies for the bug duplication; font rendering issues yields a problem in searches in that there's so many synonyms to search for, and finding the bug you speak of may prove difficult. (Do I search for distortion or mangled or unreadable or rendered incorrectly, or .. or .. or.. :) I'll give #34280 a check out tomorrow and reopen if it's not fixed, but I highly suspect that not to be the case. Thanks for your help. *** This bug has been marked as a duplicate of bug 34280 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35998] Artifacts under Gnome Shell
https://bugs.freedesktop.org/show_bug.cgi?id=35998 --- Comment #5 from rob...@gmail.com 2011-04-16 01:53:47 PDT --- Same artifacts here. x1250 (Gallium-Driver) on Samsung R60 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36295] New: Incorrect rendering in SPECviewperf benchmark
https://bugs.freedesktop.org/show_bug.cgi?id=36295 Summary: Incorrect rendering in SPECviewperf benchmark Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: pell...@gmail.com Created an attachment (id=45701) -- (https://bugs.freedesktop.org/attachment.cgi?id=45701) rendering comparison intel vs r600g Using mesa from GIT + r600g, 7 first tests of SPECviewperf 11 show big rendering errors (see attached image). The same tests run well using an Intel based laptop (with Ubuntu 9.10). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36295] Incorrect rendering in SPECviewperf benchmark
https://bugs.freedesktop.org/show_bug.cgi?id=36295 --- Comment #1 from pell...@gmail.com 2011-04-16 02:35:29 PDT --- Forgot to mention that tests 3/7 and 4/7 print some Mesa errors when running with ST_DEUG=fallback,mesa : test3 : Mesa: User error: GL_INVALID_OPERATION in glBegin(fragment program not valid) Mesa: User error: GL_INVALID_OPERATION in glEnd Mesa: User error: GL_INVALID_OPERATION in glProgramStringARB(invalid ARB fragment program option) test4 : Mesa: User error: GL_INVALID_OPERATION in glProgramStringARB(invalid ARB vertex program option) Mesa: User error: GL_INVALID_OPERATION in glProgramString(bad program) Mesa: User error: GL_INVALID_OPERATION in glProgramStringARB(invalid ARB fragment program option) Mesa: User error: GL_INVALID_OPERATION in glDrawElements(vertex program not valid) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36295] Incorrect rendering in SPECviewperf benchmark
https://bugs.freedesktop.org/show_bug.cgi?id=36295 José Fonseca jfons...@vmware.com changed: What|Removed |Added Product|DRI |Mesa Version|unspecified |git Component|DRM/Radeon |Mesa core AssignedTo|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org|org CC||bri...@vmware.com --- Comment #2 from José Fonseca jfons...@vmware.com 2011-04-16 02:50:43 PDT --- This is a bug in SPECviewperf11, which relies on NV_fragment_program2 extension, even when it is not advertised. Me and Brian have a patch that workarounds this by tolerating NV_fragment_program2 's IF/ELSE/ENDIF opcodes. This is exactly the same stratergy that AMD's fglrx drivers took: not advertise NVIDIA's extension, but silently handle it. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [RFC] drm: emit change events when mode config changes
On 04/14/2011 12:42 PM, Jesse Barnes wrote:
We've already seen that apps want to monitor the display config, and
some (like upowerd) poll for changes since we don't provide a
notification for general mode config changes, just hotplug events. So
add a new drm event, with CHANGE=1 set in the event, to allow for it.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
index 4c95b5f..174ee64 100644
--- a/drivers/gpu/drm/drm_crtc.c
+++ b/drivers/gpu/drm/drm_crtc.c
@@ -1589,6 +1589,8 @@ int drm_mode_setcrtc(struct drm_device *dev, void *data,
set.fb = fb;
ret = crtc-funcs-set_config(set);
+ drm_sysfs_change_event(dev);
+
out:
kfree(connector_set);
mutex_unlock(dev-mode_config.mutex);
diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
index 9507204..df946d4 100644
--- a/drivers/gpu/drm/drm_fb_helper.c
+++ b/drivers/gpu/drm/drm_fb_helper.c
@@ -822,6 +822,8 @@ int drm_fb_helper_set_par(struct fb_info *info)
return ret;
}
}
+
+ drm_sysfs_change_event(dev);
mutex_unlock(dev-mode_config.mutex);
if (fb_helper-delayed_hotplug) {
diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c
index 2eee8e0..fd3af31 100644
--- a/drivers/gpu/drm/drm_sysfs.c
+++ b/drivers/gpu/drm/drm_sysfs.c
@@ -467,9 +467,9 @@ EXPORT_SYMBOL(drm_sysfs_connector_remove);
* drm_sysfs_hotplug_event - generate a DRM uevent
* @dev: DRM device
*
- * Send a uevent for the DRM device specified by @dev. Currently we only
- * set HOTPLUG=1 in the uevent environment, but this could be expanded to
- * deal with other types of events.
+ * Send a uevent for the DRM device specified by @dev. Set HOTPLUG=1 in the
+ * event to indicate a display config change occurred, probably due to a
+ * display being added or removed.
*/
void drm_sysfs_hotplug_event(struct drm_device *dev)
{
@@ -483,6 +483,24 @@ void drm_sysfs_hotplug_event(struct drm_device *dev)
EXPORT_SYMBOL(drm_sysfs_hotplug_event);
/**
+ * drm_sysfs_change_event - generate a DRM uevent indicating a display
config change
+ * @dev: DRM device
+ *
+ * Send a uevent for the DRM device specified by @dev. Set CHANGE=1 to
+ * indicate that a userspace initiated display configuration change occurred.
+ */
+void drm_sysfs_change_event(struct drm_device *dev)
+{
+ char *event_string = CHANGE=1;
+ char *envp[] = { event_string, NULL };
+
+ DRM_DEBUG(generating hotplug event\n);
Should be change event here?
+
+ kobject_uevent_env(dev-primary-kdev.kobj, KOBJ_CHANGE, envp);
+}
+EXPORT_SYMBOL(drm_sysfs_change_event);
+
+/**
* drm_sysfs_device_add - adds a class device to sysfs for a character driver
* @dev: DRM device to be added
* @head: DRM head in question
diff --git a/include/drm/drmP.h b/include/drm/drmP.h
index ad5770f..3aff8fc 100644
--- a/include/drm/drmP.h
+++ b/include/drm/drmP.h
@@ -1506,6 +1506,7 @@ extern struct class *drm_sysfs_create(struct module
*owner, char *name);
extern void drm_sysfs_destroy(void);
extern int drm_sysfs_device_add(struct drm_minor *minor);
extern void drm_sysfs_hotplug_event(struct drm_device *dev);
+extern void drm_sysfs_change_event(struct drm_device *dev);
extern void drm_sysfs_device_remove(struct drm_minor *minor);
extern char *drm_get_connector_status_name(enum drm_connector_status status);
extern int drm_sysfs_connector_add(struct drm_connector *connector);
--
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
--
___
Dri-devel mailing list
dri-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
--
___
Dri-devel mailing list
dri-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Linux 2.6.39-rc3
On Fri, Apr 15, 2011 at 09:06:41PM +0200, Ingo Molnar wrote: * Alexandre Demers alexandre.f.dem...@gmail.com wrote: On 11-04-15 10:27 AM, Joerg Roedel wrote: On Fri, Apr 15, 2011 at 10:16:59AM -0400, Alexandre Demers wrote: Ok, I'll test it today. Should I apply it on a clean rc3 without any of the other patches? Yes, apply it just on -rc3 without any other patch. BTW, may I suggest adding the info under bug 33012 in kernel bugzilla? This could be useful in the future. Cool, thanks Joerg The patch was applied and tested. It looks fine, I'm able to boot without problem. Joerg, mind submitting it with a changelog that includes everything we learned about this bug and all the Tested-by's in place? Looks like I am too late, it is already applied. But the changelog contains a link to the korg-bugzilla which has all information too. So the information is not lost. Joerg ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Linux 2.6.39-rc3
On Fri, Apr 15, 2011 at 12:18:02PM -0700, Yinghai Lu wrote: On 04/15/2011 12:06 PM, Ingo Molnar wrote: Joerg, mind submitting it with a changelog that includes everything we learned about this bug and all the Tested-by's in place? Is anyone of the opinion that we should try to revert the allocation order/alignment changes in addition to this fix? We should figure out what is written to 0xa0001000 (main memory) by GPU before internal GART is setup. Joerg, can you insert some dump code in the drm/radon code to find out which function cause the problem? I am not a GPU expert, but I will see what I can find out. Joerg ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Linux 2.6.39-rc3
* Joerg Roedel j...@8bytes.org wrote: On Fri, Apr 15, 2011 at 09:06:41PM +0200, Ingo Molnar wrote: * Alexandre Demers alexandre.f.dem...@gmail.com wrote: On 11-04-15 10:27 AM, Joerg Roedel wrote: On Fri, Apr 15, 2011 at 10:16:59AM -0400, Alexandre Demers wrote: Ok, I'll test it today. Should I apply it on a clean rc3 without any of the other patches? Yes, apply it just on -rc3 without any other patch. BTW, may I suggest adding the info under bug 33012 in kernel bugzilla? This could be useful in the future. Cool, thanks Joerg The patch was applied and tested. It looks fine, I'm able to boot without problem. Joerg, mind submitting it with a changelog that includes everything we learned about this bug and all the Tested-by's in place? Looks like I am too late, it is already applied. But the changelog contains a link to the korg-bugzilla which has all information too. So the information is not lost. Yeah. In this case getting the fix into -rc4 in a timely manner looked more important than waiting for an updated changelog :-) Thanks, Ingo ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36256] Return to tty after leaving X problematic if using multiple cards since 2.6.32
https://bugs.freedesktop.org/show_bug.cgi?id=36256 --- Comment #1 from Connor Behan connor.be...@gmail.com 2011-04-16 06:42:01 PDT --- I can make the consoles work if I delete /dev/vga_arbiter before starting X. This explains why 2.6.32 was the first kernel where I had this problem. Can you go back to making vga_arb a module so people can solve this properly? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28847] Regnum Online: shader backend not rendering
https://bugs.freedesktop.org/show_bug.cgi?id=28847 Sven Arvidsson s...@whiz.se changed: What|Removed |Added Summary|[r300c, r300g] Regnum |Regnum Online: shader |Online only works in safe |backend not rendering |mode| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36236] Problems with lights in Trine game from www.humblebundle.com
https://bugs.freedesktop.org/show_bug.cgi?id=36236 --- Comment #15 from Sven Arvidsson s...@whiz.se 2011-04-16 07:02:14 PDT --- (In reply to comment #14) Interesting, I have this with llvmpipe too, but it looks correct with nvc0, so I'd look for a driver specific issue. This is interesting, would it be possible to track down the bug by comparing logs from llvmpipe and nvc0? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Linux 2.6.39-rc3
On Fri, Apr 15, 2011 at 12:11:28PM -0400, Jerome Glisse wrote: Do you also got the write if you load radeon with radeon.no_wb=1 ? I think at this address it's the wb page, or maybe the cp as wb likely take only one page radeon.no_wb=1 makes no difference. The box still reboots. Joerg ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Linux 2.6.39-rc3
On Sat, Apr 16, 2011 at 12:35 PM, Joerg Roedel j...@8bytes.org wrote: On Fri, Apr 15, 2011 at 12:11:28PM -0400, Jerome Glisse wrote: Do you also got the write if you load radeon with radeon.no_wb=1 ? I think at this address it's the wb page, or maybe the cp as wb likely take only one page radeon.no_wb=1 makes no difference. The box still reboots. Joerg If you want to go the printk way you can add printk before each test ring_test, ib_test in r600.c this 2 functions are the own that might trigger the first GPU gart activities. Cheers, Jerome ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 32402] Oops associated with radeon_unpin_work_func
https://bugzilla.kernel.org/show_bug.cgi?id=32402 --- Comment #11 from Adriano adriano.vil...@yahoo.com 2011-04-16 21:08:04 --- An update: at least in my case, the problem seems to be related to page flipping in the radeon driver. I have disabled page flipping in my xorg.conf file and haven't seen the problem since. Here's some related links: https://bugs.freedesktop.org/show_bug.cgi?id=35452 https://bugs.gentoo.org/show_bug.cgi?id=359569 I would first see the heavy screen corruption described in the second link above, and only later the kernel oops described in this bug report. I'm sorry if my problem isn't directly related to this bug report, but the oops message is very similar to the one I was getting. Thank you, Adriano -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 32402] Oops associated with radeon_unpin_work_func
https://bugzilla.kernel.org/show_bug.cgi?id=32402 --- Comment #12 from Mike Mestnik cheako...@gmail.com 2011-04-16 21:28:03 --- On 04/16/11 16:08, bugzilla-dae...@bugzilla.kernel.org wrote: https://bugzilla.kernel.org/show_bug.cgi?id=32402 --- Comment #11 from Adriano adriano.vil...@yahoo.com 2011-04-16 21:08:04 --- An update: at least in my case, the problem seems to be related to page flipping in the radeon driver. I have disabled page flipping in my xorg.conf file and haven't seen the problem since. Thank you for the update I haven’t seen this problem in a while and since then I've upgraded kernel and xorg/mesa. I have another issue that I'm sure is unrelated where my system locks up(no network not I/O) if I'm not running at least 3 facebook games: deeprealms, castle_age and sororitylife. Here's some related links: https://bugs.freedesktop.org/show_bug.cgi?id=35452 https://bugs.gentoo.org/show_bug.cgi?id=359569 I would first see the heavy screen corruption described in the second link above, and only later the kernel oops described in this bug report. I'm sorry if my problem isn't directly related to this bug report, but the oops message is very similar to the one I was getting. Thank you, Adriano -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36318] New: r600g segfaults
https://bugs.freedesktop.org/show_bug.cgi?id=36318 Summary: r600g segfaults Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: ianml...@gmail.com r600g segfaults running glxgears. Here is a backtrace #0 0x75327f6e in loopback_VertexAttrib3svNV (index=1283, v=0x1e08) at main/api_loopback.c:1137 #1 0x7532800f in loopback_VertexAttribs3svNV (index=value optimized out, n=value optimized out, v=0x2dd) at main/api_loopback.c:1220 #2 0x7525eed6 in execute_list (ctx=0xb55960, list=value optimized out) at main/dlist.c:8163 #3 0x7526130a in _mesa_CallList (list=1) at main/dlist.c:8511 #4 0x00401ce2 in draw () #5 0x004035c9 in main () -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
