https://bugs.freedesktop.org/show_bug.cgi?id=89659
Bug ID: 89659
Summary: GPU Hangs with dota2
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: kontakt(a)ib-guder.de
Created attachment 114442
--> https://bugs.freedesktop.org/attachment.cgi?id=114442&action=edit
dmesg after a crash
Hello,
I get reproducible GPU hangs often within one minute spectating a game in
dota2. Other OpenGL applications runs without hangs. The screen stays black,
the keyboard doesn't work after a crash. Networking via ssh works.
Archlinux 64bit
Mesa: 10.5.1
Linux: 3.18.6 and 3.14.53
Thank you and best wishes
Tom Guder
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89059
Bug ID: 89059
Summary: Dota crashes constantly before 10min mark
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: jarkko_korpi(a)hotmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
I got oibaf ppa. They started to use LLVM 3.6 compiler around that time I
started to have unstable dota. I cant finnish any dota 2 games. The computer
hangs before 10min mark while in dota. But I have played around 2hour episode
of game of thrones from tell tale. So this sounds only dota 2 issue for me.
I could see console a message something like this:
"Still active bo inside vm"
The computer freezes, most of the times I could only force boot.
Gpu r9 290
3.19.0-031900rc7
OpenGL renderer string: Gallium 0.4 on AMD HAWAII
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel
(git-08a06b6 2015-02-10 trusty-oibaf-ppa)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=90284
Bug ID: 90284
Summary: radeon crashes (ring 0 stall) with GPU fault detected:
147, and *ERROR* radeon: dpm resume failed.
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: niklas(a)trippler.no
Created attachment 115515
--> https://bugs.freedesktop.org/attachment.cgi?id=115515&action=edit
journalctl -r -x --boot=-4
Graphics card: AMD R9 290
Kernel: Linux archfractal 4.0.1-1-ARCH #1 SMP PREEMPT
Monitors connected: 2
DE: Xfce
Relevant packages:
local/xf86-video-ati 1:7.5.0-2 (xorg-drivers xorg)
local/lib32-mesa 10.5.4-1
local/lib32-mesa-libgl 10.5.4-1
local/lib32-mesa-vdpau 10.5.4-1
local/linux 4.0.1-1 (base)
local/xorg-server 1.17.1-5 (xorg)
This bug, which is triggered by dota2 (Valve game), locks up both displays for
a few seconds before they blink black and freeze in the last frame displayed,
requireing a system reboot. The bug seems to happen with others (same symptoms
/ log messages) using other applications (chrome html5 video was mentioned),
but dota2 seems like one of the few recreatable ways to trigger the bug.
Steps to recreate:
Have steam and dota 2 installed (might have to remove steams own bundled
libstdc++ libraries as they conflict with mesa).
Launch dota 2 with any video settings
Start a new lobby with "cheats enabled" and "all pick" game mode (these don't
matter, but make it faster to recreate)
Pick the hero "Chaos Knight" and enter the game
Type in chat "-lvlup 24" to gain max level and skill up everything
Click R to use ulti (which spawns copies of himself)
Hold-drag mouse over all the illusions and the hero.
When the mouse button is released the above bug triggers, crashing the
displaydriver and taking the computer down with it.
In the log attached (journal_log) the bug is triggered at 17:43:50, the first
line there is: "kernel: radeon 0000:01:00.0: GPU fault detected: 147
0x000cc801"
I noticed a few lines later the following lines appeared:
May 02 17:44:01 archfractal kernel: [drm:radeon_pm_resume [radeon]] *ERROR*
radeon: dpm resume failed
May 02 17:44:01 archfractal kernel: [drm:ci_dpm_enable [radeon]] *ERROR*
ci_start_dpm failed
I guessed the bug had something to do with dpm, and disabled it (kernel
parameter radeon.dpm=0). When I had done this the bug could still be recreated,
but the log showed completely different error messages. This log is also
attached as "journal_log_radeon_dpm_is_0"
I had to gzip the first log to fit within the 3M file size limit
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=81689
Priority: medium
Bug ID: 81689
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Black screen in info-beamer
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: sa(a)whiz.se
Hardware: x86 (IA32)
Status: NEW
Version: 10.2
Component: Drivers/Gallium/r600
Product: Mesa
The multimedia presenter info-beamer ( http://info-beamer.org/ ) just renders a
black screen with r600g.
It's working fine with software rendering and on Intel hardware.
Not a regression, or at least present in Mesa 9.2.
I've made an apitrace of one of the beamer demos:
https://my.owndrive.com/public.php?service=files&t=cef11b335be2741058363783…
The trace renders correctly but gives a lot of errors, so this might be a bug
in info-beamer:
0 87813 glGetUniformLocation(program = 0, name = "Color") = -1
87813: warning: glGetError(glGetUniformLocation) = GL_INVALID_VALUE
87872: glDebugOutputCallback: High severity API error 1, GL_INVALID_OPERATION
in glReadBuffer(buffer=0x405)
87872: glDebugOutputCallback: High severity API error 1, GL_INVALID_OPERATION
in glDrawBuffer(buffer=0x405)
0 87872 glPopAttrib()
87872: warning: glGetError(glPopAttrib) = GL_INVALID_OPERATION
87882: glDebugOutputCallback: High severity API error 1, GL_INVALID_VALUE in
glGetUniformLocation
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: REDWOOD
-- Model: XFX Radeon HD 5670 1GB
-- Display connector: DVI
-- xf86-video-ati: 7.4.0
-- xserver: 1.16.0
-- mesa: 10.2.4
-- drm: 2.4.54
-- kernel: 3.13
--
You are receiving this mail because:
You are the assignee for the bug.
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.
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.
https://bugs.freedesktop.org/show_bug.cgi?id=50338
Bug #: 50338
Summary: r600g: EE r600_shader.c:140 r600_pipe_shader_create -
translation from TGSI failed !
Classification: Unclassified
Product: Mesa
Version: git
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 62087
--> https://bugs.freedesktop.org/attachment.cgi?id=62087
R600_DUMP_SHADERS=1 output
Trying to reproduce bug #50325 on Mesa git caused this error:
EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed !
Bug can be reproduced by one of these:
build/glretrace lt-glyphy-demo.trace
demo/glyphy-demo
I get the translation failed error both with R600_LLVM=0, and R600_LLVM=1.
I've attached the R600_DUMP_SHADERS=1 output.
glretrace is from https://github.com/apitrace/apitrace/tree/1.0
and glyphy is from https://code.google.com/p/glyphy/source/checkout
lt-glypy-demo.trace is here:
https://bugs.freedesktop.org/attachment.cgi?id=62078
git version of Mesa:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 8.1-devel (git-35f302d)
OpenGL shading language version string: 1.30
OpenGL extensions:
Built with (on Debian unstable):
./configure --with-dri-drivers= --with-gallium-drivers=r600,swrast
--enable-glx-tls --enable-gallium-llvm LLVM_CONFIG=/usr/bin/llvm-config-3.1
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.