From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1
Date: Mon, 27 Jun 2016 13:28:01 +0000 [thread overview]
Message-ID: <bug-93652-502-MMkRys2qqD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93652-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3609 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93652
Adam Bolte <boltronics@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |boltronics@gmail.com
--- Comment #11 from Adam Bolte <boltronics@gmail.com> ---
Confirming this same behaviour on an Asus Radeon R9 285 OC 2GB card:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939]
As others have said, Gallium Nine seems to run reliably. Vanilla Wine causes
regular crashes, where I always have to SSH into the host from a laptop to
reboot it. No problem with fglrx on Ubuntu 14.04.4.
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level does
help a lot while active, but somehow this keeps getting reset back to auto
which causes crashes again. I even have a cron job to run the above command
every minute, but it's not enough.
[ 6960.948175] INFO: task Xorg:5192 blocked for more than 120 seconds.
[ 6960.948177] Tainted: G OE 4.7.0-rc2+ #2
[ 6960.948177] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 6960.948178] Xorg D ffff88086ec56d80 0 5192 5169 0x00000004
[ 6960.948180] ffff880820e5c0c0 000000000011f5f8 ffffffff81327b2d
ffff88082620c000
[ 6960.948181] ffff880847c45780 ffff8808453274e8 0000000000000001
000000000011f5f8
[ 6960.948182] ffff880842e8d9c8 ffffffff815cd641 ffff880407949400
ffffffffc0b10c0f
[ 6960.948183] Call Trace:
[ 6960.948186] [<ffffffff81327b2d>] ? __kfifo_in+0x2d/0x40
[ 6960.948187] [<ffffffff815cd641>] ? schedule+0x31/0x80
[ 6960.948200] [<ffffffffc0b10c0f>] ? amd_sched_entity_push_job+0x6f/0x110
[amdgpu]
[ 6960.948202] [<ffffffff810b87b0>] ? wake_atomic_t_function+0x60/0x60
[ 6960.948211] [<ffffffffc0b115af>] ? amdgpu_job_submit+0x9f/0xf0 [amdgpu]
[ 6960.948218] [<ffffffffc0ad6cbf>] ? amdgpu_vm_bo_update_mapping+0x2bf/0x430
[amdgpu]
[ 6960.948225] [<ffffffffc0ad6f8a>] ? amdgpu_vm_bo_split_mapping+0x15a/0x1a0
[amdgpu]
[ 6960.948231] [<ffffffffc0ad81cf>] ? amdgpu_vm_clear_freed+0x4f/0x90 [amdgpu]
[ 6960.948237] [<ffffffffc0ac81a8>] ? amdgpu_gem_va_update_vm+0x188/0x1c0
[amdgpu]
[ 6960.948239] [<ffffffffc09cdc9a>] ? ttm_bo_add_to_lru+0x8a/0xf0 [ttm]
[ 6960.948245] [<ffffffffc0ac929c>] ? amdgpu_gem_va_ioctl+0x22c/0x2e0 [amdgpu]
[ 6960.948251] [<ffffffffc07e5701>] ?
drm_gem_object_handle_unreference_unlocked+0x11/0xa0 [drm]
[ 6960.948254] [<ffffffffc07e6601>] ? drm_ioctl+0x131/0x4c0 [drm]
[ 6960.948260] [<ffffffffc0ac9070>] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0
[amdgpu]
[ 6960.948262] [<ffffffff811f1ee9>] ? do_readv_writev+0x149/0x240
[ 6960.948263] [<ffffffff8131b974>] ? timerqueue_add+0x54/0xa0
[ 6960.948267] [<ffffffffc0ab2046>] ? amdgpu_drm_ioctl+0x46/0x80 [amdgpu]
[ 6960.948269] [<ffffffff8120537d>] ? do_vfs_ioctl+0x9d/0x5c0
[ 6960.948270] [<ffffffff814b65ed>] ? __sys_recvmsg+0x7d/0x90
[ 6960.948271] [<ffffffff81205914>] ? SyS_ioctl+0x74/0x80
[ 6960.948272] [<ffffffff815d1536>] ? entry_SYSCALL_64_fastpath+0x1e/0xa8
drm: 625d1810ad1f61dd4f4b2b2ee7e5cc67e1fdc2f1 on master.
xf86-video-amdgpu: d96dabc71b1b32dc4b422a9633cdd4e0e95da052 on master.
mesa: d93bacc1fa4bf1d6d358da3615b00305e8518f33 on master.
linux: 0812a945fbb814e7946fbe6ddcc81d054c8b6c91 on polaris-test (from
git://people.freedesktop.org/~agd5f/linux)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5084 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-27 13:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 14:42 [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1 bugzilla-daemon
2016-01-10 17:26 ` bugzilla-daemon
2016-01-11 0:41 ` bugzilla-daemon
2016-02-19 21:14 ` bugzilla-daemon
2016-03-09 6:15 ` bugzilla-daemon
2016-03-14 13:42 ` bugzilla-daemon
2016-03-28 2:20 ` bugzilla-daemon
2016-03-29 19:18 ` bugzilla-daemon
2016-04-04 9:03 ` bugzilla-daemon
2016-05-10 20:16 ` bugzilla-daemon
2016-05-27 13:12 ` bugzilla-daemon
2016-06-27 13:28 ` bugzilla-daemon [this message]
2016-08-22 3:05 ` bugzilla-daemon
2016-10-30 1:34 ` bugzilla-daemon
2016-10-31 20:40 ` bugzilla-daemon
2017-01-14 14:32 ` bugzilla-daemon
2017-01-14 23:22 ` bugzilla-daemon
2017-01-14 23:43 ` bugzilla-daemon
2017-01-16 1:01 ` bugzilla-daemon
2017-05-20 15:51 ` bugzilla-daemon
2017-05-26 19:58 ` bugzilla-daemon
2019-09-17 3:00 ` 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-93652-502-MMkRys2qqD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).