dri-devel April 2013

dri-devel@lists.freedesktop.org

142 participants
765 discussions

[Bug 54381] New: [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL
by bugzilla-daemon＠bugzilla.kernel.org 30 Jun '14

30 Jun '14

https://bugzilla.kernel.org/show_bug.cgi?id=54381 Summary: [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL Product: Drivers Version: 2.5 Kernel Version: 3.7.2 and up 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: rose(a)semkath.de Regression: No I'm running a 3 monitor setup with a Radeon HD graphics card [Radeon HD 6000 Series]. I'm not using the proprietary drivers. Connectors are: 2 DVI and 1 HDMI. When I change the second DVI connection from a monitor to a projector and try to set the correct resolution (1920x1080) it fails with the following error message: [15189.014994] [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL [15189.015008] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:12] It changes the resolution but there are black areas at the sides and at the bottom of the displayed picture. It only happens if I connect the projector, not when the usual monitor is connected. This problem does not exist with kernel version 3.6.11. $ scripts/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux semkath-desktop 3.8.0 #1 SMP PREEMPT Wed Feb 20 18:31:08 CET 2013 x86_64 AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux Gnu C 4.7.2 Gnu make 3.82 binutils 2.23.1 util-linux 2.22.2 mount debug module-init-tools 12 e2fsprogs 1.42.6 Linux C Library 2.16 Dynamic linker (ldd) 2.16 Procps UNKNOWN Net-tools 1.60_p20120127084908 Kbd 1.15.5 Sh-utils 8.21 Modules Loaded snd_aloop kvm_amd firewire_ohci k10temp i2c_piix4 firewire_core -- 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 18

[Bug 48357] New: Display resolutions not detected correctly after startup with VGA over DisplayPort
by bugzilla-daemon＠freedesktop.org 28 Jun '14

28 Jun '14

https://bugs.freedesktop.org/show_bug.cgi?id=48357 Bug #: 48357 Summary: Display resolutions not detected correctly after startup with VGA over DisplayPort Classification: Unclassified Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: heroeschman(a)gmx.de Created attachment 59545 --> https://bugs.freedesktop.org/attachment.cgi?id=59545 dmesg Hi. One of my monitors is a VGA LCD connected over DisplayPort. After startup not all resolutions are detected but only resolutions up to 1024x768. However if i disconnect the monitor and reconnect it again (at 287.472381 in the log file) all screen resolutions are detected correctly. The initial detection does not work and dmesg shows "[drm:radeon_dp_i2c_aux_ch], aux i2c too many retries, giving up" error messages. drm_helper_probe_single_connector_modes() then falls back and probes some modes up to 1024x768 that is why higher resolutions are missing. No idea why it works after reconnecting the monitor. dmesg log is "dmesg | grep drm" with drm.debug=0x0e from a 3.4-rc1 kernel but the problem already happend in earlier versions. The problem also happens if only the VGA monitor is connected. -- 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 34772] New: [radeon] [R300] GPU lockups with when KMS is enabled
by bugzilla-daemon＠bugzilla.kernel.org 28 Jun '14

28 Jun '14

https://bugzilla.kernel.org/show_bug.cgi?id=34772 Summary: [radeon] [R300] GPU lockups with when KMS is enabled Product: Drivers Version: 2.5 Kernel Version: 2.6.38 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: rbrito(a)ime.usp.br Regression: No Created an attachment (id=57062) --> (https://bugzilla.kernel.org/attachment.cgi?id=57062) dmesg output right after the lock up, obtained via the network Hi there. I have been getting some Oopses/stack traces when I try to use my iBook G4 (with an "ATI Technologies Inc M11 NV/FireGL Mobility T2e" card) and I enable KMS. The userland here is Debian unstable with the DRM from experimental, but I am willing to test anything that you would like me to. For example, attached is the last of a series of such Oopses that I got when I tried to test if a video was playing or not with mplayer. I tried to use 2.6.39-rc{5,6}, but upon boot I get messages telling me that there were failures and that hardware acceleration will be disabled and I that I get is a desktop with colors distorted like if there were some endianness issues. This is, BTW, part of my attempts to get Linux running well on PowerPC, with some of my logs (with photos) present at my homepage: http://www.ime.usp.br/~rbrito/linux/debug-r300/ Please, if there is anything that I can provide to fix this, let me know and I will do my best. Thanks, Rogério Brito. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 25

[Bug 42603] New: Watching video with radeon oss driver sometimes leads to kernel panic
by bugzilla-daemon＠bugzilla.kernel.org 26 Jun '14

26 Jun '14

https://bugzilla.kernel.org/show_bug.cgi?id=42603 Summary: Watching video with radeon oss driver sometimes leads to kernel panic Product: Drivers Version: 2.5 Kernel Version: 3.0.17 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: bugzilla.kernel.org(a)boris64.net Regression: No Created an attachment (id=72119) --> (https://bugzilla.kernel.org/attachment.cgi?id=72119) picture of panic Watching video (mostly flashvideo and dvb-s/c in kaffeine) sometimes leads to kernel panic with the radeon oss driver. This is somehow not reproducable, but happens about once a week. It happens for quite some time (1/2 a year?) now, also happened on older kernels, actually since i own this card... Attached is a screenshot of the panic. Used software: kernel-3.0.17 xorg-server-1.11.3 mesa+xf86-video-radeon: latest git snapshot(s) -- 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 2

[Bug 42616] New: Radeon Kernel Mode Setting sets wrong mode
by bugzilla-daemon＠bugzilla.kernel.org 26 Jun '14

26 Jun '14

https://bugzilla.kernel.org/show_bug.cgi?id=42616 Summary: Radeon Kernel Mode Setting sets wrong mode 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: thomas.jones(a)utoronto.ca Regression: No I have a Radeon HD 3470, connected to a Dell P2010H monitor via Display Port. The monitor's native resolution is 1600x900, and everything works correctly with UMS, however if I use KMS I cannot use that mode, I can use at least 1024x768, 1280x1024, and 1152x864 with KMS, but no matter how I try I cannot get it to work in 1600x900. I have tried with the CVT timings, (reduced blanking and not) and with the ones provided in the monitor's EDID. If I attempt to set any of those modes (the 1600x900) with KMS on the monitor claims that I'm using an unsupported mode. UMS works just fine though. I'm running Fedora, and I don't think this is a regression in the kernel since I don't think this computer has ever worked with KMS. Right now what I've done is I have set the kernel command line to boot with 1152x864 and KMS, then I tried to use xrandr to change modes and the monitor just complained. dmesg doesn't seem to have anything useful to say, and neither does Xorg.0.log -- 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 8

[Bug 44800] New: Radeon HD 6450 CAICOS screen corruption and kernel crashes
by bugzilla-daemon＠freedesktop.org 16 Jun '14

16 Jun '14

https://bugs.freedesktop.org/show_bug.cgi?id=44800 Bug #: 44800 Summary: Radeon HD 6450 CAICOS screen corruption and kernel crashes Classification: Unclassified Product: DRI Version: unspecified 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: marko.kohtala(a)gmail.com Created attachment 55597 --> https://bugs.freedesktop.org/attachment.cgi?id=55597 Artefacts in X I got Radeon HD 6450 1GB DDR3 last fall and have been unable to use it. I currently run fairly recent 32-bit Debian versions on top of 64-bit vanilla kernel 3.2.1 (currently with minor patch to makefile and a debug output patch https://bugs.freedesktop.org/attachment.cgi?id=53428). I've tried with 32-bit kernel and some older kernels without noticing any difference. I've tried installing Windows and ran some OpenCL tests. All worked fine so I'd expect the hardware is working correctly. I tried if kernel options iomem=off mem=2G would help. They did not help. mem=2G was needed because jmicron driver for ATA failed without iomem. I attach some more files I collected while trying if it has gotten fixed. Now I'm back to running a loaned nVidia card to be able to report 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 16

[Bug 31565] New: [r300] radeon_texture.c:136: radeon_teximage_map: Assertion `!image->base.Data' failed.
by bugzilla-daemon＠freedesktop.org 24 May '14

24 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=31565 Summary: [r300] radeon_texture.c:136: radeon_teximage_map: Assertion `!image->base.Data' failed. Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: vlee(a)vmware.com mesa: d18df9e336b5d2e68a4a6185f7b9d0d0c095c3c4 (master) chipset: RV530 71C5 (ATI Radeon X1600) system architecture: i686 libdrm-dev: 2.4.21-1ubuntu2.1 kernel version: 2.6.35-22-generic Linux distribution: Ubuntu 10.10 i386 Machine model: iMac4,1 Run piglit fbo-blit. $ ./bin/fbo-blit ... radeonSetSpanFunctions: bad format: 0x0002 radeonSetSpanFunctions: bad format: 0x0002 fbo-blit: radeon_texture.c:136: radeon_teximage_map: Assertion `!image->base.Data' failed. (gdb) bt #0 0x0020c416 in __kernel_vsyscall () #1 0x00354941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0x00357e42 in abort () at abort.c:92 #3 0x0034d8e8 in __assert_fail (assertion=0x1123ce5 "!image->base.Data", file=0x1123cb6 "radeon_texture.c", line=136, function=0x1123f06 "radeon_teximage_map") at assert.c:81 #4 0x00f2fb0f in radeon_teximage_map (image=0x9884200, write_enable=1 '\001') at radeon_texture.c:136 #5 0x00f22fb0 in radeon_map_unmap_framebuffer (ctx=<value optimized out>, fb=0x9884350, map=1 '\001') at radeon_span.c:1047 #6 0x00f2ebc4 in radeonSpanRenderStart (ctx=0x9526458) at radeon_span.c:1085 #7 0x01027253 in swrast_render_start (ctx=0x9526458, x=10, y=10, width=10, height=10, format=6407, type=5126, packing=0x9535108, pixels=0x98b7508) at swrast/s_context.h:268 #8 _swrast_ReadPixels (ctx=0x9526458, x=10, y=10, width=10, height=10, format=6407, type=5126, packing=0x9535108, pixels=0x98b7508) at swrast/s_readpix.c:473 #9 0x00f2176d in radeonReadPixels (ctx=0x9526458, x=10, y=10, width=10, height=10, format=6407, type=5126, pack=0x9535108, pixels=0x98b7508) at radeon_pixel_read.c:221 #10 0x00f9a58b in _mesa_ReadPixels (x=10, y=10, width=10, height=10, format=6407, type=5126, pixels=0x98b7508) at main/readpix.c:232 #11 0x0804b53e in piglit_probe_rect_rgb (x=10, y=10, w=10, h=10, expected=0xbfde7a00) at piglit/tests/util/piglit-util.c:278 #12 0x0804a890 in verify_color_rect (start_x=10, start_y=10, w=20, h=20) at /piglit/tests/fbo/fbo-blit.c:110 #13 0x0804ae31 in run_test () at piglit/tests/fbo/fbo-blit.c:193 #14 0x0804aeb6 in piglit_display () at /piglit/tests/fbo/fbo-blit.c:206 #15 0x0804ce7b in display () at piglit/tests/util/piglit-framework.c:52 #16 0x00d79820 in fghRedrawWindow (window=0x9509050, enumerator=0xbfde7b68) at freeglut_main.c:210 #17 fghcbDisplayWindow (window=0x9509050, enumerator=0xbfde7b68) at freeglut_main.c:227 #18 0x00d7d660 in fgEnumWindows (enumCallback=0xd79790 <fghcbDisplayWindow>, enumerator=0xbfde7b68) at freeglut_structure.c:394 #19 0x00d79cdb in fghDisplayAll () at freeglut_main.c:249 #20 glutMainLoopEvent () at freeglut_main.c:1450 #21 0x00d7a605 in glutMainLoop () at freeglut_main.c:1498 #22 0x0804d024 in main (argc=1, argv=0xbfde7df4) at piglit/tests/util/piglit-framework.c:118 (gdb) frame 4 #4 0x00f2fb0f in radeon_teximage_map (image=0x9884200, write_enable=1 '\001') at radeon_texture.c:136 136 assert(!image->base.Data); (gdb) l 131 radeon_print(RADEON_TEXTURE, RADEON_VERBOSE, 132 "%s(img %p), write_enable %s.\n", 133 __func__, image, 134 write_enable ? "true": "false"); 135 if (image->mt) { 136 assert(!image->base.Data); 137 138 radeon_bo_map(image->mt->bo, write_enable); 139 teximage_set_map_data(image); 140 } (gdb) print image->base $1 = {InternalFormat = 6408, _BaseFormat = 6408, TexFormat = 2, Border = 0, Width = 64, Height = 64, Depth = 1, Width2 = 64, Height2 = 64, Depth2 = 1, WidthLog2 = 6, HeightLog2 = 6, DepthLog2 = 0, MaxLog2 = 6, WidthScale = 64, HeightScale = 64, DepthScale = 1, IsClientData = 0 '\000', _IsPowerOfTwo = 1 '\001', TexObject = 0x9884690, FetchTexelc = 0x10cfc60 <fetch_texel_float_to_chan>, FetchTexelf = 0x10c9dc0 <fetch_texel_2d_f_rgba8888_rev>, RowStride = 64, ImageOffsets = 0x9884278, Data = 0xb77cb000, DriverData = 0x0} (gdb) print image->base.Data $2 = (GLvoid *) 0xb77cb000 -- 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 36934] New: screen corruption after running a game through wine
by bugzilla-daemon＠freedesktop.org 24 May '14

24 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=36934 Summary: screen corruption after running a game through wine Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aaalmosss(a)gmail.com After running a game through wine, some graphic elements of other applications get garbled. These include window decorations, window shadows, images in already opened tabs of firefox, parts of the taskbar etc. They usually return to normal if refreshed (e.g. window shadows on resizing the window). The problem seems to occur only through wine, but I don't think its wine's fault. I use 32bit debian unstable (kde 4.4.5, compiz 8.4, xserver 7.6 (xserver-xorg-core 1.9.5)) with vanilla kernel 2.6.37.6 and wine 1.3.15 from sources. The issue appears with both the installed mesa 7.10.2 and 7.11-dev from git. I'm not sure about the product and component, just guessing... #35452 might be related, but there Michel Dänzer said that's related to page flipping, which is not in 2.6.37, and this one also happens with non-fullscreen games. -- 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 51604] New: and yet it moves: colored sparkling
by bugzilla-daemon＠freedesktop.org 24 May '14

24 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=51604 Bug #: 51604 Summary: and yet it moves: colored sparkling 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 They are on some rocks in episode 1, on all level exits, but most apparent on the tree joints in episode 2. Upon startup this is printed: Mesa: User error: GL_INVALID_OPERATION in glUniform(program not linked) BTW is it normal that it almost always segfaults on startup? The backtrace is different each time (64 bit). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 58839] New: errors about too many fences printed while playing neverball
by bugzilla-daemon＠freedesktop.org 24 May '14

24 May '14

https://bugs.freedesktop.org/show_bug.cgi?id=58839 Priority: medium Bug ID: 58839 Assignee: dri-devel(a)lists.freedesktop.org Summary: errors about too many fences printed while playing neverball Severity: normal Classification: Unclassified OS: All Reporter: aaalmosss(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa This is printed in mass quantities: EE r600_pipe.c:80 r600_create_fence - r600: too many concurrent fences They don't cause any visible rendering error though. -- You are receiving this mail because: You are the assignee for the bug.

1 8

← Newer
1
...
29
30
31
32
33
34
35
...
77
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2013