dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 61941] New: Random GPU lockups/resets on Mobility Radeon HD 3650 with radeon.dpm=1
by bugzilla-daemon＠bugzilla.kernel.org 19 Aug '16

19 Aug '16

https://bugzilla.kernel.org/show_bug.cgi?id=61941 Bug ID: 61941 Summary: Random GPU lockups/resets on Mobility Radeon HD 3650 with radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: >=3.11.0 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: itumaykin(a)gmail.com Regression: No Created attachment 109311 --> https://bugzilla.kernel.org/attachment.cgi?id=109311&action=edit lspci -vvv Hello. I have 3.11 kernel with radeon.dpm enabled via kernel boot option. Sometimes under unknown circumstances my GPU resets. It happens seldom and randomly during a common desktop workflow: web browsing, document typing, video playback. No games or video benchmarks or any other GPU-eating stuff. During such lockup my screen turns black, but backlight is still on. After a while image reappears, though it is blurry and after 10-15 seconds my screen is back to normal state completely. Also sometimes after such reset I am able to continue working, but sometimes screen is stuck with one image that appeared after screen restoration and I have to reboot machine to fix this. Everything else seems to work fine during lockups, for example music is playing without any problems. I can't say for sure, but it looks like this bug happens more often when some video is played in Firefox. (JIC: I don't have Adobe Flash installed.) My OS is Gentoo amd64 with vanilla kernel 3.11.{0,1}. And this happens with power_dpm_state set to "balanced". I've attached two dmesg outputs after such lockups. I do understand that it is probably too vague description to fix this and I am ready to provide any other additional info. -- You are receiving this mail because: You are watching the assignee of the bug.

1 25

[Bug 81382] New: Text console blanking does not go away
by bugzilla-daemon＠freedesktop.org 15 Aug '16

15 Aug '16

https://bugs.freedesktop.org/show_bug.cgi?id=81382 Priority: medium Bug ID: 81382 Assignee: dri-devel(a)lists.freedesktop.org Summary: Text console blanking does not go away Severity: normal Classification: Unclassified OS: All Reporter: vda.linux(a)googlemail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 102847 --> https://bugs.freedesktop.org/attachment.cgi?id=102847&action=edit dmesg I log in as root on a text virtual console. After about 10 minutes screen blanks. Surprisingly, pressing a key does *not* unblank the screen! Machine is still alive (I can ssh into it), and typed keys even reach the console: I can type e.g. "ls -lR /usr" and I see disk indicator blinking, ls process is visible in the ps in ssh session, etc. This does not happen in X. This is observed on Lenovo T60, on RHEL7 kernel and also on recent upstream kernel 3.15.5. Investigation had revealed that VT unblanking code, after all the hard work it done to turn display back on, calls ATOM_LCD_BLOFF (backlight off, numeric value 2) function. Digging further, I discovered that fb_blank(blank=0) almost at its end calls fb_notifier_call_chain(FB_EVENT_BLANK). Which calls backlight.c::fb_notifier_callback(), which tries to set brightness via radeon_atom_backlight_update_status(), which does atombios_set_backlight_level(radeon_atom_bl_level()), but radeon_atom_bl_level() is zero (it's an uint8_t, brightness level). So it's essentially atombios_set_backlight_level(0) and it switches backlight off. In drivers/gpu/drm/radeon/*, bd->props.brightness, surprisingly, is only set in radeon_atom_backlight_init() and radeon_legacy_backlight_init(), all other locations are only reading it. So, if this init code sets it to 0, then VT unblanking code will use this zero value as brightness to restore, causing this bug. And indeed, that's what happens on the machine exhibiting this bug: [ 2.301563] radeon_atom_get_backlight_level_from_reg: RADEON_BIOS_2_SCRATCH [ 2.301633] radeon_atom_get_backlight_level_from_reg: bios_2_scratch:00000000 [ 2.301704] radeon_atom_backlight_init: bd->props.brightness=0 [ 2.301780] radeon_atom_backlight_update_status: atombios_set_back The full dmesg of the RHEL7 boot with many debug printks added is attached. (Sorry, I started debugging it on RHEL7, I believe mainline does not differ significantly). It shows the following: After "setterm -blank 1 && sleep 60", VT blanking triggers at ~362 seconds, and at ~370 seconds VT is trying to unblank because of keyboard activity. The bug is evident here: [ 370.852058] fb_blank: fb_notifier_call_chain(FB_EVENT_BLANK)... [ 370.852061] fbcon_event_notify: case FB_EVENT_BLANK: fbcon_fb_blanked(blank:0) [ 370.852063] fbcon_fb_blanked: do_unblank_screen(0) [ 370.852064] do_unblank_screen: entered on cpu 0 [ 370.852066] do_unblank_screen: !console_blanked on cpu 0 [ 370.852068] backlight: drivers/video/backlight/backlight.c:fb_notifier_callback: backlight_update_status() [ 370.852071] radeon_atom_backlight_update_status: atombios_set_backlight_level() [ 370.852072] radeon_atom_bl_level: level = bd->props.brightness:0 [ 370.852074] atombios_set_backlight_level(level:0) [ 370.852077] atombios_set_backlight_level: atom_execute_table(ATOM_LCD_BLOFF) ^^^^^^^^^^^^^^^^^^^^ THIS TURNS OFF DISPLAY ^^^^^^^^^^^^^^^^^ [ 370.852083] atom_execute_table_locked(index:23,*params:ffff8802) returns 0 [ 370.852085] backlight: drivers/video/backlight/backlight.c:fb_notifier_callback: backlight_update_status() [ 370.852940] fb_blank returns 0 [ 370.852942] fbcon_blank: update_screen()... [ 370.862313] do_unblank_screen: done on cpu 0 Note: PCI error seen during blanking is not causing this bug. It happens on first blanking (including Xserver screen blankings, which do not exhibit this bug), and never repeats. Google says it's a known issue on Radeon, comes from PCIe lanes reconfiguration. I am unsure how to proceed from here. Maybe init code needs fixing to properly read backlight brightness on this hardware? I think radeon people are more qualified to take it from here. I'm willing to test patches. -- You are receiving this mail because: You are the assignee for the bug.

1 45

[Bug 85241] New: audio over HDMI on AMD E-350 with radeon driver
by bugzilla-daemon＠bugzilla.kernel.org 15 Aug '16

15 Aug '16

https://bugzilla.kernel.org/show_bug.cgi?id=85241 Bug ID: 85241 Summary: audio over HDMI on AMD E-350 with radeon driver Product: Drivers Version: 2.5 Kernel Version: 3.14 and higher Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: wmyrda(a)auticon.pl Regression: No I have problem with HDMI and audio on my Asus AMD E-350 platform which started around kernel 3.14 with sigle error message "[drm:dce4_afmt_write_speaker_allocation] *ERROR* Couldn't read Speaker Allocation Data Block: 0" which become even more severe with kernels 3.15 & 3.16 as now logs are flooded with "sound hdaudioC0D0: HDMI ATI/AMD: no speaker allocation for ELD" My setup is PC with Asus E-350 connected directly to the TV with HDMI cable (it has been in the past to the 5.1 analog system hence the entry of "options snd-hda-intel model=3stack-6ch-dig" in /etc/modprobe.d/alsa.conf) on software side it is Gentoo with libdrm & mesa & xf86-video-ati --- git versions updated on the regular basis about every 1-2 weeks pulseaudio 5.0 xorg 1.16.1 here are some logs. If more info is needed please let me know dmesg 3.14.19 http://pastebin.com/AHyV1nRk Xorg.0.log http://pastebin.com/J66tUcU5 audio 3.16.3 http://www.alsa-project.org/db/?f=7e2075...92b0b5c23e audio 3.15.10 http://www.alsa-project.org/db/?f=bbb92a...14bd0bc831 audio 3.14.19 http://www.alsa-project.org/db/?f=5d2f93...2a7a6697a6 -- You are receiving this mail because: You are watching the assignee of the bug.

1 6

[Bug 84431] New: Kernel crash when unloading radeon module for switcheroo card
by bugzilla-daemon＠bugzilla.kernel.org 05 Aug '16

05 Aug '16

https://bugzilla.kernel.org/show_bug.cgi?id=84431 Bug ID: 84431 Summary: Kernel crash when unloading radeon module for switcheroo card Product: Drivers Version: 2.5 Kernel Version: all Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: pali.rohar(a)gmail.com Regression: No Created attachment 149991 --> https://bugzilla.kernel.org/attachment.cgi?id=149991&action=edit Fix crash after rmmod radeon on PX systems. Calling rmmod radeon on PX system cause kernel crash. Reason is function vga_switcheroo_init_domain_pm_ops() which setting dev->pm_domain function of PCI device. When radeon module is unloaded pointer dev->pm_domain is set to vga_switcheroo function which try to call radeon function (which does not exists in memory after rmmod radeon). I bet that nouveau has same problem. I'm attaching simple patch which set dev->pm_domain of PCI device back to NULL when removing radeon device so vga_switcheroo will not be called. But I think that proper way for fixing this bug - which is in vga_switcheroo - should be to add function like "vga_switcheroo_exit_domain_pm_ops()" which will set pm_domain back to origin value (which is in my case NULL). With my patch on PX system I can call rmmod radeon, modprobe radeon, rmmod radeon, ... many times without no crash. -- You are receiving this mail because: You are watching the assignee of the bug.

1 11

[Bug 64475] New: Slow work and low brightness in Euro Track Simulator II game with HD6850
by bugzilla-daemon＠freedesktop.org 29 Jul '16

29 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=64475 Priority: medium Bug ID: 64475 Assignee: dri-devel(a)lists.freedesktop.org Summary: Slow work and low brightness in Euro Track Simulator II game with HD6850 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: commiethebeastie(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 79172 --> https://bugs.freedesktop.org/attachment.cgi?id=79172&action=edit Euro Truck Simulator screenshot I tried to run the game with STEAM_RUNTIME="1" R600_LLVM=0 R600_HYPERZ=0 steam Driver "radeon" Option "SwapbuffersWait" "on" Option "ColorTiling" "off" Option "ColorTiling2D" "off" Option "EnablePageFlip" "on" Option "AccelMethod" "EXA" and STEAM_RUNTIME="1" R600_LLVM=1 R600_HYPERZ=1 R600_DEBUG=sb steam Driver "radeon" Option "SwapbuffersWait" "off" Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "EnablePageFlip" "off" Option "AccelMethod" "EXA" options But all times the game runs slowly and with low brightness. In the mirrors is visible to normal brightness. Also I can put apitrace file here. direct rendering: Yes OpenGL renderer string: Gallium 0.4 on AMD BARTS OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 (git-5471e39) OpenGL core profile shading language version string: 1.40 Linux localhost 3.9.0-next-20130509 #1 SMP PREEMPT Thu May 9 12:49:14 MSK 2013 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 62441] New: Bastion game runs slowly
by bugzilla-daemon＠freedesktop.org 15 Jul '16

15 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=62441 Priority: medium Bug ID: 62441 Assignee: dri-devel(a)lists.freedesktop.org Summary: Bastion game runs slowly Severity: normal Classification: Unclassified OS: All Reporter: lvella(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/DRI/R600 Product: Mesa Game Bastion (from Humble Indie Bundle V and Steam) runs very slowly on most parts, specially when the scene is full of special effects (rain, etc), rendering it unplayable. The only part where it runs at normal speed is at main menu and the very beginning of the game. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 62967] New: Game Dungeon Defenders crash my whole system.
by bugzilla-daemon＠freedesktop.org 15 Jul '16

15 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=62967 Priority: medium Bug ID: 62967 Assignee: dri-devel(a)lists.freedesktop.org Summary: Game Dungeon Defenders crash my whole system. Severity: normal Classification: Unclassified OS: All Reporter: lvella(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 77255 --> https://bugs.freedesktop.org/attachment.cgi?id=77255&action=edit glxinfo output When I run Dungeon Defenders, the game window pops up and the first intro animation runs very slowly (a red logo building in front of a white backgroud), then at the second animation, a seeming magic circle with purple fire, my computer halts and freezes completely, and I have to reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 75241] New: radeon_compute_pll_avivo broken in 3.15-rc3
by bugzilla-daemon＠bugzilla.kernel.org 05 Jul '16

05 Jul '16

https://bugzilla.kernel.org/show_bug.cgi?id=75241 Bug ID: 75241 Summary: radeon_compute_pll_avivo broken in 3.15-rc3 Product: Drivers Version: 2.5 Kernel Version: 3.15-rc3 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: clemens(a)ladisch.de Regression: Yes After upgrading from rc2 to rc3, my RS880 no longer outputs a signal that my monitor is able to show. Bisected to this: commit c2fb3094669a3205f16a32f4119d0afe40b1a1fd Author: Christian König <christian.koenig(a)amd.com> Date: Sun Apr 20 13:24:32 2014 +0200 drm/radeon: improve PLL limit handling in post div calculation This improves the PLL parameters when we work at the limits of the allowed ranges. Debug output with black screen: kernel: [drm:drm_crtc_helper_set_config] attempting to set mode from userspace kernel: [drm:drm_mode_debug_printmodeline] Modeline 29:"1600x1200" 60 162000 1600 1664 1856 2160 1200 1201 1204 1250 0x48 0x5 kernel: [drm:radeon_encoder_set_active_device] setting active device to 00000200 from 00000200 00000200 for encoder 2 kernel: [drm:drm_crtc_helper_set_mode] [CRTC:14] kernel: [drm:radeon_atom_encoder_dpms] encoder dpms 21 to mode 3, devices 00000001, active_devices 00000000 kernel: [drm:radeon_compute_pll_avivo] 162000 - 161990, pll dividers - fb: 2036.3 ref: 30, post 6 With this commit reverted (and working screen): kernel: [drm:radeon_compute_pll_avivo] 162000 - 16106, pll dividers - fb: 1023.5 ref: 13, post 7 -- You are receiving this mail because: You are watching the assignee of the bug.

1 35

[Bug 48472] New: GPU Lockup while running demo in wine
by bugzilla-daemon＠freedesktop.org 24 Jun '16

24 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=48472 Bug #: 48472 Summary: GPU Lockup while running demo in wine Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nathanhirschauer(a)verfriemelt.org While running Razor 1911 - Scene is dead (http://www.chiptune.com/razor/rzr-the_scene_is_dead.zip) in wine I get a GPU Lockup: [ 690.049988] radeon 0000:01:00.0: GPU lockup CP stall for more than 10233msec [ 690.049993] GPU lockup (waiting for 0x00002749 last fence id 0x00002746) [ 690.051188] radeon 0000:01:00.0: GPU softreset [ 690.051191] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xE5700030 [ 690.051193] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00110103 [ 690.051195] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 [ 690.051202] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE [ 690.066201] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 [ 690.082204] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 [ 690.082206] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 [ 690.082208] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200080C0 [ 690.083209] radeon 0000:01:00.0: GPU reset succeed [ 690.103443] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 690.103467] radeon 0000:01:00.0: WB enabled [ 690.134854] [drm] ring test succeeded in 1 usecs [ 690.134861] [drm] ib test succeeded in 1 usecs I'm using mesa-git (c653287) with Linux 3.2.13 (Arch Linux) and Xorg 1.12.0.901 on a Thinkpad R500 (which has the following VGA Controller: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] (Mobility Radeon HD 3450) Attached the a logfile with WINEDEBUG=+wgl,+opengl. Seems like the lockup occurs while the following message appears (Line 1232): trace:opengl:wine_glDrawArrays (7, 0, 4) I hope I attached all important files/infos - If I forgot something, let me know. -- 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 78987] New: black screen when trying to enable external VGA screen on Trinity APU laptop
by bugzilla-daemon＠freedesktop.org 19 Jun '16

19 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=78987 Priority: medium Bug ID: 78987 Assignee: dri-devel(a)lists.freedesktop.org Summary: black screen when trying to enable external VGA screen on Trinity APU laptop Severity: major Classification: Unclassified OS: All Reporter: dev(a)lynxeye.de Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 99447 --> https://bugs.freedesktop.org/attachment.cgi?id=99447&action=edit dmesg from failing machine Plugging in an VGA monitor and trying to enable it results in black screen on both the internal laptop display as well as the external VGA monitor. The graphics is dead after this, I have not found any way to restore the screen. However the machine is still responding to ssh and I was able to pick up an quite interesting dmesg snapshot. If you need me to test patches or need any other information, just ping me. -- 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 September 2014