dri-devel March 2011

dri-devel@lists.freedesktop.org

88 participants
477 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 35045] New: BUG at ttm_bo.c:272! (ttm_bo_ref_bug -> ttm_bo_list_ref_sub+0x28/0x30)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=35045 Summary: BUG at ttm_bo.c:272! (ttm_bo_ref_bug -> ttm_bo_list_ref_sub+0x28/0x30) 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: freedesktop(a)treblig.org Hi, I've got a repeatable oops that happens when viewing full screen video in flash in chromium, under kwin (with effects enabled) and switching virtual desktop/workspace on ATI Technologies Inc RV710 [Radeon HD 4350]. Hardware: ATI Technologies Inc RV710 [Radeon HD 4350] in an ASRock P55M Pro motherboard, with an i7-860 CPU, and 8GB RAM, connected to Dell S2409W display via DVI. OS: Ubuntu Natty upto date as of today, 64bit install, running KDE. Kernel: Daily build from DRM next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/ linux-image-2.6.38-996-generic_2.6.38-996.201103041138_amd64.deb claims to be commit e73f88af66fcc50083fae4b7e1c39b469179a97a DRM/mesa/etc: ii libdrm-radeon1 2.4.23-1ubuntu3 ii libdrm2 2.4.23-1ubuntu3 ii libgl1-mesa-dri 7.10.1~git20110215.cc1636b6-0 I've got a 3x3 virtual desktop setup, and am running Chromium and go to youtube and pop a video full screen; and move around the virtual desktop with ctrl-alt-arrows. The oops below was produced twice. I've got a bunch of related symptoms; I installed the daily build because I was getting instances of [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35! (which I think is EDEADLOCK) doing similar combinations of going in and out of full screen flash. I've also seen when I try to go into full screen rapid flickering as if it can't decide whether to go into full screen or stay out; once that's triggered that flickering can repeat itself when starting other apps. This corresponds to Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717870 and possibly also ubuntu bug 717889 Mar 5 22:12:17 major kernel: [ 495.890854] ------------[ cut here ]------------ Mar 5 22:12:17 major kernel: [ 495.890882] kernel BUG at /home/kernel-ppa/COD/linux/drivers/gpu/drm/ttm/ttm_bo.c:272! Mar 5 22:12:17 major kernel: [ 495.890917] invalid opcode: 0000 [#1] SMP Mar 5 22:12:17 major kernel: [ 495.890939] last sysfs file: /sys/devices/system/cpu/cpu7/topology/thread_siblings Mar 5 22:12:17 major kernel: [ 495.890971] CPU 1 Mar 5 22:12:17 major kernel: [ 495.890981] Modules linked in: ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT binfmt_misc xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm dm_crypt snd_hda_codec_hdmi snd_hda_codec_via snd_hda_intel snd_seq_midi snd_hda_codec snd_rawmidi snd_hwdep snd_seq_midi_event snd_seq snd_pcm snd_seq_device snd_timer snd ppdev soundcore parport_pc snd_page_alloc lp parport radeon usbhid usb_storage ttm hid firewire_ohci drm_kms_helper uas drm firewire_core r8169 pata_via crc_itu_t i2c_algo_bit configfs Mar 5 22:12:17 major kernel: [ 495.891289] Mar 5 22:12:17 major kernel: [ 495.893682] Pid: 42, comm: kworker/1:1 Not tainted 2.6.38-996-generic #201103041138 P55M Pro/To Be Filled By O.E.M. Mar 5 22:12:17 major kernel: [ 495.896183] RIP: 0010:[<ffffffffa00f3d89>] [<ffffffffa00f3d89>] ttm_bo_ref_bug+0x9/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 495.898561] RSP: 0000:ffff8802277ebd90 EFLAGS: 00010202 Mar 5 22:12:17 major kernel: [ 495.900903] RAX: ffffffffa00f6801 RBX: 0000000000000000 RCX: ffff880222bb3120 Mar 5 22:12:17 major kernel: [ 495.903223] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff880222bb308c Mar 5 22:12:17 major kernel: [ 495.905545] RBP: ffff8802277ebd90 R08: 0000000000000000 R09: 0000000000000000 Mar 5 22:12:17 major kernel: [ 495.907870] R10: ffff8800c7453b58 R11: 0000000000000000 R12: ffff880222bb308c Mar 5 22:12:17 major kernel: [ 495.910371] R13: ffffffffa00f3d80 R14: ffff880222bb3048 R15: 0000000000000000 Mar 5 22:12:17 major kernel: [ 495.912659] FS: 0000000000000000(0000) GS:ffff8800c7440000(0000) knlGS:0000000000000000 Mar 5 22:12:17 major kernel: [ 495.914975] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Mar 5 22:12:17 major kernel: [ 495.917310] CR2: 00000000f0969000 CR3: 00000001dc19a000 CR4: 00000000000006e0 Mar 5 22:12:17 major kernel: [ 495.919642] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 5 22:12:17 major kernel: [ 495.921973] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Mar 5 22:12:17 major kernel: [ 495.924274] Process kworker/1:1 (pid: 42, threadinfo ffff8802277ea000, task ffff8802277bc440) Mar 5 22:12:17 major kernel: [ 495.926774] Stack: Mar 5 22:12:17 major kernel: [ 495.929067] ffff8802277ebdc0 ffffffff812d31be 0000000000000001 0000000000000000 Mar 5 22:12:17 major kernel: [ 495.931384] ffff880222b1a208 0000000000000000 ffff8802277ebdd0 ffffffffa00f5048 Mar 5 22:12:17 major kernel: [ 495.933688] ffff8802277ebe10 ffffffffa00f67c8 01ff8802277ebe10 ffff880222bb3000 Mar 5 22:12:17 major kernel: [ 495.936003] Call Trace: Mar 5 22:12:17 major kernel: [ 495.938310] [<ffffffff812d31be>] kref_sub+0x3e/0x80 Mar 5 22:12:17 major kernel: [ 495.940583] [<ffffffffa00f5048>] ttm_bo_list_ref_sub+0x28/0x30 [ttm] Mar 5 22:12:17 major kernel: [ 495.942967] [<ffffffffa00f67c8>] ttm_bo_reserve+0x88/0xa0 [ttm] Mar 5 22:12:17 major kernel: [ 495.945209] [<ffffffffa0154858>] radeon_unpin_work_func+0x28/0xb0 [radeon] Mar 5 22:12:17 major kernel: [ 495.947398] [<ffffffff810813ce>] process_one_work+0x10e/0x390 Mar 5 22:12:17 major kernel: [ 495.949673] [<ffffffffa0154830>] ? radeon_unpin_work_func+0x0/0xb0 [radeon] Mar 5 22:12:17 major kernel: [ 495.951872] [<ffffffff8108221d>] worker_thread+0xdd/0x260 Mar 5 22:12:17 major kernel: [ 495.954094] [<ffffffff81082140>] ? worker_thread+0x0/0x260 Mar 5 22:12:17 major kernel: [ 495.956341] [<ffffffff81086277>] kthread+0x97/0xa0 Mar 5 22:12:17 major kernel: [ 495.958735] [<ffffffff8100ce24>] kernel_thread_helper+0x4/0x10 Mar 5 22:12:17 major kernel: [ 495.958738] [<ffffffff810861e0>] ? kthread+0x0/0xa0 Mar 5 22:12:17 major kernel: [ 495.958740] [<ffffffff8100ce20>] ? kernel_thread_helper+0x0/0x10 Mar 5 22:12:17 major kernel: [ 495.958741] Code: 48 89 10 48 89 8f e0 00 00 00 48 89 8f d8 00 00 00 c9 89 f0 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 0f 1f 44 00 00 <0f> 0b eb fe 0f 1f 00 55 48 89 e5 0f 1f 44 00 00 48 83 3e 00 48 Mar 5 22:12:17 major kernel: [ 495.958754] RIP [<ffffffffa00f3d89>] ttm_bo_ref_bug+0x9/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 495.958761] RSP <ffff8802277ebd90> Mar 5 22:12:17 major kernel: [ 495.970338] ---[ end trace eb6ea5ab08ebf6f9 ]--- Mar 5 22:12:17 major kernel: [ 495.971011] BUG: unable to handle kernel paging request at fffffffffffffff8 Mar 5 22:12:17 major kernel: [ 495.973499] IP: [<ffffffff81085f30>] kthread_data+0x10/0x20 Mar 5 22:12:17 major kernel: [ 495.976059] PGD 1a05067 PUD 1a06067 PMD 0 Mar 5 22:12:17 major kernel: [ 495.978440] Oops: 0000 [#2] SMP Mar 5 22:12:17 major kernel: [ 495.980762] last sysfs file: /sys/devices/system/cpu/cpu7/topology/thread_siblings Mar 5 22:12:17 major kernel: [ 495.983104] CPU 1 Mar 5 22:12:17 major kernel: [ 495.983112] Modules linked in: ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT binfmt_misc xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm dm_crypt snd_hda_codec_hdmi snd_hda_codec_via snd_hda_intel snd_seq_midi snd_hda_codec snd_rawmidi snd_hwdep snd_seq_midi_event snd_seq snd_pcm snd_seq_device snd_timer snd ppdev soundcore parport_pc snd_page_alloc lp parport radeon usbhid usb_storage ttm hid firewire_ohci drm_kms_helper uas drm firewire_core r8169 pata_via crc_itu_t i2c_algo_bit configfs Mar 5 22:12:17 major kernel: [ 495.993045] Mar 5 22:12:17 major kernel: [ 495.995587] Pid: 42, comm: kworker/1:1 Tainted: G D 2.6.38-996-generic #201103041138 P55M Pro/To Be Filled By O.E.M. Mar 5 22:12:17 major kernel: [ 495.998137] RIP: 0010:[<ffffffff81085f30>] [<ffffffff81085f30>] kthread_data+0x10/0x20 Mar 5 22:12:17 major kernel: [ 496.000687] RSP: 0018:ffff8802277eb9a8 EFLAGS: 00010096 Mar 5 22:12:17 major kernel: [ 496.003225] RAX: 0000000000000000 RBX: ffff8802277bc440 RCX: ffff8802277ebb28 Mar 5 22:12:17 major kernel: [ 496.005892] RDX: ffff8802277bc440 RSI: 0000000000000001 RDI: ffff8802277bc440 Mar 5 22:12:17 major kernel: [ 496.008436] RBP: ffff8802277eb9a8 R08: ffff8800c7456f60 R09: ffff88022762b8a8 Mar 5 22:12:17 major kernel: [ 496.010907] R10: ffff88022762b898 R11: 0000000000000001 R12: 0000000000000001 Mar 5 22:12:17 major kernel: [ 496.013390] R13: 0000000000000001 R14: ffff8800c7453ac0 R15: 00007ffffffff000 Mar 5 22:12:17 major kernel: [ 496.015887] FS: 0000000000000000(0000) GS:ffff8800c7440000(0000) knlGS:0000000000000000 Mar 5 22:12:17 major kernel: [ 496.018383] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Mar 5 22:12:17 major kernel: [ 496.020860] CR2: fffffffffffffff8 CR3: 00000001dc19a000 CR4: 00000000000006e0 Mar 5 22:12:17 major kernel: [ 496.023477] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 5 22:12:17 major kernel: [ 496.025936] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Mar 5 22:12:17 major kernel: [ 496.028369] Process kworker/1:1 (pid: 42, threadinfo ffff8802277ea000, task ffff8802277bc440) Mar 5 22:12:17 major kernel: [ 496.030832] Stack: Mar 5 22:12:17 major kernel: [ 496.033291] ffff8802277eb9d8 ffffffff8107f89a ffff8802277eba48 ffff8802277bc440 Mar 5 22:12:17 major kernel: [ 496.035764] ffff8802277bc7e0 0000000000000001 ffff8802277ebb28 ffffffff815b11e9 Mar 5 22:12:17 major kernel: [ 496.038401] ffff880222f55800 ffff8802277ebfd8 ffff8802277ebb28 0000000000013ac0 Mar 5 22:12:17 major kernel: [ 496.040860] Call Trace: Mar 5 22:12:17 major kernel: [ 496.043305] [<ffffffff8107f89a>] wq_worker_sleeping+0x1a/0x90 Mar 5 22:12:17 major kernel: [ 496.045791] [<ffffffff815b11e9>] schedule+0x549/0x790 Mar 5 22:12:17 major kernel: [ 496.048146] [<ffffffff812c8429>] ? cfq_cic_free+0x19/0x20 Mar 5 22:12:17 major kernel: [ 496.050423] [<ffffffff812cb00a>] ? cic_free_func+0x7a/0x90 Mar 5 22:12:17 major kernel: [ 496.052633] [<ffffffff812caf90>] ? cic_free_func+0x0/0x90 Mar 5 22:12:17 major kernel: [ 496.054976] [<ffffffff812c8294>] ? __call_for_each_cic+0x34/0x50 Mar 5 22:12:17 major kernel: [ 496.057143] [<ffffffff812bb90d>] ? put_io_context+0x4d/0x60 Mar 5 22:12:17 major kernel: [ 496.059273] [<ffffffff8106a302>] do_exit+0x2c2/0x3f0 Mar 5 22:12:17 major kernel: [ 496.061397] [<ffffffff815b4b43>] oops_end+0xf3/0x100 Mar 5 22:12:17 major kernel: [ 496.063503] [<ffffffff8100fc3b>] die+0x5b/0x90 Mar 5 22:12:17 major kernel: [ 496.065648] [<ffffffff815b4200>] do_trap+0x140/0x160 Mar 5 22:12:17 major kernel: [ 496.067779] [<ffffffffa00f3d80>] ? ttm_bo_ref_bug+0x0/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 496.070047] [<ffffffff8100d905>] do_invalid_op+0x95/0xb0 Mar 5 22:12:17 major kernel: [ 496.072160] [<ffffffffa00f3d89>] ? ttm_bo_ref_bug+0x9/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 496.072163] [<ffffffff8104bc3f>] ? account_entity_dequeue+0x7f/0xb0 Mar 5 22:12:17 major kernel: [ 496.072165] [<ffffffff812d5e7f>] ? rb_erase+0xbf/0x140 Mar 5 22:12:17 major kernel: [ 496.072167] [<ffffffff8100cc9b>] invalid_op+0x1b/0x20 Mar 5 22:12:17 major kernel: [ 496.072173] [<ffffffffa00f3d80>] ? ttm_bo_ref_bug+0x0/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 496.072177] [<ffffffffa00f6801>] ? ttm_bo_global_show+0x21/0x30 [ttm] Mar 5 22:12:17 major kernel: [ 496.072181] [<ffffffffa00f3d89>] ? ttm_bo_ref_bug+0x9/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 496.072184] [<ffffffff812d31be>] kref_sub+0x3e/0x80 Mar 5 22:12:17 major kernel: [ 496.072188] [<ffffffffa00f5048>] ttm_bo_list_ref_sub+0x28/0x30 [ttm] Mar 5 22:12:17 major kernel: [ 496.072192] [<ffffffffa00f67c8>] ttm_bo_reserve+0x88/0xa0 [ttm] Mar 5 22:12:17 major kernel: [ 496.072206] [<ffffffffa0154858>] radeon_unpin_work_func+0x28/0xb0 [radeon] Mar 5 22:12:17 major kernel: [ 496.072209] [<ffffffff810813ce>] process_one_work+0x10e/0x390 Mar 5 22:12:17 major kernel: [ 496.072221] [<ffffffffa0154830>] ? radeon_unpin_work_func+0x0/0xb0 [radeon] Mar 5 22:12:17 major kernel: [ 496.072223] [<ffffffff8108221d>] worker_thread+0xdd/0x260 Mar 5 22:12:17 major kernel: [ 496.072225] [<ffffffff81082140>] ? worker_thread+0x0/0x260 Mar 5 22:12:17 major kernel: [ 496.072227] [<ffffffff81086277>] kthread+0x97/0xa0 Mar 5 22:12:17 major kernel: [ 496.072229] [<ffffffff8100ce24>] kernel_thread_helper+0x4/0x10 Mar 5 22:12:17 major kernel: [ 496.072231] [<ffffffff810861e0>] ? kthread+0x0/0xa0 Mar 5 22:12:17 major kernel: [ 496.072233] [<ffffffff8100ce20>] ? kernel_thread_helper+0x0/0x10 Mar 5 22:12:17 major kernel: [ 496.072234] Code: 1f 44 00 00 65 48 8b 04 25 40 cc 00 00 48 8b 80 48 03 00 00 8b 40 f0 c9 c3 66 90 55 48 89 e5 0f 1f 44 00 00 48 8b 87 48 03 00 00 <48> 8b 40 f8 c9 c3 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 0f Mar 5 22:12:17 major kernel: [ 496.072246] RIP [<ffffffff81085f30>] kthread_data+0x10/0x20 Mar 5 22:12:17 major kernel: [ 496.072248] RSP <ffff8802277eb9a8> Mar 5 22:12:17 major kernel: [ 496.072249] CR2: fffffffffffffff8 Mar 5 22:12:17 major kernel: [ 496.072250] ---[ end trace eb6ea5ab08ebf6fa ]--- Mar 5 22:12:17 major kernel: [ 496.072251] Fixing recursive fault but reboot is needed! root@major:/home/dg# -- 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 34740] New: Invalid EDID on NEC 225WNX
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=34740 Summary: Invalid EDID on NEC 225WNX 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: freiheits(a)mail.ru Created an attachment (id=43837) --> (https://bugs.freedesktop.org/attachment.cgi?id=43837) dmesg log i have a NEC MultiSync 225WNX display, and ATI Radeon 9800 Pro (R350) AGP with 2_6_37 it works, but in the log I find error and after loading, KDE offers me set the screen resolution settings manually. [ 23.745086] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 24.438301] start_kdeinit (2339): /proc/2339/oom_adj is deprecated, please use /proc/2339/oom_score_adj instead. [ 30.772338] ata3.00: configured for UDMA/133 [ 30.772344] ata3: EH complete [ 31.570015] eth0: no IPv6 routers present [ 31.885279] EXT4-fs (sda2): re-mounted. Opts: acl,user_xattr,commit=0 [ 31.979079] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 32.044963] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 32.140389] EXT4-fs (sda3): re-mounted. Opts: commit=0 [ 43.879049] i2c i2c-0: readbytes: ack/nak timeout [ 43.879122] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 52.805480] bootsplash: status on console 0 changed to on [ 209.310829] fuse init (API version 7.15) [ 401.118127] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 15

[Bug 34632] New: RV300 clutter test_texture_pick_with_alpha: assertion failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=34632 Summary: RV300 clutter test_texture_pick_with_alpha: assertion failed 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: py(a)luyten.fr Created an attachment (id=43721) --> (https://bugs.freedesktop.org/attachment.cgi?id=43721) standalone test output I use jhbuild to build gnome-shell. Clutter module compiles fine but when I make check , then the "test_texture_pick_with_alpha" fails . ERROR:test-clutter-texture.c:65:test_texture_pick_with_alpha: assertion failed: (actor == CLUTTER_ACTOR (tex)) Aborted (core dumped) ATI card : radeon 9600 GL_VENDOR: X.Org R300 Project GL_RENDERER: Gallium 0.4 on RV350 GL_VERSION: 2.1 Mesa 7.9 The output 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 1

[Bug 34626] New: Mesa-Gallium with R600 - Framerate limited to 60 fps after suspend-cycle
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=34626 Summary: Mesa-Gallium with R600 - Framerate limited to 60 fps after suspend-cycle Product: DRI Version: XOrg CVS Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: peterle(a)hottemptation.org Hello, I past I thought this is a bug of IOQuake3, but during switching between Mesa-Classic and Mesa-Gallium I recognized, that the problem only exists with Mesa-Gallium! Reproduce: 1. $export vblank_mode=0 // switching of vsync 2. Launch an IOQuake3 based game (Quake3 Arena, OpenArena, World of Padman...) 3. check that VSYNC in IOQuake3 is also disabled! 4. Start a game and set "cg_drawpfs 1", know you should have at the top right corner a display with your current framerate which is hopefully over 60 fps 5. switch to a tty during playing (should be no problem with Kernel-Mode-Setting) 6. #pm-suspend (as root) 7. resume from suspend 8. switch back to X11/IOQuake3 -> framerate is limited to 60 fps To fix this you have to relaunch IOQuake3 or simply type into quake-console "vid_restart". With Mesa-Classic and the R600-Driver this is not necessary, it displays always the maximum possible framerate. Maybe Gallium doesn't read or forget the environment-variable export_vblank during resume from suspend? -- 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 34313] New: RV770 lock-up with OpenGL
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=34313 Summary: RV770 lock-up with OpenGL Product: Mesa Version: 7.7 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rah(a)bash.sh Created an attachment (id=43405) --> (https://bugs.freedesktop.org/attachment.cgi?id=43405) X server log I get the following GPU lock-up report with many different OpenGL programs, but in this instance Stellarium. ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x38f/0x3f0 [radeon]() Hardware name: P5Q GPU lockup (waiting for 0x000CAA2E last fence id 0x000CAA28) Modules linked in: usb_storage cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_ondemand freq_table lirc_serial(C) lirc_dev sco bnep rfcomm l2cap crc16 binfmt_misc ip6t_LOG ip6table_filter ip6_tables fuse nfsd exportfs nls_iso8859_1 nls_cp437 vfat fat coretemp loop dm_crypt snd_hda_codec_hdmi radeon snd_hda_codec_realtek ttm snd_emu10k1_synth snd_hda_intel snd_emux_synth snd_hda_codec snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_ac97_codec ac97_bus snd_util_mem snd_pcm_oss snd_hwdep snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi snd_pcm snd_rawmidi gspca_pac207 gspca_main videodev v4l1_compat drm_kms_helper drm snd_seq_midi_event v4l2_compat_ioctl32 snd_page_alloc 8250_pnp snd_seq snd_timer snd_seq_device snd btusb pcspkr i2c_i801 asus_atk0110 bluetooth emu10k1_gp soundcore 8250 gameport evdev serial_core dm_mod usbhid hid sg uhci_hcd sr_mod cdrom atl1e firewire_ohci firewire_core crc_itu_t via_rhine mii ehci_hcd [last unloaded: scsi_wait_scan] Pid: 2992, comm: Xorg Tainted: G WC 2.6.37-linux-2.6-latest-32 #10 Call Trace: [<ffffffff8103c8fb>] ? warn_slowpath_common+0x7b/0xc0 [<ffffffff8103c9f5>] ? warn_slowpath_fmt+0x45/0x50 [<ffffffffa0461b1f>] ? radeon_fence_wait+0x38f/0x3f0 [radeon] [<ffffffff81057740>] ? autoremove_wake_function+0x0/0x30 [<ffffffffa00f90c9>] ? ttm_bo_wait+0x119/0x1d0 [ttm] [<ffffffffa0478b8e>] ? radeon_gem_wait_idle_ioctl+0x8e/0x110 [radeon] [<ffffffffa01fa331>] ? drm_ioctl+0x3c1/0x440 [drm] [<ffffffffa0478b00>] ? radeon_gem_wait_idle_ioctl+0x0/0x110 [radeon] [<ffffffff8100d772>] ? save_i387_xstate+0x92/0x210 [<ffffffff810022df>] ? do_signal+0x19f/0x800 [<ffffffff810e7a5f>] ? do_vfs_ioctl+0x9f/0x550 [<ffffffff8100d538>] ? restore_i387_xstate+0x148/0x1d0 [<ffffffff810e7f90>] ? sys_ioctl+0x80/0xa0 [<ffffffff81002dbb>] ? system_call_fastpath+0x16/0x1b ---[ end trace 37e82fba971a1173 ]--- -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 29

[Bug 33969] New: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33969 Summary: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds 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: adam.rak(a)streamnovation.com Created an attachment (id=42998) --> (https://bugs.freedesktop.org/attachment.cgi?id=42998) Full dmesg after the crash Hardware is Fusion Zacate APU (HD6310) Mesa is commit ec96b0ecdbe723f4664188010c7f86d5d7f41d82 checkout ddx is commit a4899db96029acde6cd400fc0541693a487898e7 checkout linux kernel is 2.6.38-rc3 commit 44f2c5c841da1b1e0864d768197ab1497b5c2cc1 X.Org X Server 1.7.7 (debian squeeze) Running nexuiz crashes the X when entering play mode. (no apparent error log) Running(and playing) extremetuxracer produces a kernel oops after a few seconds, the dmesg is in the attachment. -- 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 33681] New: Random system lockup with KMS, Mobility Radeon HD3470
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33681 Summary: Random system lockup with KMS, Mobility Radeon HD3470 Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jsagarribay(a)gmail.com Created an attachment (id=42685) --> (https://bugs.freedesktop.org/attachment.cgi?id=42685) kernel log The computer often locks itself, the panel suddenly loses the image (it sometimes blooms, or get filled with a solid color or a pattern of vertical white and grey stripes). I don't know how to trigger the bug, it can happen anytime, even with an idle system. It has happened to me since I started using KMS, it was stable both with radeonHD and radeon drivers in UMS mode. The frequency of the problem has varied a lot; with the first KMS versions it happened a lot, then it seemed to be fixed with some kernel versions, but reappeared with others... As the problem is random, it can happen after a few minutes of uptime, or after some hours, or not happen at all. At first, I thougth the kernel was completely dead, but I recently found out that I can use SysRq+S and SysRq+T to get some logs. If I try to reboot with SysRq+B the system locks fully and doesn't react to anything, I always have to do a hard reboot. I'll attach lspci, one X log and three differen kernel logs. -- 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 33301] New: dynpm doesn't downclock
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33301 Summary: dynpm doesn't downclock Product: DRI Version: XOrg 6.7.0 Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: cristiklein(a)gmail.com Hello, I have an ATI Mobility Radeon HD 2400. I am using Linux 2.6.37. Currently, dynpm does not down-clock the GPU for me. dmesg is filled with the following messages: [245199.552075] [drm:r600_pm_get_dynpm_state], Requested: e: 30000 m: 40000 p: 16 (about 10 messages / second) I attach a script with all the necessary details. Cristi. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2011