dri-devel February 2012

dri-devel@lists.freedesktop.org

114 participants
627 discussions

[Bug 30325] New: video=1280x720@50 no longer works
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=30325 Summary: video=1280x720@50 no longer works Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: marius.groeger(a)web.de With the current drm-radeon-testing my grub cmdline option video=1280x720@50 no longer works (RS780, output to LCD TV via HDMI). The fbcon apparently is enabled, but the TV doen't get a displayable picture anymore. Booting with d-r-t from 6 weeks ago works and correctly uses the EDID reported 1280x720@50 mode. I did ask the same thing on the dri-devel mailing list and received no answer so I'm filing this bug both as another humble nudge to the authors of the drm video= code, and as a more persistent reminder of the issue. Thanks Marius -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 30227] New: Radom X.org freeze by a GPU lockup
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=30227 Summary: Radom X.org freeze by a GPU lockup Product: DRI Version: XOrg CVS Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: kronat(a)tiscali.it Created an attachment (id=38743) --> (https://bugs.freedesktop.org/attachment.cgi?id=38743) dmesg after the fail Apparently random GPU lockup (ati r300), with X.org freeze. It happens more frequently if I compile and I switch over many applications (firefox, terminal, opera). Attached there is the dmesg after the fail (I could continue to work on others console - ctrl+alt+f1,2,3..). -- 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 29941] New: radeon/KMS: Screen hotplugging does not work any more
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29941 Summary: radeon/KMS: Screen hotplugging does not work any more Product: DRI Version: DRI CVS 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: direx(a)betriebsdirektor.de I noticed that in recent kernel versions the runtime detection of newly added monitors does not work properly. When I plug in my TV (DVI2HDMI) after booting I cannot enable it. xrandr correctly shows a new screen and I can even enable the output, but the TV screen stays black. Restarting X does not help. The driver also seems to recognize the port status after plugging it in (/sys/class/drm/card0-DVI-I-2/status) changes from "disconnected" to "connected". When I plug the HDMI cable in _before_ booting my computer the TV works just fine. GFX: Radeon HD 3870 Linux: 2.6-git (issue appeared in 2.6.35) with KMS Mesa: git libdrm: git xf86-video-ati: 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 8

[Bug 29787] New: random XRandR failures (i2c related?)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29787 Summary: random XRandR failures (i2c related?) Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aelschuring(a)hotmail.com A few weeks ago, X started displaying weird errors during normal use. These range from simple output resets to application crashes due to X BadAlloc responses. In detail, this is what I see happening: - output blink. Usually the screen goes dark for about a second. When the screen returns, I see either: - display position getting cancelled (xrandr --pos 0x0) on my left screen when this happens I can usually get it back to the correct position via the xrandr command line tool, but sometimes that triggers a WM crash - display rotation getting cancelled (xrandr --rotate normal) on the right screen. When this happens: - quodlibet (python-gtk app) crashing with BadAlloc (serial 255 error_code 11 request_code 53 minor_code 0). It will keep crashing like this until I restart X - whatever other app I had running on the right screen has disappeared as well - window manager (e17) crashing. It can recover succesfully, though - when I re-enable screen rotation, the display gets completely garbled I have started seeing this happen with 2.6.35-rc3 (was running 2.6.34-rc6 before that), and with 2.6.35.1 this happens a lot less frequently (from once a day to twice in a week). >From the latest crash, I can give the following info from xsession-errors: (E17 init) E17 INIT: XINERAMA CHOSEN: [1], 1080x1920+1280+0 E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+896 (output blinking starts) E17 INIT: XINERAMA SCREEN: [0], 1280x1024+0+0 E17 INIT: XINERAMA CHOSEN: [153045780], 0x153045764+0+153046580 (e17 crash, try to recover) E17 INIT: XINERAMA CHOSEN: [1], 1920x1080+1280+0 E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+0 (rotation lost on [1], position lost on [0]) E17 INIT: XINERAMA CHOSEN: [1], 1080x1920+1280+0 E17 INIT: XINERAMA CHOSEN: [141138596], 0x141138580+0+141139396 E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+896 (restoring rotation confuses E17) ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 6 requests ago: file nsX11ErrorHandler.cpp, line 182 UNKNOWN [/usr/lib/xulrunner-1.9.2/libxul.so +0x001CA781] (firefox crashing) Now, the reason for the E17 crash looks like a use-after-free bug. Question is: who is freeing the Xinerama structures, and why are they freed at all? I never had these problems before, and when using stock 2.6.32 (from Debian) I don't have these problems either, so I'm ruling out hardware failure. I can see the following lines logged by the kernel (KMS enabled on radeon 9550): [12045.280155] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [13500.386132] [drm:radeon_vga_detect] *ERROR* VGA-1: probed a monitor but no|invalid EDID [13797.568760] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID And I believe these are harmless (and reported in #27708). I can see these messages being reported for as long my kernel logs go back. But when the crashes occur, they are followed by these lines: [35753.097508] i2c i2c-1: sendbytes: NAK bailout. [35762.752866] i2c i2c-1: sendbytes: NAK bailout. [35772.912023] i2c i2c-1: readbytes: ack/nak timeout Which I believe are not so harmless. Or they could be a red herring, I'm not qualified to tell. Since the same time, I've been seeing a lot of lines logged by g-s-d, like gdk_pixbuf_format_get_name: assertion `format != NULL' failed But I do not believe these are relevant. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 21

[Bug 29579] New: 2.6.35 with RV630 AGP does not enable KMS/DRM
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29579 Summary: 2.6.35 with RV630 AGP does not enable KMS/DRM Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: juho-mikko.pellinen(a)lut.fi Created an attachment (id=37860) --> (https://bugs.freedesktop.org/attachment.cgi?id=37860) 2.6.35 Xorg.0.log with radeon.modeset=0 I'm having problems with getting KMS to work with 2.6.35. I have earlier configuration with 2.6.34 and KMS works as it should. When booting up I get framebuffer console and X starts without errors. Steps to reproduce: 1. copy working config from 2.6.34 to 2.6.35 2. make oldconfig and double check the differing options, none related to drm/radeon 3. compile kernel, boot it with different configurations 4. drm does not initialize, framebuffer console does not came up, X can't open dri 6. If I boot with radeon.modeset=0 drm initializes. I have tried number of kernel configs without any success. Prior to this I consulted #radeon, but it couldn't find any problems with my configuration. Normally I compile things as modules and it works quite well. AGP-drivers are compiled as modules/in kernel and load before radeon/drm. I have tried 2.6.35 vanilla, -rc2, -rc4, -rc6, -rc6, -gentoo-r1 . They all fail the same way. Any ideas how to get KMS working again? My hardware: RV630 AGP (HD2600 Pro AGP) nForce3 chipset CPU Athlon64 3xxx+ lscpi: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: ATI Technologies Inc RV630 PRO AGP [Radeon HD 2600 PRO AGP] 02:06.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) 02:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) 02:07.1 Input device controller: Creative Labs SB Audigy Game Port (rev 03) 02:07.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port 02:08.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 33

[Bug 29445] New: Linux 2.6.34 kernel Radeon KMS driver freezes my computer sometimes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29445 Summary: Linux 2.6.34 kernel Radeon KMS driver freezes my computer sometimes Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 0453411800(a)netti.fi Created an attachment (id=37682) --> (https://bugs.freedesktop.org/attachment.cgi?id=37682) /var/log/dmesg I use the kernel radeon driver with a Radeon Mobility R300 on a Toshiba laptop. The driver in 2.6.32 works fine and also the non-KMS driver in 2.6.34. However, when I enable the KMS driver (and disable the framebuffer drivers) in the 2.6.34 kernel, my computer freezes after a while of using X. If I don't start X the new KMS driver works fine. The outputs of dmesg, Xorg.0.log, and glxinfo are attached separately. In the case when I collected the above output, the bug manifested when I changed back to the virtual desktop of a running audio application (foobar2000 under wine). Access to the USB port with an external hard disk died at that moment. Usually the entire computer freezes (including keyboard, mouse, etc), but sometimes the bug seems to just disable the USB system. It only happens when the KMS driver is active so I file the bug here and not at the USB system or elsewhere. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 29217] New: After pm-suspend the second monitor shows garbled output on evergreen card (kms)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29217 Summary: After pm-suspend the second monitor shows garbled output on evergreen card (kms) Product: DRI Version: DRI CVS 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: bugs.xorg(a)boris64.net Created an attachment (id=37311) --> (https://bugs.freedesktop.org/attachment.cgi?id=37311) digicam picture of both monitors After resuming a previous (via pm-suspend) suspended system the second monitor only shows a garbled picture. Running xrandr to switch resolution seems to work, but the picture still ist truncated. This is a kms/multihead configuration. Used software: Kernel-2.6.35-rc5 latest xf86-video-ati from git latest libdrm from git latest mesa from 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 14

[Bug 29095] New: RC410: 3D apps do not run after upgrade to 2.6.35-rc5
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29095 Summary: RC410: 3D apps do not run after upgrade to 2.6.35-rc5 Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: tstellar(a)gmail.com Created an attachment (id=37103) --> (https://bugs.freedesktop.org/attachment.cgi?id=37103) Output from glxgears with RADEON_DEBUG=all I just upgraded from 2.6.33 to 2.6.35-rc5, and whenever I try to run glxgears or any of the mesa demos only a black window is displayed. There is nothing interesting in my dmesg log. I am using the latest git versions of libdrm, mesa, xf86-video-ati, and X server 1.8.1.902. My card is a Radeon Xpress 200M IGP (RC410) I can give bisecting the kernel a try, but first I wanted to see if anyone had any ideas about what might be wrong. Previously, I was running a patched version of 2.6.33 to work around this bug: https://bugzilla.kernel.org/show_bug.cgi?id=15626 . The fix for this bug made it into one of the 2.6.35-rc* releases. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 11

[Bug 29026] New: r600: Garbled screen after resuming from suspend (KMS)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29026 Summary: r600: Garbled screen after resuming from suspend (KMS) Product: DRI Version: DRI CVS 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: direx(a)betriebsdirektor.de Created an attachment (id=36970) --> (https://bugs.freedesktop.org/attachment.cgi?id=36970) system log Using mesa-git, libdrm-git and xf86-video-ati-git I always get a garbled screen (including framebuffer console) after resume. I took a screenshot, but obviously it looks normal. Video card: Radeon HD3870 Kernel: Linux-git (2.6.35-rc4+), KMS enabled by default There is no crash or lockup, it's just sort of impossible to read anything on the screen after resuming. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 29001] New: latest d-r-t has regular X crashes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29001 Summary: latest d-r-t has regular X crashes Product: DRI Version: XOrg CVS 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: aidan(a)cisco.com after updating to latest d-r-t, X crashes regularly, often just by starting firefox and waiting for it to restore all the previous open tabs. xorg-server 1.8.1.902 git libdrm/mesa/ddx kde 4.4.5 on rv790. Backtrace: [ 33638.299] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1358] [ 33638.299] 1: /usr/bin/X (0x400000+0x636f9) [0x4636f9] [ 33638.299] 2: /lib/libpthread.so.0 (0x7fc9ad310000+0xf120) [0x7fc9ad31f120] [ 33638.299] 3: /usr/lib/libpixman-1.so.0 (0x7fc9ac3a6000+0x3ce53) [0x7fc9ac3e2e53] [ 33638.299] 4: /usr/lib/libpixman-1.so.0 (0x7fc9ac3a6000+0x31091) [0x7fc9ac3d7091] [ 33638.299] 5: /usr/lib/libpixman-1.so.0 (pixman_image_composite32+0xfe3) [0x7fc9ac3d91c3] [ 33638.299] 6: /usr/lib64/xorg/modules/libfb.so (fbComposite+0x225) [0x7fc9a99ad8b5] [ 33638.299] 7: /usr/lib64/xorg/modules/libexa.so (0x7fc9a9780000+0x10701) [0x7fc9a9790701] [ 33638.299] 8: /usr/lib64/xorg/modules/libexa.so (0x7fc9a9780000+0xe15e) [0x7fc9a978e15e] [ 33638.299] 9: /usr/bin/X (0x400000+0xd4b80) [0x4d4b80] [ 33638.299] 10: /usr/bin/X (0x400000+0xce2ad) [0x4ce2ad] [ 33638.300] 11: /usr/bin/X (0x400000+0x2f5ec) [0x42f5ec] [ 33638.300] 12: /usr/bin/X (0x400000+0x24de5) [0x424de5] [ 33638.300] 13: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fc9ab9dbbbd] [ 33638.300] 14: /usr/bin/X (0x400000+0x24999) [0x424999] [ 33638.300] Bus error at address 0x7fc99fb86b04 [ 33638.300] Fatal server error: [ 33638.300] Caught signal 7 (Bus error). Server aborting [ 33638.300] [ 33638.300] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

← Newer
1
2
3
4
5
6
7
8
9
...
63
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2012