dri-devel June 2011

dri-devel@lists.freedesktop.org

101 participants
499 discussions

[Bug 37471] New: Website with information about maintainers/developers
by bugzilla-daemon＠freedesktop.org 29 May '19

29 May '19

https://bugs.freedesktop.org/show_bug.cgi?id=37471 Summary: Website with information about maintainers/developers Product: DRI Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de There should be a website with information about main developers/maintainers: Product (DRM Intel, DRM Radeon, Mesa) | Component[s] (Maintainer, Core developer, Intel, R200, R300, R600, nouveau, ...) | Real Name | eMail | Name on IRC | Usual time to ask (e.g. 17 to 20 UTC) | Available on IRC channels (#dri-devel, #nouveau, ...) | Working for [Red Hat, SUSE, Linux Foundation, Ubuntu, ...] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[PATCH wq#for-linus] drm: fix a fallout from slow-work -> wq conversion
by Tejun Heo 19 Jun '18

19 Jun '18

Commit 991ea75c (drm: use workqueue instead of slow-work), which made drm to use wq instead of slow-work, didn't account for the return value difference between delayed_slow_work_enqueue() and queue_delayed_work(). The former returns 0 on success and -errno on failures while the latter never fails and only uses the return value to indicate whether the work was already pending or not. This misconversion triggered spurious error messages. Remove the now unnecessary return value check and error message. Signed-off-by: Tejun Heo <tj(a)kernel.org> Reported-by: Markus Trippelsdorf <markus(a)trippelsdorf.de> Cc: David Airlie <airlied(a)linux.ie> Cc: dri-devel(a)lists.freedesktop.org --- Markus, it's almost trivial but it would be great if you can test this one too. David, may I route this wq#for-linus? Thanks. drivers/gpu/drm/drm_crtc_helper.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc_helper.c b/drivers/gpu/drm/drm_crtc_helper.c index 4598130..211ed7e 100644 --- a/drivers/gpu/drm/drm_crtc_helper.c +++ b/drivers/gpu/drm/drm_crtc_helper.c @@ -839,7 +839,6 @@ static void output_poll_execute(struct work_struct *work) struct drm_connector *connector; enum drm_connector_status old_status, status; bool repoll = false, changed = false; - int ret; mutex_lock(&dev->mode_config.mutex); list_for_each_entry(connector, &dev->mode_config.connector_list, head) { @@ -874,11 +873,8 @@ static void output_poll_execute(struct work_struct *work) dev->mode_config.funcs->output_poll_changed(dev); } - if (repoll) { - ret = queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); - if (ret) - DRM_ERROR("delayed enqueue failed %d\n", ret); - } + if (repoll) + queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); } void drm_kms_helper_poll_disable(struct drm_device *dev)

4 4

[Bug 28771] New: Vsync always on
by bugzilla-daemon＠freedesktop.org 12 Jun '18

12 Jun '18

https://bugs.freedesktop.org/show_bug.cgi?id=28771 Summary: Vsync always on Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se With kernel 2.6.35, there doesn't seem to be a way to turn off vsync/vblank. E.g. "vblank_mode=0 glxgears" has no effect. This seems to be the same for both r300c and r300g. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: RV570 -- Model: Asus EAX1950Pro 256MB -- Display connector: DVI -- xf86-video-ati: 801e83227a59a29eea425ea612083bbf2b536c30 -- xserver: 1.8.1.901 -- mesa: a5c44986a3f19936df448fe4ae47ca77ece9b0ce -- drm: 6ea2bda5f5ec8f27359760ce580fdad3df0464df -- kernel: 2.6.35-rc3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[Bug 36072] New: celestia causes kernel oops when allocation a lot of memory (for textures)
by bugzilla-daemon＠bugzilla.kernel.org 28 Feb '18

28 Feb '18

https://bugzilla.kernel.org/show_bug.cgi?id=36072 Summary: celestia causes kernel oops when allocation a lot of memory (for textures) Product: Drivers Version: 2.5 Kernel Version: 2.6.38 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: acelists(a)atlas.sk Regression: Yes The celestia program often allocates a lot of memory (like 1.5GB on my 2GB machine with 3GB swap) for its textures. I don't know where it stores them (probably not Video memory), but it seems in system RAM, because swap is used much. Sometimes when this happens the kernel crashes. After that I can only sync and reboot the machine with alt-sysrq commands. I have only noticed this with kernel 2.6.38.x, not before. I was using the OSS ati driver 6.14.1, with mesa 7.10.2. All including the kernel seft compiled (for AMD fam10h CPU). I do not understand the first line of the log. Where can I increase the vmalloc size. Is the on the kernel command line? But it should not crash the kernel in any case, just the program. Here is the kernel log: May 19 21:26:52 coolbox kernel: vmap allocation for size 178982912 failed: use vmalloc=<size> to increase size. May 19 21:26:52 coolbox kernel: BUG: unable to handle kernel paging request at b892a45d May 19 21:26:52 coolbox kernel: IP: [<f9696a50>] ttm_mem_io_lock+0x0/0x20 [ttm] May 19 21:26:52 coolbox kernel: *pde = 00000000 May 19 21:26:52 coolbox kernel: Oops: 0000 [#1] PREEMPT SMP May 19 21:26:52 coolbox kernel: last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:01/ATK0110:00/hwmon/hwmon0/fan3_input May 19 21:26:52 coolbox kernel: Modules linked in: fbcon font bitblit softcursor radeon ttm drm_kms_helper drm agpgart fb fbdev autofs4 cfbcopyarea cfbimgblt cfbfillrect nf_conntrack_ftp xt_tcpudp xt_owner xt_multiport nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT ipt_LOG iptable_filter ip_tables x_tables asus_atk0110 snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss cpufreq_conservative cpufreq_ondemand psmouse pcspkr cx88_blackbird firmware_class cx2341x cx8802 tuner_simple tuner_types tda9887 tda8290 tea5767 tuner cx8800 cx88xx rc_core i2c_algo_bit tveeprom v4l2_common videodev btcx_risc videobuf_dma_sg videobuf_core forcedeth snd_hda_codec_via snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore snd_page_alloc i2c_nforce2 i2c_core ext4 mbcache jbd2 crc16 usbhid powernow_k8 processor mperf ohci_hcd ehci_hcd usbcore fuse May 19 21:26:52 coolbox kernel: May 19 21:26:52 coolbox kernel: Pid: 25014, comm: celestia Not tainted 2.6.38.6 #57 System manufacturer System Product Name/M2N68 May 19 21:26:52 coolbox kernel: EIP: 0060:[<f9696a50>] EFLAGS: 00010246 CPU: 3 May 19 21:26:52 coolbox kernel: EIP is at ttm_mem_io_lock+0x0/0x20 [ttm] May 19 21:26:52 coolbox kernel: EAX: b892a420 EBX: d03cfc28 ECX: 00000000 EDX: 00000000 May 19 21:26:52 coolbox kernel: ESI: f519a40c EDI: b892a420 EBP: d03cfd48 ESP: d03cfbf0 May 19 21:26:52 coolbox kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 May 19 21:26:52 coolbox kernel: Process celestia (pid: 25014, ti=d03ce000 task=f06fb830 task.ti=d03ce000) May 19 21:26:52 coolbox kernel: Stack: May 19 21:26:52 coolbox kernel: f9696f25 d03cfc28 d03cfd80 d03cfc98 f96970e2 f29e2c2c fffffff4 00040002 May 19 21:26:52 coolbox kernel: f519a40c f9695c16 f29e2c64 f50135c0 00040001 00000002 00000002 d03cfcd0 May 19 21:26:52 coolbox kernel: f519a45c f519a40c 00000000 af3e5000 d03cfc48 d03cfc9c f519a40c d03cfc98 May 19 21:26:52 coolbox kernel: Call Trace: May 19 21:26:52 coolbox kernel: [<f9696f25>] ? ttm_mem_reg_iounmap+0x35/0x70 [ttm] May 19 21:26:52 coolbox kernel: [<f96970e2>] ? ttm_bo_move_memcpy+0x182/0x310 [ttm] May 19 21:26:52 coolbox kernel: [<f9695c16>] ? ttm_bo_mem_space+0x306/0x3a0 [ttm] May 19 21:26:52 coolbox kernel: [<f97f4fb0>] ? radeon_bo_move+0xe0/0x330 [radeon] May 19 21:26:52 coolbox kernel: [<f96944d5>] ? ttm_bo_reserve_locked+0xa5/0x120 [ttm] May 19 21:26:52 coolbox kernel: [<f97f4ed0>] ? radeon_bo_move+0x0/0x330 [radeon] May 19 21:26:52 coolbox kernel: [<f9694e15>] ? ttm_bo_handle_move_mem+0x135/0x330 [ttm] May 19 21:26:52 coolbox kernel: [<f9695ddc>] ? ttm_bo_move_buffer+0x12c/0x140 [ttm] May 19 21:26:52 coolbox kernel: [<f9695e86>] ? ttm_bo_validate+0x96/0x120 [ttm] May 19 21:26:52 coolbox kernel: [<f97f5f5a>] ? radeon_bo_list_validate+0x5a/0xe0 [radeon] May 19 21:26:52 coolbox kernel: [<f980d14c>] ? radeon_cs_ioctl+0x7c/0x1a0 [radeon] May 19 21:26:52 coolbox kernel: [<c0206466>] ? prepare_for_delete_or_cut+0x3c6/0x650 May 19 21:26:52 coolbox kernel: [<f96b3b51>] ? drm_ioctl+0x191/0x380 [drm] May 19 21:26:52 coolbox kernel: [<c0206466>] ? prepare_for_delete_or_cut+0x3c6/0x650 May 19 21:26:52 coolbox kernel: [<f980d0d0>] ? radeon_cs_ioctl+0x0/0x1a0 [radeon] May 19 21:26:52 coolbox kernel: [<c018ccf8>] ? handle_pte_fault+0x88/0x630 May 19 21:26:52 coolbox kernel: [<c026006f>] ? prio_tree_insert+0x12f/0x250 May 19 21:26:52 coolbox kernel: [<f96b39c0>] ? drm_ioctl+0x0/0x380 [drm] May 19 21:26:52 coolbox kernel: [<c01b1edf>] ? do_vfs_ioctl+0x7f/0x590 May 19 21:26:52 coolbox kernel: [<c011df35>] ? do_page_fault+0x185/0x3a0 May 19 21:26:52 coolbox kernel: [<c0190bae>] ? mmap_region+0x16e/0x440 May 19 21:26:52 coolbox kernel: [<c01351d5>] ? irq_exit+0x35/0x70 May 19 21:26:52 coolbox kernel: [<c01b242d>] ? sys_ioctl+0x3d/0x70 May 19 21:26:52 coolbox kernel: [<c0206466>] ? prepare_for_delete_or_cut+0x3c6/0x650 May 19 21:26:52 coolbox kernel: [<c03979a1>] ? syscall_call+0x7/0xb May 19 21:26:52 coolbox kernel: [<c0206466>] ? prepare_for_delete_or_cut+0x3c6/0x650 May 19 21:26:52 coolbox kernel: [<c0206466>] ? prepare_for_delete_or_cut+0x3c6/0x650 May 19 21:26:52 coolbox kernel: Code: 00 00 00 66 31 c0 83 c8 01 89 47 50 eb 9f 90 8d 74 26 00 89 da 89 f0 e8 0f cb ff ff 85 c0 74 a4 89 c5 eb b2 8d b4 26 00 00 00 00 <80> 78 3d 00 74 03 31 c0 c3 84 d2 75 0a 83 c0 28 e8 db f5 cf c6 May 19 21:26:52 coolbox kernel: EIP: [<f9696a50>] ttm_mem_io_lock+0x0/0x20 [ttm] SS:ESP 0068:d03cfbf0 May 19 21:26:52 coolbox kernel: CR2: 00000000b892a45d May 19 21:26:52 coolbox kernel: ---[ end trace 70c887d309b00b2d ]--- May 19 21:27:18 coolbox kernel: Emergency Sync complete May 19 21:27:21 coolbox kernel: Emergency Sync complete -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 12

[Bug 37474] New: Segmentation Fault in glCopyTexSubImage2D
by bugzilla-daemon＠freedesktop.org 30 Jan '18

30 Jan '18

https://bugs.freedesktop.org/show_bug.cgi?id=37474 Summary: Segmentation Fault in glCopyTexSubImage2D Product: Mesa Version: 7.10 Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r128 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: asguthrie(a)gmail.com Created an attachment (id=47011) --> (https://bugs.freedesktop.org/attachment.cgi?id=47011) stracktrace projectM-pulseaudio seg faults whilst calling glCopyTextSubImage2D. stacktrace attached. patch inspired by bug #27652 also attached. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 29322] New: Software rendering with UMS on radeon 9000 AGP (rv250)
by bugzilla-daemon＠freedesktop.org 03 Nov '17

03 Nov '17

https://bugs.freedesktop.org/show_bug.cgi?id=29322 Summary: Software rendering with UMS on radeon 9000 AGP (rv250) Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: support.intranet(a)libero.it Created an attachment (id=37460) --> (https://bugs.freedesktop.org/attachment.cgi?id=37460) dmesg Booting with radeon.modeset=0 (kernel 2.6.34.1) makes every 3D app (except from glxgears and OpenBVE so far) run in software rendering, at about 0.2 fps. With KMS 3d works in hardware, but is very sluggish (together with 2D). This happens with mesa 7.7 through git. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[Bug 37696] New: [RADEON:KMS:PLL] frequent colored lines appear on screen
by bugzilla-daemon＠freedesktop.org 17 Oct '17

17 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=37696 Summary: [RADEON:KMS:PLL] frequent colored lines appear on screen Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: roysjosh(a)gmail.com Hello, I'm back again! This bug is about the same hardware as in https://bugs.freedesktop.org/show_bug.cgi?id=19960 . ASUS monitor VH226H, ASUS motherboard M3A78-E, HD3200 (rs780). 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3200 Graphics [1002:9610] (prog-if 00 [VGA controller]) I just upgraded from f14 to f15 (2.6.38.6-27.fc15.x86_64) and some frequently occurring but not frequent in number colored lines have appeared on my screen... they don't necessarily go all the way across the screen either. I grabbed the "good" registers from bug 19960 and diff'd them to the current regs: [...] 258c258 < 00000404 00000002 (2) --- > 00000404 00000003 (3) 269c269 < 00000430 00910032 (9502770) --- > 00000430 00da0030 (14286896) 275c275 < 00000448 159ec704 (362727172) --- > 00000448 1593a704 (361998084) 278c278 < 00000454 6c012003 (1812013059) --- > 00000454 6c010003 (1812004867) [...] Settings these regs gets rid of the red/white/blue/etc lines: # ./avivotool regset 0x404 0x2 ; ./avivotool regset 0x430 0x910032 OLD: 0x404 (0404) 0x00000003 (3) NEW: 0x404 (0404) 0x00000002 (2) OLD: 0x430 (0430) 0x00da0030 (14286896) NEW: 0x430 (0430) 0x00910032 (9502770) And 0x43c was already set to 7: # ./avivotool regmatch 0x43c 0x43c 0x00000007 (7) Thanks! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 29725] New: EXT_framebuffer_object extension with free radeon driver
by bugzilla-daemon＠freedesktop.org 08 Oct '17

08 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=29725 Summary: EXT_framebuffer_object extension with free radeon driver Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bioinfornatics(a)gmail.com hi, i am fedora packager and i package this game: http://os.wildfiregames.com/ i see for radeon driver a crash because with EXT_framebuffer_object extension with free radeon driver. beta rpm can be found here: http://koji.fedoraproject.org/koji/taskinfo?taskID=2415654 rpm -qa | grep mesa mesa-dri-drivers-7.8.1-8.fc13.x86_64 mesa-libGL-devel-7.8.1-8.fc13.x86_64 mesa-libGL-7.8.1-8.fc13.x86_64 mesa-debuginfo-7.8.1-8.fc13.x86_64 mesa-libGLU-devel-7.8.1-8.fc13.x86_64 mesa-libGLU-7.8.1-8.fc13.x86_64 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

[Bug 37724] New: occlusion queries are messed up in ut2004 (regression, bisected)
by bugzilla-daemon＠freedesktop.org 11 Mar '17

11 Mar '17

https://bugs.freedesktop.org/show_bug.cgi?id=37724 Summary: occlusion queries are messed up in ut2004 (regression, bisected) Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com The majority of the 3d objects disappear periodically since this commit: f76787b3eae3f0b8af839fabfb24b57715a017f6 is the first bad commit commit f76787b3eae3f0b8af839fabfb24b57715a017f6 Author: Marek Olšák <maraeo(a)gmail.com> Date: Sun May 29 04:36:36 2011 +0200 r300g: fix occlusion queries when depth test is disabled or zbuffer is missing From now on, depth test is always enabled in hardware. If depth test is disabled in Gallium, the hardware Z function is set to ALWAYS. If there is no zbuffer set, the colorbuffer0 memory is set as a zbuffer to silence the CS checker. This fixes piglit: - occlusion-query-discard - NV_conditional_render/bitmap - NV_conditional_render/drawpixels - NV_conditional_render/vertex_array :040000 040000 baeff41ffed8952cbb1666d04941c6d5d01ca4fc cdb64f4b684804b818df4b65c04109eaad568e11 M src -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 22

[Bug 34643] New: ut2004/doom3 looping in submenu on r300g/PageFlip
by bugzilla-daemon＠freedesktop.org 19 Mar '16

19 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=34643 Summary: ut2004/doom3 looping in submenu on r300g/PageFlip Product: Mesa Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: krzysztof.krakowiak(a)gmail.com Created an attachment (id=43736) --> (https://bugs.freedesktop.org/attachment.cgi?id=43736) gdb/ut2k4 output and backraces. ut2004(32/64bit) and doom3(32bit) are looping everytime in submenu on r300g/PageFlip. I believe that bug occured during last two weeks, but bisecting would be hard, because I was bisecting for: https://bugs.freedesktop.org/show_bug.cgi?id=34418 And everytime supertuxkart wasnt working, ut2k4 also and vice versa, altough bugs were definitely different. Now previous bug is fixed(which affected only 64bit apps), but ut2004/doom3 got very similar behaviour(like looped video tape or something, moving forward and back), similar spam in console, but a bit different at output. Disabling PageFLip fixes this problem definitely, but I was happpy pflip user from a long time. Kernel is fresh D-R-T, DDX/DRM/Mesa from master. --- UT2004 dmesg --- [...] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [...] --- EOF UT2004 dmesg --- --- UT2004 gdb output/backtrace --- [...] [Thread 0x7fffe50cd700 (LWP 5934) exited] [New Thread 0x7fffe50cd700 (LWP 5935)] [Thread 0x7fffe50cd700 (LWP 5935) exited] [New Thread 0x7fffe50cd700 (LWP 5936)] [...] [Thread 0x7fffe50cd700 (LWP 6540) exited] [New Thread 0x7fffe50cd700 (LWP 6541)] radeon: The kernel rejected CS, see dmesg for more information. [Thread 0x7fffe50cd700 (LWP 6541) exited] [...] Program received signal SIGINT, Interrupt. 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 #1 0x00007ffff65eac6a in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007ffff65ec2ff in xcb_wait_for_reply () from /usr/lib64/libxcb.so.1 #3 0x00007ffff684392d in _XReply () from /usr/lib64/libX11.so.6 #4 0x00007fffe6c1748c in DRI2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #5 0x00007fffe6c14bf9 in dri2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #6 0x00007fffe56de4d8 in dri2_allocate_textures () from /opt/xorg/lib64/dri/gallium/r300_dri.so #7 0x00007fffe56dfb77 in dri_st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #8 0x00007fffe573f132 in st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #9 0x00007fffe5740916 in st_manager_validate_framebuffers () from /opt/xorg/lib64/dri/gallium/r300_dri.so #10 0x00007fffe58e3c1e in st_validate_state () from /opt/xorg/lib64/dri/gallium/r300_dri.so #11 0x00007fffe58ebb3a in st_Clear () from /opt/xorg/lib64/dri/gallium/r300_dri.so #12 0x0000000000d291d9 in FOpenGLRenderInterface::Clear(int, FColor, int, float, int, unsigned int) () #13 0x000000000069d234 in UGameEngine::Draw(UViewport*, int, unsigned char*, int*) () #14 0x0000000000d1d106 in USDLViewport::Repaint(int) () #15 0x0000000000d1ab09 in USDLClient::Tick() () #16 0x00000000006a0f54 in UGameEngine::Tick(float) () #17 0x000000000053d2a3 in CMainLoop::RunLoop() () #18 0x000000000053344f in ?? () #19 0x000000000052f1a0 in main () --- UT2004 gdb output/backtrace --- --- Doom3 output --- [...] radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information [...] --- EOF Doom3 output --- TIP: For full logs, look into attachements (but nothing special in xorg.log) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

← Newer
1
...
5
6
7
8
9
10
11
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2011