[Bug 93571] New: GPU HANG: ecode 8:0:0x85df3c1b, in Borderlands2 [3479], reason: Ring hung
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Jan 3 17:23:56 PST 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93571
Bug ID: 93571
Summary: GPU HANG: ecode 8:0:0x85df3c1b, in Borderlands2
[3479], reason: Ring hung
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: tdaitx at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 120784
--> https://bugs.freedesktop.org/attachment.cgi?id=120784&action=edit
GPU crash dump from /sys/class/drm/card0/error
While running Borderlands 2 on an Asus UX303LA running Ubuntu 15.04 (Wily) it
hangs very often. Usually it hangs in 1 or 3 minutes after a game starts, on a
good day I can play for about 15~30 minutes before the first hang.
Happens on 15.04 mesa drivers as well as the ones from oibaf
(http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu).
dmesg from first hang
-----
[ 561.357624] [drm] stuck on render ring
[ 561.366850] [drm] GPU HANG: ecode 8:0:0x85df3c1b, in Borderlands2 [3479],
reason: Ring hung, action: reset
[ 561.366852] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 561.366853] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 561.366854] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 561.366855] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 561.366857] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 561.369331] drm/i915: Resetting chip after gpu hang
[ 567.362378] [drm] stuck on render ring
[ 567.368586] [drm] GPU HANG: ecode 8:0:0x85dffffb, in Borderlands2 [3479],
reason: Ring hung, action: reset
[ 567.370470] drm/i915: Resetting chip after gpu hang
[ 567.383705] show_signal_msg: 52 callbacks suppressed
[ 567.383709] Borderlands2[3479]: segfault at 79438 ip 00000000091c4352 sp
00000000ffddfc40 error 6 in Borderlands2[8048000+235a000]
further hangs:
[ 872.692295] [drm] stuck on render ring
[ 872.699387] [drm] GPU HANG: ecode 8:0:0x85dffffb, in Borderlands2 [3767],
reason: Ring hung, action: reset
[ 872.702364] drm/i915: Resetting chip after gpu hang
[ 1072.911271] [drm] stuck on render ring
[ 1072.919318] [drm] GPU HANG: ecode 8:0:0x85dffffb, in Borderlands2 [3767],
reason: Ring hung, action: reset
[ 1072.922381] drm/i915: Resetting chip after gpu hang
[ 1078.905058] [drm] stuck on render ring
[ 1078.912613] [drm] GPU HANG: ecode 8:0:0x85df3c1b, in Borderlands2 [3767],
reason: Ring hung, action: reset
[ 1078.914904] drm/i915: Resetting chip after gpu hang
[ 1078.929812] Borderlands2[3767]: segfault at 75bb8 ip 00000000091c4352 sp
00000000ffcda580 error 6 in Borderlands2[8048000+235a000]
I'm not sure if this is related, but every time I start my computer I see the
following message in dmesg:
[ 59.392871] ------------[ cut here ]------------
[ 59.392894] WARNING: CPU: 1 PID: 0 at
/build/linux-cRemOf/linux-4.2.0/drivers/gpu/drm/i915/intel_uncore.c:620
hsw_unclaimed_reg_debug+0x6d/0x90 [i915]()
[ 59.392895] Unclaimed register detected before reading register 0x22390
[ 59.392896] Modules linked in: ctr ccm rfcomm xt_conntrack ipt_REJECT
nf_reject_ipv4 xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter ip_tables x_tables binfmt_misc bnep arc4 iwlmvm mac80211
asus_nb_wmi asus_wmi uvcvideo sparse_keymap videobuf2_vmalloc videobuf2_memops
videobuf2_core hid_sony iwlwifi intel_rapl x86_pkg_temp_thermal v4l2_common
intel_powerclamp ff_memless coretemp videodev media btusb snd_hda_codec_hdmi
snd_hda_codec_conexant snd_hda_codec_generic input_leds joydev btrtl btbcm
btintel serio_raw bluetooth cfg80211 snd_hda_intel snd_soc_rt5640
snd_soc_rl6231 snd_soc_core lpc_ich snd_hda_codec hid_multitouch
[ 59.392929] mei_me mei snd_compress shpchp snd_hda_core snd_hwdep
processor_thermal_device ac97_bus intel_soc_dts_iosf snd_pcm_dmaengine iosf_mbi
snd_pcm snd_timer int3400_thermal dw_dmac acpi_thermal_rel dw_dmac_core
int3402_thermal snd int340x_thermal_zone soundcore 8250_dw kvm_intel acpi_als
mac_hid kvm i2c_designware_platform kfifo_buf i2c_designware_core
snd_soc_sst_acpi industrialio spi_pxa2xx_platform acpi_pad parport_pc ppdev lp
parport sunrpc acpi_call(OE) autofs4 btrfs xor raid6_pq drbg ansi_cprng
algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse i915 crct10dif_pclmul
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper
i2c_algo_bit cryptd drm_kms_helper drm ahci libahci wmi video sdhci_acpi sdhci
i2c_hid hid
[ 59.392962] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE
4.2.0-22-generic #27-Ubuntu
[ 59.392963] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS
UX303LAB.203 12/11/2014
[ 59.392965] 0000000000000000 8995c010696f2a81 ffff88021ec83c78
ffffffff817e94c9
[ 59.392967] 0000000000000000 ffff88021ec83cd0 ffff88021ec83cb8
ffffffff8107b3d6
[ 59.392969] 0000000000000000 ffff88007fa70000 0000000000022390
ffff88007fa743c8
[ 59.392970] Call Trace:
[ 59.392972] <IRQ> [<ffffffff817e94c9>] dump_stack+0x45/0x57
[ 59.392978] [<ffffffff8107b3d6>] warn_slowpath_common+0x86/0xc0
[ 59.392980] [<ffffffff8107b465>] warn_slowpath_fmt+0x55/0x70
[ 59.392993] [<ffffffffc01f714d>] hsw_unclaimed_reg_debug+0x6d/0x90 [i915]
[ 59.392995] [<ffffffff817f0067>] ? _raw_spin_lock_irqsave+0x37/0x40
[ 59.393005] [<ffffffffc01f95f9>] gen6_read32+0x59/0x180 [i915]
[ 59.393016] [<ffffffffc01ee788>] intel_lrc_irq_handler+0xc8/0x220 [i915]
[ 59.393025] [<ffffffffc01e5297>] gen8_gt_irq_handler+0x217/0x240 [i915]
[ 59.393034] [<ffffffffc01e535e>] gen8_irq_handler+0x9e/0x590 [i915]
[ 59.393036] [<ffffffff810d4284>] handle_irq_event_percpu+0x74/0x180
[ 59.393038] [<ffffffff810d43d9>] handle_irq_event+0x49/0x70
[ 59.393040] [<ffffffff810d7751>] handle_edge_irq+0x81/0x150
[ 59.393042] [<ffffffff810172b5>] handle_irq+0x25/0x40
[ 59.393044] [<ffffffff817f2eaf>] do_IRQ+0x4f/0xe0
[ 59.393046] [<ffffffff817f0e2b>] common_interrupt+0x6b/0x6b
[ 59.393047] <EOI> [<ffffffff810e78a4>] ? enqueue_hrtimer+0x44/0x80
[ 59.393051] [<ffffffff816870b0>] ? cpuidle_enter_state+0x130/0x270
[ 59.393052] [<ffffffff8168708b>] ? cpuidle_enter_state+0x10b/0x270
[ 59.393054] [<ffffffff81687227>] cpuidle_enter+0x17/0x20
[ 59.393056] [<ffffffff810bd4f2>] call_cpuidle+0x32/0x60
[ 59.393057] [<ffffffff81687203>] ? cpuidle_select+0x13/0x20
[ 59.393059] [<ffffffff810bd788>] cpu_startup_entry+0x268/0x320
[ 59.393061] [<ffffffff8104d3d3>] start_secondary+0x183/0x1c0
[ 59.393063] ---[ end trace 2ee219074b7f3e5f ]---
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160104/94a66565/attachment.html>
More information about the intel-gfx-bugs
mailing list