dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 51355] New: Mode switch kills HDMI on TURKS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=51355 Bug #: 51355 Summary: Mode switch kills HDMI on TURKS Classification: Unclassified 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: zboszor(a)pr.hu Created attachment 63369 --> https://bugs.freedesktop.org/attachment.cgi?id=63369 dmesg log after a prboom session I have tried playing prboom on Fedora 17/x86_64 and noticed that the HDMI output is turned off. The DVI output is set to primary, mode switch to 640x480 is performed on the DVI output and it's switched back to 1920x1080 when exiting from prboom but HDMI output is not restored. The TV says "no signal", xrandr says this before or after a prboom session: $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 HDMI-0 connected (normal left inverted right x axis y axis) 1360x768 60.0 + 60.0 1920x1080 60.0 50.0 30.0 25.0 24.0 30.0 25.0 1920x1080i 30.0 1680x1050 60.0 59.9 1680x945 60.0 1400x1050 60.0 59.9 1600x900 60.0 1280x1024 75.0 60.0 1440x900 59.9 59.9 1280x960 60.0 1366x768 60.0 1280x800 74.9 59.8 59.9 1152x864 75.0 1280x768 84.8 74.9 59.9 60.0 1280x720 60.0 50.0 1440x576 25.0 1024x768 85.0 75.1 75.0 70.1 60.0 1440x480 30.0 1024x576 60.0 800x600 85.1 72.2 75.0 60.3 56.2 720x576 50.0 848x480 60.0 720x480 59.9 640x480 85.0 75.0 72.8 60.0 59.9 59.9 720x400 85.0 640x400 85.1 640x350 85.1 DVI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.0*+ 60.0 2048x1152 60.0 1920x1200 59.9 60.0 1600x1200 65.0 60.0 1680x1050 74.9 60.0 59.9 1680x945 60.0 1400x1050 74.9 60.0 59.9 1600x900 60.0 1280x1024 75.0 60.0 1440x900 75.0 59.9 59.9 1280x960 60.0 1366x768 60.0 1360x768 60.0 1280x800 74.9 59.8 59.9 1152x864 75.0 1280x768 74.9 59.9 60.0 1280x720 60.0 1024x768 75.1 75.0 70.1 60.0 1024x576 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 848x480 60.0 640x480 75.0 72.8 60.0 59.9 720x400 70.1 VGA-0 disconnected (normal left inverted right x axis y axis) dmesg shows some bugs being hit: [140302.370894] ------------[ cut here ]------------ [140302.370943] WARNING: at drivers/gpu/drm/radeon/r600_hdmi.c:548 r600_hdmi_disable+0x161/0x1c0 [radeon]() [140302.370946] Hardware name: To be filled by O.E.M. [140302.371022] Modules linked in: tcp_lp rfcomm fuse ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_d efrag_ipv4 xt_state nf_conntrack bnep be2iscsi iscsi_boot_sysfs bluetooth bnx2i cnic uio cxgb4i cxgb4 cxgb3i xt_CHECKSUM iptable_mangle cxgb3 mdio libcxgbi ib _iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi bridge scsi_transport_iscsi stp llc w83793 hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec eeepc_wmi microcode asus_wmi r8169 snd_hwdep hid_generic snd_pcm sparse_keymap snd_page_alloc snd_timer rfk ill edac_core edac_mce_amd serio_raw pcspkr sp5100_tco snd fam15h_power k10temp i2c_piix4 mii soundcore vhost_net tun macvtap macvlan nfsd nfs_acl auth_rpcgss kvm_amd kvm lockd sunrpc uinput binfmt_misc crc32c_intel ghash_clmulni_intel 3w_9xxx firewire_ohci firewire_core mxm_wmi crc_itu_t wmi radeon i2c_algo_bit dr m_kms_helper ttm drm i2c_core [last unloaded: scsi_wait_scan] [140302.371029] Pid: 13250, comm: Xorg Not tainted 3.5.0-rc3+ #1 [140302.371032] Call Trace: [140302.371042] [<ffffffff81055cdf>] warn_slowpath_common+0x7f/0xc0 [140302.371049] [<ffffffff81055d3a>] warn_slowpath_null+0x1a/0x20 [140302.371072] [<ffffffffa00de261>] r600_hdmi_disable+0x161/0x1c0 [radeon] [140302.371095] [<ffffffffa00f0fb5>] radeon_atom_encoder_disable+0x175/0x180 [radeon] [140302.371113] [<ffffffffa004a678>] drm_encoder_disable+0x18/0x30 [drm_kms_helper] [140302.371127] [<ffffffffa004b0b8>] drm_crtc_helper_set_mode+0x468/0x500 [drm_kms_helper] [140302.371150] [<ffffffffa004c171>] drm_crtc_helper_set_config+0xa11/0xb30 [drm_kms_helper] [140302.371175] [<ffffffffa0022e77>] drm_mode_setcrtc+0x127/0x5c0 [drm] [140302.371181] [<ffffffff815f1b7d>] ? mutex_lock+0x1d/0x50 [140302.371209] [<ffffffffa00a7df2>] ? radeon_crtc_gamma_set+0x72/0x80 [radeon] [140302.371226] [<ffffffffa0013553>] drm_ioctl+0x4d3/0x580 [drm] [140302.371248] [<ffffffffa0022d50>] ? drm_mode_setplane+0x380/0x380 [drm] [140302.371257] [<ffffffff81181149>] do_vfs_ioctl+0x99/0x580 [140302.371263] [<ffffffff812618aa>] ? inode_has_perm.isra.30.constprop.60+0x2a/0x30 [140302.371268] [<ffffffff81262e27>] ? file_has_perm+0x97/0xb0 [140302.371273] [<ffffffff811816c9>] sys_ioctl+0x99/0xa0 [140302.371280] [<ffffffff815fbe29>] system_call_fastpath+0x16/0x1b [140302.371284] ---[ end trace 5b0596b4d30657d2 ]--- [140302.374401] ------------[ cut here ]------------ [140302.374435] WARNING: at drivers/gpu/drm/radeon/r600_hdmi.c:548 r600_hdmi_disable+0x161/0x1c0 [radeon]() [140302.374438] Hardware name: To be filled by O.E.M. [140302.374511] Modules linked in: tcp_lp rfcomm fuse ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_d efrag_ipv4 xt_state nf_conntrack bnep be2iscsi iscsi_boot_sysfs bluetooth bnx2i cnic uio cxgb4i cxgb4 cxgb3i xt_CHECKSUM iptable_mangle cxgb3 mdio libcxgbi ib _iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi bridge scsi_transport_iscsi stp llc w83793 hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec eeepc_wmi microcode asus_wmi r8169 snd_hwdep hid_generic snd_pcm sparse_keymap snd_page_alloc snd_timer rfk ill edac_core edac_mce_amd serio_raw pcspkr sp5100_tco snd fam15h_power k10temp i2c_piix4 mii soundcore vhost_net tun macvtap macvlan nfsd nfs_acl auth_rpcgss kvm_amd kvm lockd sunrpc uinput binfmt_misc crc32c_intel ghash_clmulni_intel 3w_9xxx firewire_ohci firewire_core mxm_wmi crc_itu_t wmi radeon i2c_algo_bit dr m_kms_helper ttm drm i2c_core [last unloaded: scsi_wait_scan] [140302.374518] Pid: 13250, comm: Xorg Tainted: G W 3.5.0-rc3+ #1 [140302.374520] Call Trace: [140302.374529] [<ffffffff81055cdf>] warn_slowpath_common+0x7f/0xc0 [140302.374536] [<ffffffff81055d3a>] warn_slowpath_null+0x1a/0x20 [140302.374558] [<ffffffffa00de261>] r600_hdmi_disable+0x161/0x1c0 [radeon] [140302.374581] [<ffffffffa00f0fb5>] radeon_atom_encoder_disable+0x175/0x180 [radeon] [140302.374595] [<ffffffffa004a678>] drm_encoder_disable+0x18/0x30 [drm_kms_helper] [140302.374608] [<ffffffffa004a7d0>] drm_helper_disable_unused_functions+0x140/0x170 [drm_kms_helper] [140302.374622] [<ffffffffa004c0a2>] drm_crtc_helper_set_config+0x942/0xb30 [drm_kms_helper] [140302.374646] [<ffffffffa0022e77>] drm_mode_setcrtc+0x127/0x5c0 [drm] [140302.374651] [<ffffffff815f1b7d>] ? mutex_lock+0x1d/0x50 [140302.374678] [<ffffffffa00a7df2>] ? radeon_crtc_gamma_set+0x72/0x80 [radeon] [140302.374695] [<ffffffffa0013553>] drm_ioctl+0x4d3/0x580 [drm] [140302.374717] [<ffffffffa0022d50>] ? drm_mode_setplane+0x380/0x380 [drm] [140302.374725] [<ffffffff81181149>] do_vfs_ioctl+0x99/0x580 [140302.374730] [<ffffffff812618aa>] ? inode_has_perm.isra.30.constprop.60+0x2a/0x30 [140302.374735] [<ffffffff81262e27>] ? file_has_perm+0x97/0xb0 [140302.374740] [<ffffffff811816c9>] sys_ioctl+0x99/0xa0 [140302.374746] [<ffffffff815fbe29>] system_call_fastpath+0x16/0x1b [140302.374749] ---[ end trace 5b0596b4d30657d3 ]--- [140302.382514] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140302.382542] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140302.682598] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140302.682619] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140302.983555] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140302.983583] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140303.284423] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140303.284450] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140303.585144] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140303.585171] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140303.885975] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140303.885992] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140304.186780] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140304.186808] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140304.487641] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140304.487730] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [140304.788431] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [140304.788450] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149602.598876] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149602.598906] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149602.899406] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149602.899435] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149603.200220] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149603.200238] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149603.501001] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149603.501019] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149603.801893] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149603.801983] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149604.102716] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149604.102747] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149604.406520] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149604.406538] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149604.707445] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149604.707463] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [149605.008251] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [149605.008280] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 Kernel is 3.5-rc3+, commit 2fe8ac608bf1a9c947f03f5d8cbf25c91b4f1a7c. -- 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 51190] New: [RADEON:KMS:RV370:RESUME] garbage on screen (console or X) after suspend-resume with radeon (KMS only)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=51190 Bug #: 51190 Summary: [RADEON:KMS:RV370:RESUME] garbage on screen (console or X) after suspend-resume with radeon (KMS only) Classification: Unclassified Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: cyberbat(a)lavabit.com Created attachment 63153 --> https://bugs.freedesktop.org/attachment.cgi?id=63153 full kernel 3.5rc2 log Screen on my Samsung R50 notebook with AMD Mobility Radeon X300 (RV370 chipset) become completely unusable after resume (watch screenshots). I've tested different kernels from 2.6.32 till 3.5rc2. Just the same thing. The thing happens only with KMS turned on. I have tried suspend from X (Xfce) and from console (using pm-suspend). I repeatedly get following errors in kernel log after resume: Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000000023d last fence id 0x000000000000023c) Jun 15 18:56:39 localhost kernel: Failed to wait GUI idle while programming pipes. Bad things might happen. Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:392) RBBM_STATUS=0x80010140 Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:411) RBBM_STATUS=0x80010140 Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:423) RBBM_STATUS=0x00000140 Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU reset succeed Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: GPU reset succeed Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: f5eaf400 unpin not necessary Jun 15 18:56:39 localhost kernel: [drm] radeon: 1 quad pipes, 1 Z pipes initialized. Jun 15 18:56:39 localhost kernel: [drm] PCIE GART of 512M enabled (table at 0x00000000D0040000). Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: WB enabled Jun 15 18:56:39 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000b0000000 and cpu addr 0xff8de000 Jun 15 18:56:39 localhost kernel: [drm] radeon: ring at 0x00000000B0001000 Jun 15 18:56:39 localhost kernel: [drm] ring test succeeded in 1 usecs Jun 15 18:56:39 localhost kernel: [drm] ib test succeeded in 0 usecs ... Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000490 last fence id 0x000000000000033b) Jun 15 18:58:32 localhost kernel: Failed to wait GUI idle while programming pipes. Bad things might happen. Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:392) RBBM_STATUS=0x80010140 Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:411) RBBM_STATUS=0x80010140 Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:423) RBBM_STATUS=0x00000140 Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU reset succeed Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: GPU reset succeed Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: f5eaf400 unpin not necessary Jun 15 18:58:32 localhost kernel: [drm] radeon: 1 quad pipes, 1 Z pipes initialized. Jun 15 18:58:32 localhost kernel: [drm] PCIE GART of 512M enabled (table at 0x00000000D0040000). Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: WB enabled Jun 15 18:58:32 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000b0000000 and cpu addr 0xff8de000 Jun 15 18:58:32 localhost kernel: [drm] radeon: ring at 0x00000000B0001000 Jun 15 18:58:32 localhost kernel: [drm] ring test succeeded in 1 usecs Jun 15 18:58:32 localhost kernel: [drm] ib test succeeded in 0 usecs Jun 15 19:00:46 localhost /usr/sbin/gpm[1110]: *** info [daemon/processrequest.c(42)]: Jun 15 19:00:46 localhost /usr/sbin/gpm[1110]: Request on 6 (console 1) Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for more than 200579msec Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000000058f) Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: failed to get a new IB (-35) Jun 15 19:01:42 localhost kernel: [drm:radeon_cs_ib_chunk] *ERROR* Failed to get ib ! Jun 15 19:01:42 localhost kernel: Failed to wait GUI idle while programming pipes. Bad things might happen. Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:392) RBBM_STATUS=0x80010140 Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:411) RBBM_STATUS=0x80010140 Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: (r300_asic_reset:423) RBBM_STATUS=0x00000140 Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU reset succeed Jun 15 19:01:42 localhost kernel: radeon 0000:01:00.0: GPU reset succeed I recognize that I have really old notebook, but It has enough power for my tasks so it will be good to use KMS on it cause I loose a lot of features of X without it. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 50805] New: radeon gpu driver bug on suspend/resume in 3.5-rc1
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=50805 Bug #: 50805 Summary: radeon gpu driver bug on suspend/resume in 3.5-rc1 Classification: Unclassified Product: DRI Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: austin.lund(a)gmail.com Created attachment 62685 --> https://bugs.freedesktop.org/attachment.cgi?id=62685 two samples of the kernel log I get the attached traces with 3.5-rc1 after suspend/resume, sometimes. It doesn't always happen. Usually happens at least once in 10 suspend/resume cycles. The first trace seems non fatal, but the system locks up in the second one and needs to be rebooted. -- 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 49943] New: radeon/drm: Hotplug udev events stop working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=49943 Bug #: 49943 Summary: radeon/drm: Hotplug udev events stop working Classification: Unclassified Product: DRI Version: XOrg CVS Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: h.judt(a)gmx.at Making use of udev events, I'd like to launch a script when a monitor gets connected or disconnected. However, an event is only fired once and then never again. Kernel: linux-3.4.0-rc7 lspci: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cayman PRO [Radeon HD 6950] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI Device 0b00 Flags: bus master, fast devsel, latency 0, IRQ 54 Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at fe620000 (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at fe600000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon xrandr --verbose: HDMI-0 connected (normal left inverted right x axis y axis) Identifier: 0x58 Timestamp: 21810 Subpixel: horizontal rgb Clones: CRTCs: 0 1 2 3 4 5 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff002203010be9030000 00110103804627780b1990a755469824 10494b3fcf00818081cf81c061c04bc0 4bcf453c61cf011d007251d01e206e28 5500c48e2100001e011d8018711c1620 582c2500c48e2100009e000000fc004d 737461722044656d6f0a2020000000fd 0016500e5b10000a202020202020014b 02031df24a0102038405101293141f23 0907078301000065030c0010008c0ad0 8a20e02d10103e9600138e2100001801 1d00bc52d01e20b8285540c48e210000 1e011d80d0721c1620102c2580c48e21 00009e8c0ad08a20e02d10103e9600c4 8e210000188c0ad090204031200c4055 00c48e2100001800000000000000002b underscan vborder: 0 (0x00000000) range: (0,128) underscan hborder: 0 (0x00000000) range: (0,128) underscan: off supported: off on auto coherent: 1 (0x00000001) range: (0,1) ----- [modes cut off here] ----- ls -la /sys/class/drm/card0-HDMI-A-1/ insgesamt 0 drwxr-xr-x 3 root root 0 15. Mai 2012 . drwxr-xr-x 8 root root 0 15. Mai 2012 .. lrwxrwxrwx 1 root root 0 15. Mai 10:12 device -> ../../card0 -r--r--r-- 1 root root 4096 15. Mai 10:12 dpms -r--r--r-- 1 root root 0 15. Mai 10:12 edid -r--r--r-- 1 root root 4096 15. Mai 10:12 enabled -r--r--r-- 1 root root 4096 15. Mai 10:12 modes drwxr-xr-x 2 root root 0 15. Mai 10:12 power -r--r--r-- 1 root root 4096 15. Mai 09:14 status lrwxrwxrwx 1 root root 0 15. Mai 2012 subsystem -> ../../../../../../../class/drm -rw-r--r-- 1 root root 4096 15. Mai 2012 uevent Note the modification date of status and the other files. That of status did not change at all since boot, and the mdates of the others did change once apparently. I can poll "status" and see the changes when executing xrandr, but there will be no more events, and the modification dates do not change anymore. -- 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 49322] New: No picture on display connected via Displayport adaptor to HD 7870
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=49322 Bug #: 49322 Summary: No picture on display connected via Displayport adaptor to HD 7870 Classification: Unclassified 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: briancschott(a)gmail.com Created attachment 60820 --> https://bugs.freedesktop.org/attachment.cgi?id=60820 dmesg output Radeon HD 7870 mesa 8.0.2 Kernel 3.4-rc5 X.Org X Server 1.12.0 xf86-video-modesetting 0.2.0 * Monitor is a DVI monitor connected to an active mini-displayport to DVI adaptor. * Output to all three screens functions in Windows. * dmesg output and xrandr output are able to see the display and print out the correct supported resolutions * HDMI and DVI output are functioning correctly on the card. * Using xrandr I'm able to get the X server to think that the display is present and functioning. (I can place windows and the cursor on the screen) * The display is in power-saving mode from the moment that the framebuffer console initializes. I'm not able to get any image on it. -- 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 49029] New: [DRM,KMS,R300,laptop]Power management not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=49029 Bug #: 49029 Summary: [DRM,KMS,R300,laptop]Power management not working Classification: Unclassified 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: malicorne(a)chez.com Created attachment 60410 --> https://bugs.freedesktop.org/attachment.cgi?id=60410 drm output from kernel.log Hi, Archlinux running on a compal CL56 (radeon mobility 9700). kernel is 3.2.11 and I can't find any file for power management : - /sys/class/drm/card0/device/power_method doesn't exist and can't be created - /sys/class/drm/card0/device/power_profile doesn't exist and can't be created Please find attached drm output from kernel.log. Apart from that it's working fine but the lack of power management reduce the run from a battery from 4h to 1h30. -- 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 48772] New: Signal unstable over Display Port on 2560x1440 monitor
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=48772 Bug #: 48772 Summary: Signal unstable over Display Port on 2560x1440 monitor Classification: Unclassified 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: tvrtko.ursulin(a)onelan.co.uk AMD G-T56N (Radeon HD 6310) hardware with kernel 3.4-rc3 with a Xorg DDX from 28.03.2012. plus a tiling patch from bug 47765. Dell U2711 monitor native resolution is 2560x1440 on which Display Port connection is unstable. I get periodic very brief flashes of vertical noise areas, full screen width, at various vertical positions, but possible always at least roughly the same height. Then the screen goes black for a second, comes back for a while, flashing, or straight back to black and so on. Timings do not look regular, although I haven't actually timed and analysed them. Bringing the resolution down to 1920x1200 and it works fine. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 20

[Bug 48197] New: DVI monitor connected to an Ati x1550 on standard resolution blinks.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=48197 Bug #: 48197 Summary: DVI monitor connected to an Ati x1550 on standard resolution blinks. Classification: Unclassified Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ter4py(a)gmail.com Created attachment 59380 --> https://bugs.freedesktop.org/attachment.cgi?id=59380 dmesg from fedora 16 I have an Ati radeon x1550, and connected to that a DVI monitor (and another to the VGA, but this bug is present also when only the DVI monitor is connected) This bug appears in every distribution and kernel I tried, the last one is fedora 16, but I tried debian 6 too and Archlinux with the latest kernel. Description of problem: DVI screen, if on standard resolution (1680x1050) blinks from the tty to the Gnome dekstop, and especially when something like Firefox is made fullscreen: I recorded a video to explain this better: https://www.youtube.com/watch?v=8Tcjb6p0Yi4 -- 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 47708] New: LVDS panel does not turns off in stand-by mode
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=47708 Bug #: 47708 Summary: LVDS panel does not turns off in stand-by mode 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: eugene.shalygin(a)gmail.com Created attachment 58858 --> https://bugs.freedesktop.org/attachment.cgi?id=58858 dmesg When video goes into sleep mode, LVDS panel starts to show screens filled with b/w gradients and RGB colours in a cycle. In the same time a screen, connected via Display-Port goes into sleep mode correctly. This happens with and without X running. Ati drivers do not show such a behaviour. Hardware: Acer Aspire 8942g with Mobility Radeon HD 5850. Linux version 3.3 (but this happens starting with version 2.6.2x of 2.6.3x when I've tried KMS for the first time). -- 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 46711] New: Monitor not turning on after DisplayPort re-plug in Xorg
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=46711 Bug #: 46711 Summary: Monitor not turning on after DisplayPort re-plug in Xorg Classification: Unclassified 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: tvrtko.ursulin(a)onelan.co.uk Created attachment 57747 --> https://bugs.freedesktop.org/attachment.cgi?id=57747 Kernel DRM debug log showing successful replug without, and failing with Xorg running. On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up displaying the console. Re-pluging the display cable with no Xorg running is fine. Attached kernel DRM debug log. Log itself which ends after cable re-plug when Xorg is running. Which is when the display goes into power save. Before that in the same log you can find Xorg starting up and before that a successful cable re- plug when X was not running. All this is with kernel.org 3.3.0-rc4 kernel. Xorg packages are: xorg-x11-server-Xorg-1.11.3-1.fc16.x86_64 xorg-x11-drv-ati-6.14.3-8.20120209gite20284409.fc16.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 26

← Newer
1
2
3
4
5
6
7
...
73
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013