dri-devel February 2013

dri-devel@lists.freedesktop.org

130 participants
696 discussions

[Bug 53511] New: r600g llvm backend doesn't support indirect addressing
by bugzilla-daemon＠freedesktop.org 19 Aug '13

19 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=53511 Bug #: 53511 Summary: r600g llvm backend doesn't support indirect addressing Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com According to the warning message it falls back to the TGSI backend. I have seen the warning with Sauerbraten, Unigine Tropics, and Stalker: SoC with Wine (full dynamic lighting). -- 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

[Bug 54143] New: Error when running GLSL_deferred
by bugzilla-daemon＠freedesktop.org 09 Aug '13

09 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=54143 Bug #: 54143 Summary: Error when running GLSL_deferred Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: alexandre.f.demers(a)gmail.com Download and compile GLSL_deferred from http://www.autistici.org/encelo/prog_gldemos.php Mesa: User error: GL_INVALID_VALUE in glDisableVertexAttribArrayARB(index) EE r600_shader.c:1700 r600_shader_from_tgsi - GPR limit exceeded - shader requires 147 registers EE r600_shader.c:141 r600_pipe_shader_create - translation from TGSI failed ! EE r600_state_common.c:738 r600_shader_select - Failed to build shader variant (type=1, key=0) -12 With mesa git f9767dac9a06aad93a9d61d108055ad673498bf8 drm git 7080bfdfd9b6c5f003daaef37ae9c329f2d46a6c kernel 3.6.0-rc2 Using HD6950 -- 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

[Bug 43655] New: Latest radeon dri driver on HD6950 with kernel 3.2 flickers
by bugzilla-daemon＠freedesktop.org 09 Aug '13

09 Aug '13

https://bugs.freedesktop.org/show_bug.cgi?id=43655 Bug #: 43655 Summary: Latest radeon dri driver on HD6950 with kernel 3.2 flickers Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: alexandre.f.demers(a)gmail.com My new HD6950 flickers like hell right from the initialization. Using kernel 3.1.0 is just fine, but kernels 3.2.0-rc3 and over make the screen flicker (I can't tell for versions in between for now). Also, the screen seems shifted by a bit more than half my monitor's width. I also have an integrated HD3200 and I have no problem at all when selecting this integrated chipset over my PCI-E 6950 with the same driver and kernel combinations. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 36

[Bug 57875] New: Second Life viewer bad rendering with git-ec83535
by bugzilla-daemon＠freedesktop.org 30 Jul '13

30 Jul '13

https://bugs.freedesktop.org/show_bug.cgi?id=57875 Priority: medium Bug ID: 57875 Assignee: dri-devel(a)lists.freedesktop.org Summary: Second Life viewer bad rendering with git-ec83535 Severity: normal Classification: Unclassified OS: All Reporter: andabata12(a)yahoo.it Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r300 Product: Mesa With git "HEAD at ec83535 automake/gallium: attempt to fix -lrt", Cool VL Viewer a TPV for Second Life 3D world ( the official Linden Lab viewer is from ages blocked cause of https://bugs.freedesktop.org/show_bug.cgi?id=39251 ) can set only basic shaders otherwise with atmospheric, water and reflections shaders enabled, I have extensive blue triangles during the execution. On the contrary with graphics drivers from git-54ff536 ( HyperZ enabled by default) all was right with smooth rendering, lowered cpu usage and augmented framerate ( 8-10 %). -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 59322] New: r300g MSAA breaks Half-Life 2 in Wine
by bugzilla-daemon＠freedesktop.org 30 Jul '13

30 Jul '13

https://bugs.freedesktop.org/show_bug.cgi?id=59322 Priority: medium Bug ID: 59322 Assignee: dri-devel(a)lists.freedesktop.org Summary: r300g MSAA breaks Half-Life 2 in Wine Severity: normal Classification: Unclassified OS: All Reporter: stefandoesinger(a)gmx.at Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa When MSAA is enabled in Half-Life 2 running in Wine, the window only contains garbled output. Disabling multisampling in Wine or in the game settings restores proper rendering. A complication is that the game enables 2x MSAA by default if it is available. A user not knowing this fact will think that 8ed6b140 broke the game. It also makes disabling multisampling in the game settings a challenge. Hardware info: OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV530 OpenGL version string: 2.1 Mesa 9.1-devel (git-8ed6b14) OpenGL shading language version string: 1.20 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M56P [Radeon Mobility X1600] 01:00.0 0300: 1002:71c5 -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 61182] New: r600g causes KWin crashes with kernel 3.8
by bugzilla-daemon＠freedesktop.org 24 Jul '13

24 Jul '13

https://bugs.freedesktop.org/show_bug.cgi?id=61182 Priority: medium Bug ID: 61182 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600g causes KWin crashes with kernel 3.8 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: eugene.shalygin(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Kwin crashes with current mesa and kernel 3.8. It does not crash with 3.7 kernel. With mesa 9.0.2 and kernel 3.8 kwin also works fine #5 0x0000003647c892ab in __memset_sse2 () from /lib64/libc.so.6 #6 0x00007f5a8cbf6cf3 in r600_texture_create_object (screen=0x980ca0, base=0x7fff208b4770, pitch_in_bytes_override=0, buf=0x0, surface=0x7fff208b3a80) at r600_texture.c:509 #7 0x00007f5a8cbf7339 in r600_texture_create (screen=0x980ca0, templ=0x7fff208b4770) at r600_texture.c:601 #8 0x00007f5a8cbdbae5 in r600_resource_create (screen=0x980ca0, templ=0x7fff208b4770) at r600_resource.c:37 #9 0x00007f5a8cc1b4d2 in dri2_drawable_process_buffers (drawable=0xc2b130, buffers=0x764460, buffer_count=1, atts=0x7fff208b48b0, att_count=1) at dri2.c:254 #10 0x00007f5a8cc1b9b3 in dri2_allocate_textures (drawable=0xc2b130, statts=0x7fff208b48b0, statts_count=1) at dri2.c:404 #11 0x00007f5a8cc19f0f in dri_st_framebuffer_validate (stfbi=0xc2b130, statts=0x7fff208b48b0, count=1, out=0x0) at dri_drawable.c:81 #12 0x00007f5a8cc1a30e in dri_drawable_validate_att (drawable=0xc2b130, statt=ST_ATTACHMENT_FRONT_LEFT) at dri_drawable.c:206 #13 0x00007f5a8cc1a35c in dri_set_tex_buffer2 (pDRICtx=0x8fef20, target=3553, format=8409, dPriv=0xbee5e0) at dri_drawable.c:220 #14 0x00007f5a9b82f590 in dri2_bind_tex_image (dpy=0x7d15f0, drawable=29360171, buffer=8414, attrib_list=0x0) at dri2_glx.c:1002 #15 0x00007f5a9b7f30f5 in __glXBindTexImageEXT (dpy=0x7d15f0, drawable=29360171, buffer=8414, attrib_list=0x0) at glxcmds.c:2370 #16 0x00007f5a9d1773c3 in KWin::GlxTexture::loadTexture(unsigned long const&, QSize const&, int) () from /usr/lib64/libkdeinit4_kwin.so #17 0x00007f5a9d16f175 in KWin::SceneOpenGL::Window::bindTexture() () from /usr/lib64/libkdeinit4_kwin.so #18 0x00007f5a9d175a8e in KWin::SceneOpenGL::Window::performPaint(int, QRegion, KWin::WindowPaintData) () from /usr/lib64/libkdeinit4_kwin.so #19 0x00007f5a9d16e32f in KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #20 0x00007f5a9d16e4cd in KWin::SceneOpenGL2::finalDrawWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #21 0x00007f5a9d1822b5 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #22 0x00007f5a9d16178a in KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #23 0x00007f5a9d182557 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #24 0x00007f5a9d16434d in KWin::Scene::paintWindow(KWin::Scene::Window*, int, QRegion, KWin::WindowQuadList) () from /usr/lib64/libkdeinit4_kwin.so #25 0x00007f5a9d16367f in KWin::Scene::paintSimpleScreen(int, QRegion) () from /usr/lib64/libkdeinit4_kwin.so #26 0x00007f5a9d1616ce in KWin::Scene::finalPaintScreen(int, QRegion, KWin::ScreenPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #27 0x00007f5a9d182720 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () from /usr/lib64/libkdeinit4_kwin.so #28 0x00007f5a9d162a68 in KWin::Scene::paintScreen(int*, QRegion*) () from /usr/lib64/libkdeinit4_kwin.so #29 0x00007f5a9d171fce in KWin::SceneOpenGL::paint(QRegion, QList<KWin::Toplevel*>) () from /usr/lib64/libkdeinit4_kwin.so #30 0x00007f5a9d15ceac in KWin::Compositor::performCompositing() () from /usr/lib64/libkdeinit4_kwin.so #31 0x00007f5a9d15d950 in KWin::Compositor::slotCompositingOptionsInitialized() () from /usr/lib64/libkdeinit4_kwin.so #32 0x00007f5a9afb418f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #33 0x00007f5a9ae96877 in QFutureWatcherBase::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #34 0x00007f5a9a35cd6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #35 0x00007f5a9a35eaea in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #36 0x00007f5a9cc83336 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #37 0x00007f5a9af9f06e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #38 0x00007f5a9afa2891 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #39 0x00007f5a9a3f8979 in QEventDispatcherX11::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtGui.so.4 #40 0x00007f5a9af9ddcf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #41 0x00007f5a9af9e058 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #42 0x00007f5a9afa2ba8 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #43 0x00007f5a9d113d2a in kdemain () from /usr/lib64/libkdeinit4_kwin.so #44 0x0000003647c249b5 in __libc_start_main () from /lib64/libc.so.6 #45 0x0000000000400831 in _start () Hardware: Mobility Radeon HD 5850 -- You are receiving this mail because: You are the assignee for the bug.

1 55

[Bug 59477] New: libdrm 2.4.41 build failure
by bugzilla-daemon＠freedesktop.org 23 Jul '13

23 Jul '13

https://bugs.freedesktop.org/show_bug.cgi?id=59477 Priority: medium Bug ID: 59477 Assignee: dri-devel(a)lists.freedesktop.org Summary: libdrm 2.4.41 build failure Severity: normal Classification: Unclassified OS: Linux (All) Reporter: tobias.klausmann(a)mni.thm.de Hardware: All Status: NEW Version: unspecified Component: libdrm Product: DRI Hi, libdrm 2.4.41 fails to build: Building with: ./configure --with-pic \ --enable-udev make make -C tests dristat drmstat ... [ 8s] checking for VALGRIND... yes [ 8s] configure: creating ./config.status [ 9s] config.status: creating Makefile [ 9s] config.status: creating libkms/Makefile [ 9s] config.status: creating libkms/libkms.pc [ 9s] config.status: creating intel/Makefile [ 9s] config.status: creating intel/libdrm_intel.pc [ 9s] config.status: creating radeon/Makefile [ 9s] config.status: creating radeon/libdrm_radeon.pc [ 9s] config.status: creating nouveau/Makefile [ 9s] config.status: creating nouveau/libdrm_nouveau.pc [ 9s] config.status: creating omap/Makefile [ 9s] config.status: creating omap/libdrm_omap.pc [ 9s] config.status: creating exynos/Makefile [ 9s] config.status: creating exynos/libdrm_exynos.pc [ 9s] config.status: creating tests/Makefile [ 9s] config.status: creating tests/modeprint/Makefile [ 9s] config.status: creating tests/modetest/Makefile [ 9s] config.status: creating tests/kmstest/Makefile [ 9s] config.status: creating tests/radeon/Makefile [ 9s] config.status: creating tests/vbltest/Makefile [ 9s] config.status: creating include/Makefile [ 9s] config.status: creating include/drm/Makefile [ 9s] config.status: error: cannot find input file: `man/Makefile.in' [ 9s] error: Bad exit status from /var/tmp/rpm-tmp.Swr1Ta (%build) Thanks in advance -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 42678] New: [3.3-rc1]radeon 0000:07:00.0: GPU lockup CP stall for more than 10000msec
by bugzilla-daemon＠bugzilla.kernel.org 12 Jul '13

12 Jul '13

https://bugzilla.kernel.org/show_bug.cgi?id=42678 Summary: [3.3-rc1]radeon 0000:07:00.0: GPU lockup CP stall for more than 10000msec Product: Drivers Version: 2.5 Kernel Version: 3.3-rc1 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: maciej.rutecki(a)gmail.com CC: florian(a)mickler.org, just.for.lkml(a)googlemail.com, rjw(a)sisk.pl, maciej.rutecki(a)gmail.com Regression: Yes Subject : [3.3-rc1]radeon 0000:07:00.0: GPU lockup CP stall for more than 10000msec Submitter : Torsten Kaiser <just.for.lkml(a)googlemail.com> Date : 2012-01-21 19:03 Message-ID : CAPVoSvSXMvRb=1itu9DjF+s=6zfAChvUxS-x=b8EV9kOZinNpA(a)mail.gmail.com References : http://marc.info/?l=linux-kernel&m=132717279606670&w=2 This entry is being used for tracking a regression from 3.2. Please don't close it until the problem is fixed in the mainline. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 23

[Bug 44772] New: Radeon HD6950 (Cayman): Resuming from hibernation fails sometimes
by bugzilla-daemon＠freedesktop.org 11 Jul '13

11 Jul '13

https://bugs.freedesktop.org/show_bug.cgi?id=44772 Bug #: 44772 Summary: Radeon HD6950 (Cayman): Resuming from hibernation fails sometimes Classification: Unclassified Product: DRI Version: XOrg CVS Platform: All OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: h.judt(a)gmx.at Resuming after hibernation fails sometimes. After reading the snapshot (the percentage reached 100%), the screen would switch back, but instead the monitor goes black and turns off and the complete system hangs. No ssh or sysreq keys work, everything is dead. Some things I noticed that might help: * It does not occur with nomodeset=1. * You don't need X to reproduce this, just console with modesetting enabled is enough. * It is not reproducible reliably, but the likelyness that it will occur is unfortunately not small (I'd say 3-4 out of 10 attempts). * The fastboot kernel parameter is not related to it. That is all with vanilla kernel. Now enter tuxonice, because it provides more information. Tuxonice reads the atomic copy first (20%..40%..60%..80%->100%). Now, it would switch on tuxoniceui and show the progress for reading in the caches. However, in the problem case the switch does not happen, because the system hangs as described for the vanilla kernel (no ssh, sysreq). At this point, one has to push the reset button to reboot. However, tuxonice has a nice feature: It will detect the image, and that it has resumed from this image before. It then asks the user whether he wants to try resuming from that same image again or remove the image and continue booting. If one presses 'C' to resume from the image, this time everything works and the system is fully functional. In fact, it's a 100% chance that the screen does not get black or the system freezes. The issue does not occur at certain cycles, sometimes three hibernation->resume cycles go well, then the fourth and fifth will not work, then the next four are ok and so on... So, I believe there is some issue with hardware initialization and hibernation. It might be that something does not really finish in time. What could there be wrong? This is with vanilla-3.2-rc5 and 3.2-rc7-tuxonice (see http://git.tuxonice.net/?p=tuxonice-head.git;a=summary), but I guess all 3.2-rc kernels will show the same problem. I had troubles hibernating with vanilla-3.2-final, so I could not test this. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 12

[Bug 43114] New: Can't set high engine clock for RadeonHD 6620G
by bugzilla-daemon＠bugzilla.kernel.org 04 Jul '13

04 Jul '13

https://bugzilla.kernel.org/show_bug.cgi?id=43114 Summary: Can't set high engine clock for RadeonHD 6620G Product: Drivers Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: runetmember(a)gmail.com Regression: No APU model: A8-3500M with Radeon HD 6620G. Laptop model: Acer Aspire 7560G. According to official specs of this APU http://www.amd.com/us/products/notebook/apu/mainstream/Pages/mainstream.asp… https://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units#c… GPU core clock on high profile should be 444 MHz, but even when I set high profile manually ~# cat /sys/class/drm/card0/device/power_method profile ~# cat /sys/class/drm/card0/device/power_profile high GPU core clock is not 444 MHz anyway, even below 200 MHz: ~$ cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 200000 kHz current engine clock: 7990 kHz default memory clock: 667000 kHz Maybe output of radeon_pm_info is incorrect, because change between different profiles and dynpm make no difference in radeon_pm_info information. Reproduceable with Linux 3.2 and Linux 3.4rc3. dmesg of 3.4rc3 boot process attached. Is there any additional information I need to provide? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 4

← Newer
1
...
38
39
40
41
42
43
44
...
70
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2013