All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93475] Saints Row IV causes GPU lockup on Linux
Date: Tue, 22 Dec 2015 14:13:37 +0000	[thread overview]
Message-ID: <bug-93475-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2745 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93475

            Bug ID: 93475
           Summary: Saints Row IV causes GPU lockup on Linux
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: holthuis.jan@googlemail.com

When running Saints Row IV (the Linux version that was released yesterday), I'm
getting GPU lockups on my AMD A6-3410MX APU (Radeon HD 6520G) when using mesa
drivers (happens with 11.0.7 and 11.2.0-devel (git-d191066).

Heres some dmesg output: http://hastebin.com/gaxemomefo.log

My system:

$ uname -a
Linux jan-laptop 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015
x86_64 GNU/Linux

$ glxinfo | grep string
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD SUMO (DRM 2.43.0, LLVM 3.8.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0-devel
(git-d191066)
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 11.2.0-devel (git-d191066)
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.0-devel (git-d191066)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

$ cat /proc/cpuinfo
processor    : 0
vendor_id    : AuthenticAMD
cpu family    : 18
model        : 1
model name    : AMD A6-3410MX APU with Radeon(tm) HD Graphics
stepping    : 0
microcode    : 0x3000027
cpu MHz        : 1000.000
cache size    : 1024 KB
physical id    : 0
siblings    : 4
core id        : 0
cpu cores    : 4
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 6
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy
abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat cpb hw_pstate npt
lbrv svm_lock nrip_save pausefilter vmmcall
bugs        : fxsave_leak sysret_ss_attrs
bogomips    : 3195.31
TLB size    : 1536 4K pages
clflush size    : 64
cache_alignment    : 64
address sizes    : 40 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate cpb
<repeats 3 more times>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4020 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-12-22 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 14:13 bugzilla-daemon [this message]
2016-06-17  5:39 ` [Bug 93475] Saints Row IV causes GPU lockup on Linux bugzilla-daemon
2016-06-17  6:02 ` bugzilla-daemon
2016-06-17  6:04 ` bugzilla-daemon
2016-07-13  9:37 ` bugzilla-daemon
2016-08-16 18:51 ` bugzilla-daemon
2016-08-21 14:15 ` bugzilla-daemon
2017-03-12 13:24 ` bugzilla-daemon
2017-06-04 12:00 ` bugzilla-daemon
2019-07-04  1:30 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-93475-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.