dri-devel June 2011

dri-devel@lists.freedesktop.org

101 participants
499 discussions

[Bug 32556] New: screen flickers all the time with desktop image appearing only briefly
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32556 Summary: screen flickers all the time with desktop image appearing only briefly Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 3ntr0p13(a)gmail.com Created an attachment (id=41344) --> (https://bugs.freedesktop.org/attachment.cgi?id=41344) dmesg Machine is the same as in bug report 28331 although with different software components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor 4000+, this time running a 64 bits debian squeeze. The machine is a small factor desktop machine designed around laptop components, so the graphic card is an integrated radeon x1200. When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the time making the machine unusable, while with debian kernel 2.6.32-5 such "flick to black" event occur from time to time, making it annoying but usable. While booting with radeon.modeset=0 the problem doesn't exhibits itself The following packages version from debian squeeze are installed: xserver-xorg 1:7.5+8 xserver-xorg-core 2:1.7.7-10 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that machine (when booted on 2.6.37-rc6). Regards, Gildas -- 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 32422] New: Large images displayed in Firefox appear corrupted
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32422 Summary: Large images displayed in Firefox appear corrupted 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: da_fox(a)mad.scientist.com Created an attachment (id=41150) --> (https://bugs.freedesktop.org/attachment.cgi?id=41150) Picture describing a thousand words. "A picture says more than a thousand words" (aka see attachment) This is what happens when I try to view the XKCD "Online Communities 2" map (http://xkcd.com/802_large/) or other large images in firefox. -- 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 38657] New: Redwood: power state #4 not used
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=38657 Summary: Redwood: power state #4 not used Product: DRI Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mkgmafbt(a)gmail.com Created an attachment (id=48390) --> (https://bugs.freedesktop.org/attachment.cgi?id=48390) Part of dmesg with power states It's a Sapphire Radeon HD5670 512MB GDDR5. DRM reports 5 power states, but low profile won't use #4, wich is the 2D profile, nor does dynpm. All kernels with Evergreen pm support are affected by this (possible) bug, including 3.0-rc4. cat /sys/class/drm/card0/device/power_profile low cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 775000 kHz current engine clock: 399990 kHz default memory clock: 950000 kHz current memory clock: 950000 kHz voltage: 1100 mV PCIE lanes: 16 (should be 150/300 MHz 0.9V) lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] -- 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

[Bug 38756] New: [RV770] System hangs when display goes in sleep mode (with mid profile setting)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=38756 Summary: [RV770] System hangs when display goes in sleep mode (with mid profile setting) 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: b.bellec(a)gmail.com I set my Radeon in mid profile mod most of the time. After 10 minutes of inactivity, my display goes in sleep mode. Then I cannot resume the computer. I need to hard reboot. Even SysReq isn't helpful. 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV770 [Radeon HD 4850] [1002:9442] Sapphire Radeon 4850 Fedora 15 x86-64 kernel 3.0-0.rc5.git0.1.fc16 libdrm 2.4.26-1.fc15 xorg-x11-drv-ati 6.14.1-2.20110525gitfe5c42f51.fc15 -- 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 38554] New: Hibernate broken when KMS enabled on Radeon Mobility M6 LY
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=38554 Summary: Hibernate broken when KMS enabled on Radeon Mobility M6 LY 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: kjo(a)a4nancy.net.eu.org CC: kjo(a)a4nancy.net.eu.org On IBM ThinkPad X32 with Radeon Mobility M6 LY, enabling KMS breaks suspend to disk (more precisely, the devices phase). This problem is known under debian squeeze with kernels 2.6.32-18, 2.6.32-13, 2.6.32-20, 2.6.32-25, 2.6.35-1~experimental.1, 2.6.36~rc6-1~experimental.1, 2.6.39-2, 2.6.39-2-686-pae (basically all tested kernel since KMS appeared) More information can be found on the debian bug tracker: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583120 Here are some test: single user mode with KMS ========================= 1) boot in single user mode (see [1] for result of `ps aux`) 2) remove unused modules (see [2] for reslut of `lsmod`) 3) `echo freezer > /sys/power/pm_test` ; `echo disk > /sys/power/state` the freeze successes (stuff happens then bash comes back) 4) `echo devices > /sys/power/pm_test` ; `echo disk > /sys/power/state` the screen remains black, power and battery LEDs on, kernel doesn't answer to sysrq single user mode without KMS ============================ 1) boot in single user mode with `radeon.modeset=0` on kernel command line (see [3] for result of `ps aux`) 2) remove unused modules (see [4] for reslut of `lsmod`) 3) `echo freezer > /sys/power/pm_test` ; `echo disk > /sys/power/state` the freeze successes 4) `echo devices > /sys/power/pm_test` ; `echo disk > /sys/power/state` seems to succeed (stuff happens then bash comes back) single user mode with KMS, noapic, nolapic ========================================== Same test with `noapic nolapic` on kernel command line; Same result as "single user mode with KMS" single user mode with KMS, acpi=off =================================== Same test with `acpi=off` on kernel command line; The system doesn't boot, so I can't test Hope it helps, feel free to ask for more tests, Notes ===== [1]. Result of ps aux, KMS enabled: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 1.3 0.0 2080 608 ? Ss 11:20 0:00 init [S] root 2 0.0 0.0 0 0 ? S 11:20 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 11:20 0:00 [ksoftirqd/0] root 4 0.0 0.0 0 0 ? S 11:20 0:00 [kworker/0:0] root 5 0.0 0.0 0 0 ? S 11:20 0:00 [kworker/u:0] root 6 0.0 0.0 0 0 ? S 11:20 0:00 [migration/0] root 7 0.0 0.0 0 0 ? S 11:20 0:00 [watchdog/0] root 8 0.0 0.0 0 0 ? S< 11:20 0:00 [cpuset] root 9 0.0 0.0 0 0 ? S< 11:20 0:00 [khelper] root 10 0.0 0.0 0 0 ? S< 11:20 0:00 [netns] root 11 0.0 0.0 0 0 ? S 11:20 0:00 [sync_supers] root 12 0.0 0.0 0 0 ? S 11:20 0:00 [bdi-default] root 13 0.0 0.0 0 0 ? S< 11:20 0:00 [kintegrityd] root 14 0.0 0.0 0 0 ? S< 11:20 0:00 [kblockd] root 15 0.5 0.0 0 0 ? S 11:20 0:00 [kworker/0:1] root 16 0.0 0.0 0 0 ? S 11:20 0:00 [khungtaskd] root 17 0.0 0.0 0 0 ? S 11:20 0:00 [kswapd0] root 18 0.0 0.0 0 0 ? SN 11:20 0:00 [ksmd] root 19 0.0 0.0 0 0 ? SN 11:20 0:00 [khugepaged] root 20 0.0 0.0 0 0 ? S 11:20 0:00 [fsnotify_mark] root 21 0.0 0.0 0 0 ? S< 11:20 0:00 [crypto] root 24 0.0 0.0 0 0 ? S 11:20 0:00 [kworker/0:2] root 165 0.0 0.0 0 0 ? S 11:20 0:00 [khubd] root 166 0.0 0.0 0 0 ? S< 11:20 0:00 [ata_sff] root 169 0.0 0.0 0 0 ? S 11:20 0:00 [scsi_eh_0] root 170 0.0 0.0 0 0 ? S 11:20 0:00 [scsi_eh_1] root 172 0.0 0.0 0 0 ? S 11:20 0:00 [kworker/u:1] root 173 0.0 0.0 0 0 ? S 11:20 0:00 [kworker/u:2] root 256 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 257 0.0 0.0 0 0 ? S< 11:20 0:00 [kcryptd_io] root 258 0.0 0.0 0 0 ? S< 11:20 0:00 [kcryptd] root 265 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 270 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 275 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 280 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 285 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 290 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 295 0.0 0.0 0 0 ? S< 11:20 0:00 [kdmflush] root 311 0.0 0.0 0 0 ? S 11:20 0:00 [jbd2/dm-1-8] root 312 0.0 0.0 0 0 ? S< 11:20 0:00 [ext4-dio-unwrit] root 368 0.1 0.1 2588 1096 ? S<s 11:20 0:00 udevd --daemon root 514 0.7 0.0 0 0 ? S 11:20 0:00 [kworker/0:3] root 628 0.0 0.0 0 0 ? S< 11:20 0:00 [ttm_swap] root 929 0.0 0.0 0 0 ? S 11:20 0:00 [jbd2/dm-3-8] root 930 0.0 0.0 0 0 ? S< 11:20 0:00 [ext4-dio-unwrit] root 931 0.0 0.0 0 0 ? S 11:20 0:00 [jbd2/dm-4-8] root 932 0.0 0.0 0 0 ? S< 11:20 0:00 [ext4-dio-unwrit] root 933 0.0 0.0 0 0 ? S 11:20 0:00 [jbd2/dm-7-8] root 934 0.0 0.0 0 0 ? S< 11:20 0:00 [ext4-dio-unwrit] root 935 0.0 0.0 0 0 ? S 11:20 0:00 [jbd2/dm-5-8] root 936 0.0 0.0 0 0 ? S< 11:20 0:00 [ext4-dio-unwrit] root 937 0.0 0.0 0 0 ? S 11:20 0:00 [jbd2/dm-6-8] root 938 0.0 0.0 0 0 ? S< 11:20 0:00 [ext4-dio-unwrit] daemon 1226 0.0 0.0 1856 492 ? Ss 11:20 0:00 /sbin/portmap -i 127.0.0.1 statd 1256 0.0 0.0 1984 768 ? Ss 11:20 0:00 /sbin/rpc.statd root 1392 0.0 0.0 2080 88 tty4 Ss 11:20 0:00 init [S] root 1393 0.3 0.1 3088 1648 tty4 S 11:20 0:00 bash root 1394 0.0 0.0 0 0 ? S 11:20 0:00 [flush-254:1] root 1395 0.0 0.0 0 0 ? S 11:20 0:00 [flush-254:3] root 1396 0.0 0.0 0 0 ? S 11:20 0:00 [flush-254:4] root 1397 0.0 0.0 0 0 ? S 11:20 0:00 [flush-254:5] root 1398 0.0 0.0 0 0 ? S 11:20 0:00 [flush-254:6] root 1399 0.0 0.0 0 0 ? S 11:20 0:00 [flush-254:7] root 1413 0.0 0.0 2584 956 ? S< 11:21 0:00 udevd --daemon root 1414 0.0 0.0 2584 980 ? S< 11:21 0:00 udevd --daemon root 1450 0.0 0.0 2400 924 tty4 R+ 11:21 0:00 ps aux [2]. Result of lsmod, KMS enabled: Module Size Used by fuse 55666 1 radeon 712176 1 ttm 46736 1 radeon drm_kms_helper 26550 1 radeon drm 129190 3 radeon,ttm,drm_kms_helper i2c_algo_bit 12706 1 radeon power_supply 13283 1 radeon i2c_core 19022 4 radeon,drm_kms_helper,drm,i2c_algo_bit processor 26983 1 ext4 270998 6 mbcache 12810 1 ext4 jbd2 55701 1 ext4 crc16 12327 1 ext4 sha256_generic 16709 2 aes_i586 16608 2 aes_generic 37066 1 aes_i586 cbc 12659 1 dm_crypt 17809 1 dm_mod 56401 26 dm_crypt sd_mod 35060 2 crc_t10dif 12332 1 sd_mod ata_piix 21079 1 libata 132100 1 ata_piix usbcore 99225 1 scsi_mod 134453 2 sd_mod,libata thermal_sys 17667 1 processor [3]. result of `ps aux`, KMS disabled USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.5 0.0 2080 608 ? Ss 11:12 0:01 init [S] root 2 0.0 0.0 0 0 ? S 11:12 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 11:12 0:00 [ksoftirqd/0] root 4 0.1 0.0 0 0 ? S 11:12 0:00 [kworker/0:0] root 5 0.0 0.0 0 0 ? S 11:12 0:00 [kworker/u:0] root 6 0.0 0.0 0 0 ? S 11:12 0:00 [migration/0] root 7 2.0 0.0 0 0 ? S 11:12 0:04 [watchdog/0] root 8 0.0 0.0 0 0 ? S< 11:12 0:00 [cpuset] root 9 0.0 0.0 0 0 ? S< 11:12 0:00 [khelper] root 10 0.0 0.0 0 0 ? S< 11:12 0:00 [netns] root 11 0.0 0.0 0 0 ? S 11:12 0:00 [sync_supers] root 12 0.0 0.0 0 0 ? S 11:12 0:00 [bdi-default] root 13 0.0 0.0 0 0 ? S< 11:12 0:00 [kintegrityd] root 14 0.0 0.0 0 0 ? S< 11:12 0:00 [kblockd] root 15 0.5 0.0 0 0 ? S 11:12 0:01 [kworker/0:1] root 16 0.0 0.0 0 0 ? S 11:12 0:00 [khungtaskd] root 17 0.0 0.0 0 0 ? S 11:12 0:00 [kswapd0] root 18 0.0 0.0 0 0 ? SN 11:12 0:00 [ksmd] root 19 0.0 0.0 0 0 ? SN 11:12 0:00 [khugepaged] root 20 0.0 0.0 0 0 ? S 11:12 0:00 [fsnotify_mark] root 21 0.0 0.0 0 0 ? S< 11:12 0:00 [crypto] root 24 0.0 0.0 0 0 ? S 11:12 0:00 [kworker/0:2] root 159 0.0 0.0 0 0 ? S 11:12 0:00 [khubd] root 160 0.0 0.0 0 0 ? S< 11:13 0:00 [ata_sff] root 161 0.0 0.0 0 0 ? S 11:13 0:00 [scsi_eh_0] root 162 0.0 0.0 0 0 ? S 11:13 0:00 [scsi_eh_1] root 163 0.0 0.0 0 0 ? S 11:13 0:00 [kworker/u:1] root 164 0.0 0.0 0 0 ? S 11:13 0:00 [kworker/u:2] root 250 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 251 0.0 0.0 0 0 ? S< 11:14 0:00 [kcryptd_io] root 252 0.0 0.0 0 0 ? S< 11:14 0:00 [kcryptd] root 259 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 264 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 269 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 274 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 279 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 284 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 289 0.0 0.0 0 0 ? S< 11:14 0:00 [kdmflush] root 305 0.0 0.0 0 0 ? S 11:15 0:00 [jbd2/dm-1-8] root 306 0.0 0.0 0 0 ? S< 11:15 0:00 [ext4-dio-unwrit] root 362 0.1 0.1 2588 1096 ? S<s 11:15 0:00 udevd --daemon root 530 0.0 0.0 0 0 ? S 11:15 0:00 [kworker/0:3] root 555 0.0 0.0 0 0 ? S 11:15 0:00 [flush-254:1] root 884 0.0 0.0 0 0 ? S 11:15 0:00 [jbd2/dm-3-8] root 885 0.0 0.0 0 0 ? S< 11:15 0:00 [ext4-dio-unwrit] root 886 0.0 0.0 0 0 ? S 11:15 0:00 [jbd2/dm-4-8] root 887 0.0 0.0 0 0 ? S< 11:15 0:00 [ext4-dio-unwrit] root 888 0.0 0.0 0 0 ? S 11:15 0:00 [jbd2/dm-7-8] root 889 0.0 0.0 0 0 ? S< 11:15 0:00 [ext4-dio-unwrit] root 890 0.0 0.0 0 0 ? S 11:15 0:00 [jbd2/dm-5-8] root 891 0.0 0.0 0 0 ? S< 11:15 0:00 [ext4-dio-unwrit] root 892 0.0 0.0 0 0 ? S 11:15 0:00 [jbd2/dm-6-8] root 893 0.0 0.0 0 0 ? S< 11:15 0:00 [ext4-dio-unwrit] daemon 1170 0.0 0.0 1856 492 ? Ss 11:15 0:00 /sbin/portmap -i 127.0.0.1 statd 1182 0.0 0.0 1984 768 ? Ss 11:15 0:00 /sbin/rpc.statd root 1347 0.0 0.0 2080 88 tty6 Ss 11:15 0:00 init [S] root 1348 0.5 0.1 3096 1720 tty6 S 11:15 0:00 bash root 1349 0.0 0.0 0 0 ? S 11:15 0:00 [flush-254:3] root 1350 0.0 0.0 0 0 ? S 11:15 0:00 [flush-254:4] root 1351 0.0 0.0 0 0 ? S 11:15 0:00 [flush-254:5] root 1352 0.0 0.0 0 0 ? S 11:15 0:00 [flush-254:6] root 1353 0.0 0.0 0 0 ? S 11:15 0:00 [flush-254:7] root 1367 0.0 0.0 2584 956 ? S< 11:16 0:00 udevd --daemon root 1369 0.0 0.0 2584 956 ? S< 11:16 0:00 udevd --daemon root 1407 0.0 0.0 2400 932 tty6 R+ 11:16 0:00 ps aux [4]. result of lsmod, KMS disabled: Module Size Used by fuse 55666 1 processor 26983 1 ext4 270998 6 mbcache 12810 1 ext4 jbd2 55701 1 ext4 crc16 12327 1 ext4 sha256_generic 16709 2 aes_i586 16608 2 aes_generic 37066 1 aes_i586 cbc 12659 1 dm_crypt 17809 1 dm_mod 56401 26 dm_crypt sd_mod 35060 2 crc_t10dif 12332 1 sd_mod ata_piix 21079 1 libata 132100 1 ata_piix scsi_mod 134453 2 sd_mod,libata usbcore 99225 1 thermal_sys 17667 1 processor -- 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

[Bug 38465] New: Display flickers when setting power_profile
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=38465 Summary: Display flickers when setting power_profile Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: egore(a)gmx.de When calling something like echo "low" > /sys/class/drm/card0/device/power_profile my display flickers a single time. This is okay-ish, but on Microsoft Windows the clock changes do not cause such a flicker. There has to be some kind of trick to achieve that and it would be great if this would work an Linux, too. Tested on vanilla kernel 2.6.39 with libdrm 2.4.26 and xf86-video-ati 6.14.2. -- 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 37939] New: Xorg crashes with radeon KMS after resume from suspend if card in gfx
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=37939 Summary: Xorg crashes with radeon KMS after resume from suspend if card in gfx Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Keywords: regression Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hramrach(a)gmail.com cards: 220m rv515gl rv530 EG problem 2: suspend kernel using uswsusp, cancel suspend by key or due to insufficient memory -> X spinning in drm tested on some combination of rv515 / rv530 and kernel somewhere around 2.6.37-2.6.38, EG on 2.6.39 (on 2.6.38 suspend has to be stopped manually, with insufficient memory it locks up) problem 1: suspend kernel using uswsusp, start framebuffer and splashy/usplash before resume -> unusable graphics tested with some old kernels on 220m and rv515gl, possibly related to problem 2 In general it seems resume can only happen from text mode, not graphics. In response to this Debian disabled splash in early boot. This is a Xorg regression compared to UMS. -- 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 37841] New: Display distortion with powerprofile mid or low
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=37841 Summary: Display distortion with powerprofile mid or low Product: DRI Version: XOrg 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: bugreport(a)spambog.com Overview: The display is distorted when power-profile low or mid is activated. Steps to reproduce: echo low > /sys/class/drm/card0/device/power_profile or echo mid > /sys/class/drm/card0/device/power_profile Actual Results: The display is distorted, but the system is still usable. The distortion consists of noisy flickering vertical stripes, with columns between them that look ok. When I choose powerprofile default or auto or high the distortion goes away and everything's as before. Output of cat /sys/kernel/debug/dri/{0,64}/radeon_pm_info: With powerprofile default: default engine clock: 500000 kHz current engine clock: 499500 kHz default memory clock: 600000 kHz current memory clock: 594000 kHz voltage: 1000 mV PCIE lanes: 16 default engine clock: 500000 kHz current engine clock: 499500 kHz default memory clock: 600000 kHz current memory clock: 594000 kHz voltage: 1000 mV PCIE lanes: 16 With powerprofile mid: default engine clock: 500000 kHz current engine clock: 124870 kHz default memory clock: 600000 kHz current memory clock: 405000 kHz voltage: 900 mV PCIE lanes: 16 default engine clock: 500000 kHz current engine clock: 124870 kHz default memory clock: 600000 kHz current memory clock: 405000 kHz voltage: 900 mV PCIE lanes: 16 With powerprofile low: default engine clock: 500000 kHz current engine clock: 124870 kHz default memory clock: 600000 kHz current memory clock: 405000 kHz voltage: 900 mV PCIE lanes: 16 default engine clock: 500000 kHz current engine clock: 124870 kHz default memory clock: 600000 kHz current memory clock: 405000 kHz voltage: 900 mV PCIE lanes: 16 With powerprofile high: default engine clock: 500000 kHz current engine clock: 499500 kHz default memory clock: 600000 kHz current memory clock: 594000 kHz voltage: 1000 mV PCIE lanes: 16 default engine clock: 500000 kHz current engine clock: 499500 kHz default memory clock: 600000 kHz current memory clock: 594000 kHz voltage: 1000 mV PCIE lanes: 16 Expected Results: No display distortion and perhaps other values in radeon_pm_info (values of mid and low profile should differ and perhaps there should have been some lanes deactivated by these profiles). Btw. there is no such problem when I use the powermanagement-features in xorg.conf (ForceLowPowerMode, ClockGating, DynamicPM) without KMS enabled. Versions: See attached logfiles. Bug exists since power-profiles had been introduced (in kernel 2.6.34 or 2.6.35). -- 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 37368] New: Server crashes with "failed to map pixmap: -12"
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=37368 Summary: Server crashes with "failed to map pixmap: -12" Product: DRI Version: XOrg 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: gtdev(a)spearhead.de Created an attachment (id=46907) --> (https://bugs.freedesktop.org/attachment.cgi?id=46907) Server log with crash info Every now and then, the X server will crash on my machine and restart to kdm. I have never seen it happen live so far, it always happened when I was away from the machine for some time. System is Debian unstable, xserver-xorg-core package version is 1.10.1-2, but the problem has been occuring for some months now. In the server log, I find: ========== failed to map pixmap: -12 Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a38b8] 1: /usr/bin/X (0x400000+0x646e9) [0x4646e9] 2: /lib/libpthread.so.0 (0x7f45b8dd2000+0xf020) [0x7f45b8de1020] 3: /lib/libc.so.6 (0x7f45b7aed000+0x84b30) [0x7f45b7b71b30] 4: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x6436) [0x7f45b5611436] 5: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x8f92) [0x7f45b5613f92] 6: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x12355) [0x7f45b561d355] 7: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x9b31) [0x7f45b5614b31] 8: /usr/bin/X (0x400000+0xe0034) [0x4e0034] 9: /usr/bin/X (0x400000+0x2e283) [0x42e283] 10: /usr/bin/X (0x400000+0x31731) [0x431731] 11: /usr/bin/X (0x400000+0x257de) [0x4257de] 12: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f45b7b0bead] 13: /usr/bin/X (0x400000+0x25389) [0x425389] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. ========== A full server log is 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 2

[Bug 37040] New: Radeon driver reports EDID errors every 10 seconds
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=37040 Summary: Radeon driver reports EDID errors every 10 seconds Product: DRI Version: unspecified 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: teufel(a)cs.uni-frankfurt.de Created an attachment (id=46512) --> (https://bugs.freedesktop.org/attachment.cgi?id=46512) an excerpt of /var/log/messages with some comments and an example of the output to tty1 Radeon driver reports EDID errors every 10 seconds, which causes related log files increased over 100M in size every day and makes the system hardly usable because of the output every 10 seconds to tty1 (and ttyS0 in my case). See also my related LKML message: https://lkml.org/lkml/2011/4/14/661 I get every 10 seconds: radeon 0000:01:05.0: HDMI-A-1: EDID block 0 invalid. together with a block of zeroes (only on tty1, see attachment). OS: Debian GNU/Linux 6.0.1 (squeeze) kernel: Linux 2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1) (it was the same with Linux 2.6.32-5-amd64 (2.6.32-31)) Mainboard: ASUS M2A-VM Chipset (onboard): ATI Technologies Inc RS690 [Radeon X1200 Series] aka 01:05.0 0300: 1002:791e -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2011