dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 32325] New: [radeon] DRM version check only looks at minor number.
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=32325 Summary: [radeon] DRM version check only looks at minor number. Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rankincj(a)googlemail.com Created an attachment (id=41020) View: https://bugs.freedesktop.org/attachment.cgi?id=41020 Review: https://bugs.freedesktop.org/review?bug=32325&attachment=41020 [PATCH] Enable HyperZ and microtiling for R100 if DRM >= v2.x I have noticed that Mesa 7.9 prints the following message with a recent 2.6.3x kernel: "DRM version 1.6 too old to support HyperZ, disabling." The reason for this is that the DRM in the 2.6.36 kernel is v2.6: [drm] Initialized radeon 2.6.0 20080528 for 0000:01:00.0 on minor 0 and Mesa only checks the minor version number. (Assuming that the major version number is always 1.) I have attached a patch that will also enable both HyperZ and texture microtiling(?) on R100 if DRM >= v2.x. -- 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 30924] New: incorrect checking of return value of driAllocateTexture
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=30924 Summary: incorrect checking of return value of driAllocateTexture Product: Mesa Version: 7.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ssb(a)umn.edu driAllocateTexture returns -1 for failure to allocate the texture. The code checks against NULL. [driAllocateTexture:631] unable to allocate texture Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef15b] 1: /usr/bin/X (0x8048000+0x5cff5) [0x80a4ff5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe410] 3: /usr/lib/dri/radeon_dri.so (0xb433a000+0x381bf) [0xb43721bf] 4: /usr/lib/libdrm_radeon.so.1 (radeon_cs_emit+0x14) [0xb70973d4] 5: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35c78) [0xb436fc78] 6: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35d2c) [0xb436fd2c] 7: /usr/lib/dri/radeon_dri.so (0xb433a000+0x35f32) [0xb436ff32] 8: /usr/lib/dri/radeon_dri.so (0xb433a000+0x17e0a) [0xb4351e0a] 9: /usr/lib/dri/radeon_dri.so (0xb433a000+0x75ccb) [0xb43afccb] 10: /usr/lib/dri/radeon_dri.so (0xb433a000+0x17b3c8) [0xb44b53c8] 11: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x83a0) [0xb71bf3a0] 12: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x31c45) [0xb71e8c45] 13: /usr/lib/xorg/modules/extensions/libglx.so (0xb71b7000+0x3645e) [0xb71ed45e] 14: /usr/bin/X (0x8048000+0x23707) [0x806b707] 15: /usr/bin/X (0x8048000+0x1dbb5) [0x8065bb5] 16: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7333a66] 17: /usr/bin/X (0x8048000+0x1d781) [0x8065781] Segmentation fault at address 0x14 -- 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 37471] New: Website with information about maintainers/developers
by bugzilla-daemon＠freedesktop.org 29 May '19

29 May '19

https://bugs.freedesktop.org/show_bug.cgi?id=37471 Summary: Website with information about maintainers/developers Product: DRI Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de There should be a website with information about main developers/maintainers: Product (DRM Intel, DRM Radeon, Mesa) | Component[s] (Maintainer, Core developer, Intel, R200, R300, R600, nouveau, ...) | Real Name | eMail | Name on IRC | Usual time to ask (e.g. 17 to 20 UTC) | Available on IRC channels (#dri-devel, #nouveau, ...) | Working for [Red Hat, SUSE, Linux Foundation, Ubuntu, ...] -- 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 56666] New: AMD SUMO GPU lockup when launching any heavy 3D application
by bugzilla-daemon＠freedesktop.org 25 Aug '18

25 Aug '18

https://bugs.freedesktop.org/show_bug.cgi?id=56666 Priority: medium Bug ID: 56666 Assignee: dri-devel(a)lists.freedesktop.org Summary: AMD SUMO GPU lockup when launching any heavy 3D application Severity: critical Classification: Unclassified OS: Linux (All) Reporter: runetmember(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 69423 --> https://bugs.freedesktop.org/attachment.cgi?id=69423&action=edit AMD SUMO GPU lockup when I launch Unigine Heaven 3 GPU lockup happen for me while launching any heavy 3D application on Radeon HD 6620G. For example GPU lockup 100% reproducible when I launch Unigine Heaven 3 (dmesg attached). It also may happen in web-browser, if browser use rendering hardware acceleration (for example Firefox with enabled "layers.acceleration.force-enabled" option). Lockup is not reproducible when I launch same applications on discrete Radeon HD 6650M GPU using DRI_PRIME feature, so I guess my issue related to AMD SUMO GPU's (or maybe to more APU's). Software: Kubuntu 12.10 x86_64 updated from Xorg Edgers PPA. Linux 3.7rc3. With Linux 3.5 and 3.6 is also reproducible, Mesa: 9.1~git20121029.00e6819e libdrm-radeon1: git20121025.bc494b31 xserver-xorg-video-radeon: git20120928.e8cb0b72 xserver-xorg-core: 1.13.0+git20120920.70e57668 KDE 4.9.2, desktop effects enabled. Hardware: Acer Aspire 7560G laptop, BIOS 2.04, AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO) Discrete AMD Radeon HD 6650M (TURKS) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[PATCH wq#for-linus] drm: fix a fallout from slow-work -> wq conversion
by Tejun Heo 19 Jun '18

19 Jun '18

Commit 991ea75c (drm: use workqueue instead of slow-work), which made drm to use wq instead of slow-work, didn't account for the return value difference between delayed_slow_work_enqueue() and queue_delayed_work(). The former returns 0 on success and -errno on failures while the latter never fails and only uses the return value to indicate whether the work was already pending or not. This misconversion triggered spurious error messages. Remove the now unnecessary return value check and error message. Signed-off-by: Tejun Heo <tj(a)kernel.org> Reported-by: Markus Trippelsdorf <markus(a)trippelsdorf.de> Cc: David Airlie <airlied(a)linux.ie> Cc: dri-devel(a)lists.freedesktop.org --- Markus, it's almost trivial but it would be great if you can test this one too. David, may I route this wq#for-linus? Thanks. drivers/gpu/drm/drm_crtc_helper.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc_helper.c b/drivers/gpu/drm/drm_crtc_helper.c index 4598130..211ed7e 100644 --- a/drivers/gpu/drm/drm_crtc_helper.c +++ b/drivers/gpu/drm/drm_crtc_helper.c @@ -839,7 +839,6 @@ static void output_poll_execute(struct work_struct *work) struct drm_connector *connector; enum drm_connector_status old_status, status; bool repoll = false, changed = false; - int ret; mutex_lock(&dev->mode_config.mutex); list_for_each_entry(connector, &dev->mode_config.connector_list, head) { @@ -874,11 +873,8 @@ static void output_poll_execute(struct work_struct *work) dev->mode_config.funcs->output_poll_changed(dev); } - if (repoll) { - ret = queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); - if (ret) - DRM_ERROR("delayed enqueue failed %d\n", ret); - } + if (repoll) + queue_delayed_work(system_nrt_wq, delayed_work, DRM_OUTPUT_POLL_PERIOD); } void drm_kms_helper_poll_disable(struct drm_device *dev)

4 4

[Bug 28771] New: Vsync always on
by bugzilla-daemon＠freedesktop.org 12 Jun '18

12 Jun '18

https://bugs.freedesktop.org/show_bug.cgi?id=28771 Summary: Vsync always on Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se With kernel 2.6.35, there doesn't seem to be a way to turn off vsync/vblank. E.g. "vblank_mode=0 glxgears" has no effect. This seems to be the same for both r300c and r300g. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: RV570 -- Model: Asus EAX1950Pro 256MB -- Display connector: DVI -- xf86-video-ati: 801e83227a59a29eea425ea612083bbf2b536c30 -- xserver: 1.8.1.901 -- mesa: a5c44986a3f19936df448fe4ae47ca77ece9b0ce -- drm: 6ea2bda5f5ec8f27359760ce580fdad3df0464df -- kernel: 2.6.35-rc3 -- 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 48424] New: Fix warnings/errors reported by clang's scan-build tool
by bugzilla-daemon＠freedesktop.org 12 Apr '18

12 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=48424 Bug #: 48424 Summary: Fix warnings/errors reported by clang's scan-build tool Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) URL: https://gitorious.org/jobermayr/scan-build-mesa OS/Version: All Status: NEW Severity: normal Priority: medium Component: Mesa core AssignedTo: mesa-dev(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de CC: dri-devel(a)lists.freedesktop.org, nouveau(a)lists.freedesktop.org https://gitorious.org/jobermayr/scan-build-mesa ~ 8 MB to download, 680 MB on disk. Please report false positives here. I will forward them. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 59681] New: Sony VAIO VPCZ23A4R: radeon doesn't like undocking
by bugzilla-daemon＠bugzilla.kernel.org 25 Mar '18

25 Mar '18

https://bugzilla.kernel.org/show_bug.cgi?id=59681 Summary: Sony VAIO VPCZ23A4R: radeon doesn't like undocking Product: Drivers Version: 2.5 Kernel Version: 3.10-rc5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: patrakov(a)gmail.com Regression: No Created an attachment (id=104661) --> (https://bugzilla.kernel.org/attachment.cgi?id=104661) The end of the dmesg I have a Sony VAIO VPCZ23A4R laptop. It has a dock station with several devices in it: # lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06) 08:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 0a:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 0a:03.0 PCI bridge: Intel Corporation Device 151b (rev 01) 0a:04.0 PCI bridge: Intel Corporation Device 151b (rev 01) 14:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 15:03.0 PCI bridge: Intel Corporation Device 151b (rev 01) 15:04.0 PCI bridge: Intel Corporation Device 151b (rev 01) 16:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] 16:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks/Whistler HDMI Audio [Radeon HD 6000 Series] 17:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:01.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:02.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:03.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:04.0 PCI bridge: Intel Corporation Device 151b (rev 01) 19:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06) 1a:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II / PATA Controller (rev b2) 1b:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) aep-vaio ~ # lspci -n 00:00.0 0600: 8086:0104 (rev 09) 00:02.0 0300: 8086:0126 (rev 09) 00:16.0 0780: 8086:1c3a (rev 04) 00:1a.0 0c03: 8086:1c2d (rev 04) 00:1b.0 0403: 8086:1c20 (rev 04) 00:1c.0 0604: 8086:1c10 (rev b4) 00:1c.1 0604: 8086:1c12 (rev b4) 00:1c.2 0604: 8086:1c14 (rev b4) 00:1c.3 0604: 8086:1c16 (rev b4) 00:1c.6 0604: 8086:1c1c (rev b4) 00:1d.0 0c03: 8086:1c26 (rev 04) 00:1f.0 0601: 8086:1c4b (rev 04) 00:1f.2 0104: 8086:282a (rev 04) 00:1f.3 0c05: 8086:1c22 (rev 04) 02:00.0 0280: 8086:0091 (rev 34) 03:00.0 ff00: 10ec:5209 (rev 01) 04:00.0 0c03: 1033:0194 (rev 04) 05:00.0 0200: 10ec:8168 (rev 06) 08:00.0 0604: 8086:151b (rev 01) 0a:00.0 0604: 8086:151b (rev 01) 0a:03.0 0604: 8086:151b (rev 01) 0a:04.0 0604: 8086:151b (rev 01) 14:00.0 0604: 8086:151b (rev 01) 15:03.0 0604: 8086:151b (rev 01) 15:04.0 0604: 8086:151b (rev 01) 16:00.0 0300: 1002:6740 16:00.1 0403: 1002:aa90 17:00.0 0604: 8086:151b (rev 01) 18:00.0 0604: 8086:151b (rev 01) 18:01.0 0604: 8086:151b (rev 01) 18:02.0 0604: 8086:151b (rev 01) 18:03.0 0604: 8086:151b (rev 01) 18:04.0 0604: 8086:151b (rev 01) 19:00.0 0200: 10ec:8168 (rev 06) 1a:00.0 0101: 11ab:6121 (rev b2) 1b:00.0 0c03: 1033:0194 (rev 04) Devices up to and including 05:00.0 are in the laptop itself, and everything below is in the dock station. I have tested the laptop with linux-3.10-rc5 with this patch series applied: https://lkml.org/lkml/2013/6/13/349 The testcase is: boot with the dock station attached, let Xorg start (it will use both Intell and Radeon cards), switch to a virtual console, press the Undock button. Yes I know that GPU hotplug is not yet supported in Xorg, but attempting it should not lead to messages like "kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1591!" The part of the dmesg after the undocking attempt, captured over netconsole, is attached to this bug. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 4

[Bug 42941] New: Resume from suspend to memory leaves display blank on Lenovo Ideapad U455
by bugzilla-daemon＠bugzilla.kernel.org 07 Mar '18

07 Mar '18

https://bugzilla.kernel.org/show_bug.cgi?id=42941 Summary: Resume from suspend to memory leaves display blank on Lenovo Ideapad U455 Product: Power Management Version: 2.5 Kernel Version: 3.3.0-rc7+ Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Hibernation/Suspend AssignedTo: power-management_other(a)kernel-bugs.osdl.org ReportedBy: e-mail(a)date.by CC: drivers_video-dri(a)kernel-bugs.osdl.org Regression: No Created an attachment (id=72610) --> (https://bugzilla.kernel.org/attachment.cgi?id=72610) dmesg output Hardware: Lenovo Ideapad U455 laptop with AMD Athlon Neo processor and two video cards: Radeon HD 3200 and Radeon HD 4500. Description: when system resumes from suspend to memory (`echo mem > /sys/power/state`) system resumes fine as i can log into it via ssh and display turns on, but the display stays black showing nothing. However it's possible to make display show a picture by switching video cards with vga_switcheroo. Steps to reproduce attached dmesg log (see my comments below): [1]# mount -t debugfs none /sys/kernel/debug [2]# cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:01:05.0 1:DIS: :Pwr:0000:02:00.0 [3]# echo mem > /sys/power/state [4]# cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:01:05.0 1:DIS: :Pwr:0000:02:00.0 [5]# echo DIS > /sys/kernel/debug/vgaswitcheroo/switch [6]# echo IGD > /sys/kernel/debug/vgaswitcheroo/switch [7]# cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:01:05.0 1:DIS: :Off:0000:02:00.0 [8]# echo mem > /sys/power/state [9]# cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:01:05.0 1:DIS: :Off:0000:02:00.0 [10]# echo DIS > /sys/kernel/debug/vgaswitcheroo/switch [11]# echo IGD > /sys/kernel/debug/vgaswitcheroo/switch Comments: [2] This shows the state of the video cards before suspend. [3] Suspend worked fine, but display was blank after resume. [4] This shows the state of the video cards after resume. [5] That command made display to show the picture. [7] This shows the state of the video cards before second suspend, when only IGD card was active. [8] Suspend worked fine, but resume took a lot of time: PM: resume devices took 82.256 seconds ------------[ cut here ]------------ WARNING: at kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90() Hardware name: 20046 Component: resume devices, time: 82256 Modules linked in: btusb bluetooth snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 ext2 mbcache cpufreq_ondemand powernow_k8 freq_table mperf lp parport_pc parport fuse radeon brcmsmac ttm mac80211 drm_kms_helper joydev snd_hda_codec_hdmi ohci_hcd snd_hda_codec_conexant brcmutil ssb snd_hda_intel drm mmc_core snd_hda_codec sp5100_tco cfg80211 sg ideapad_laptop agpgart psmouse atl1c thermal snd_hwdep processor video crc8 thermal_sys pcmcia snd_pcm snd_timer cordic rtc_cmos pcmcia_core shpchp sparse_keymap evdev ehci_hcd i2c_piix4 snd k8temp i2c_algo_bit bcma rfkill i2c_core serio_raw soundcore snd_page_alloc battery ac hwmon button loop btrfs [last unloaded: pcmcia_rsrc] Pid: 1834, comm: bash Not tainted 3.3.0-rc7+ #36 Call Trace: [<ffffffff8103fe3f>] warn_slowpath_common+0x7f/0xc0 [<ffffffff8103ff36>] warn_slowpath_fmt+0x46/0x50 [<ffffffff8107fc96>] suspend_test_finish+0x86/0x90 [<ffffffff8107f9a1>] suspend_devices_and_enter+0x101/0x1e0 [<ffffffff8107fb51>] enter_state+0xd1/0x110 [<ffffffff8107e4c7>] state_store+0xb7/0x130 [<ffffffff812623cf>] kobj_attr_store+0xf/0x30 [<ffffffff811b0d22>] sysfs_write_file+0xf2/0x180 [<ffffffff81149793>] vfs_write+0xb3/0x180 [<ffffffff81149aba>] sys_write+0x4a/0x90 [<ffffffff8153f829>] system_call_fastpath+0x16/0x1b ---[ end trace 6802c35567ce73fa ]--- PM: Finishing wakeup. [9] This shows the state of the video cards after second resume. [10] That command turned display off and that's what appeared in dmesg output: radeon: switched on radeon 0000:02:00.0: enabling device (0000 -> 0003) radeon 0000:02:00.0: Wait for MC idle timedout ! radeon 0000:02:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). radeon 0000:02:00.0: WB enabled [drm] fence driver on ring 0 use gpu addr 0x20000c00 and cpu addr 0xffff8800a4523c00 [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8500)=0xFFFFFFFF) [drm:rv770_resume] *ERROR* r600 startup failed on resume fbcon: Remapping primary device, fb1, to tty 1-63 radeon: switched off [11] That command made display to show the picture. Notes: * I have read Documentation/power/basic-pm-debugging.txt and made all described tests and all of them were successful. * I have tried different quirks with `pm-suspend --quirk-*`, but none of them helped. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.

1 3

[Bug 50325] New: Glyphy bad render on r600g (software render is fine)
by bugzilla-daemon＠freedesktop.org 06 Mar '18

06 Mar '18

https://bugs.freedesktop.org/show_bug.cgi?id=50325 Bug #: 50325 Summary: Glyphy bad render on r600g (software render is fine) Classification: Unclassified Product: Mesa Version: 8.0 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: edwin+mesa(a)etorok.net Created attachment 62078 --> https://bugs.freedesktop.org/attachment.cgi?id=62078 apitrace (cf. https://github.com/apitrace/apitrace/tree/1.0) I just tried Glyphy on r600g and the output is very bad. Don't know if its Glyphy bug or Mesa bug, but if I force software rendering in Mesa then I do see the output. Attached screenshots of bad (r600g) and good (software render). The bad render was obtained by: demo/glyphy-demo The good one: LIBGL_ALWAYS_SOFTWARE=1 demo/glyphy-demo I tested on: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL version string: 2.1 Mesa 8.0.2 OpenGL shading language version string: 1.20 I'll try to test on mesa git later to see if its still an issue there. Also attached is a an apitrace, and the bad render can be reproduced with: build/glretrace lt-glyphy-demo.trace The good render (initialization a bit slow, but works): LIBGL_ALWAYS_SOFTWARE=1 build/glretrace lt-glyphy-demo.trace The source code for Glyphy can be found here: https://code.google.com/p/glyphy/source/checkout -- 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

← Newer
1
...
19
20
21
22
23
24
25
...
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