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: Fri, 19 Feb 2016 21:14:08 +0000 [thread overview]
Message-ID: <bug-93652-502-fKMd4AMTf4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93652-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 4603 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93652
--- Comment #3 from Wolfgang Frisch <wfr@roembden.net> ---
I'm not sure if this is the same issue but I get freezes with
- Radeon R9 380 (Tonga)
- MESA 11.1.2
- Linux 4.5-rc4
- amdgpu driver with powerplay enabled
The game usually runs for up to 30 minutes and then freezes unexpectedly.
To rule out hardware defects, I also tested the proprietary fglrx driver which
seems stable.
Steam doesn't print anything unusual on the console.
However after 2 minutes, the kernel reports an unresponsive Xorg process with a
backtrace:
[ 7680.137938] INFO: task Xorg:8367 blocked for more than 120 seconds.
[ 7680.137945] Tainted: G O 4.5.0-rc4-desktop #1
[ 7680.137948] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 7680.137952] Xorg D ffff88043ed542c0 0 8367 8218 0x00000084
[ 7680.137959] ffff88040d723a38 ffff8800bb922240 0000000000000000
ffffffff813d7879
[ 7680.137964] ffff88040d724000 ffff88042c804630 ffff88042c800000
0000000000000001
[ 7680.137969] 0000000000000000 ffff8803f651d4c0 ffff88042c806178
ffffffff818ab045
[ 7680.137974] Call Trace:
[ 7680.137985] [<ffffffff813d7879>] ? __kfifo_in+0x1d/0x25
[ 7680.137992] [<ffffffff818ab045>] ? schedule+0x7c/0x90
[ 7680.138050] [<ffffffffa006e9a4>] ? amd_sched_entity_push_job+0x52/0x6b
[amdgpu]
[ 7680.138056] [<ffffffff810bd286>] ? wait_woken+0x66/0x66
[ 7680.138102] [<ffffffffa006edd2>] ?
amdgpu_sched_ib_submit_kernel_helper+0xfd/0x170 [amdgpu]
[ 7680.138143] [<ffffffffa001ad02>] ? amdgpu_gem_prime_export+0x3f/0x3f
[amdgpu]
[ 7680.138184] [<ffffffffa001b386>] ? amdgpu_vm_bo_update_mapping+0x33f/0x415
[amdgpu]
[ 7680.138226] [<ffffffffa001bcfe>] ? amdgpu_vm_bo_update+0xe2/0x172 [amdgpu]
[ 7680.138265] [<ffffffffa0010def>] ? amdgpu_gem_va_update_vm+0x159/0x1aa
[amdgpu]
[ 7680.138306] [<ffffffffa001c10c>] ? amdgpu_vm_bo_map+0x191/0x329 [amdgpu]
[ 7680.138344] [<ffffffffa0011cd2>] ? amdgpu_gem_va_ioctl+0x2b2/0x338 [amdgpu]
[ 7680.138382] [<ffffffffa0011cd2>] ? amdgpu_gem_va_ioctl+0x2b2/0x338 [amdgpu]
[ 7680.138389] [<ffffffff8149318d>] ? drm_ioctl+0x223/0x353
[ 7680.138392] [<ffffffff8149318d>] ? drm_ioctl+0x223/0x353
[ 7680.138431] [<ffffffffa0011a20>] ? amdgpu_gem_metadata_ioctl+0x1ca/0x1ca
[amdgpu]
[ 7680.138436] [<ffffffff81138c65>] ? unmap_region+0xc3/0xd2
[ 7680.138469] [<ffffffffa0000046>] ? amdgpu_drm_ioctl+0x46/0x72 [amdgpu]
[ 7680.138474] [<ffffffff8116ecf5>] ? vfs_ioctl+0x16/0x23
[ 7680.138478] [<ffffffff8116f1df>] ? do_vfs_ioctl+0x46a/0x513
[ 7680.138483] [<ffffffff810ff59d>] ? __audit_syscall_entry+0xbe/0xe2
[ 7680.138488] [<ffffffff8116f2d6>] ? SyS_ioctl+0x4e/0x71
[ 7680.138493] [<ffffffff818adc57>] ? entry_SYSCALL_64_fastpath+0x12/0x66
[ 7680.138528] INFO: task kworker/u12:12:2299 blocked for more than 120
seconds.
[ 7680.138531] Tainted: G O 4.5.0-rc4-desktop #1
[ 7680.138534] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 7680.138536] kworker/u12:12 D ffff88043ec542c0 0 2299 2 0x00000080
[ 7680.138578] Workqueue: amdgpu-pageflip-queue amdgpu_flip_work_func [amdgpu]
[ 7680.138581] ffff8803251dfca0 ffff88042ddc82c0 000000000000000a
0000000000000490
[ 7680.138586] ffff8803251e0000 ffff8803251dfd80 ffff88042ddc82c0
0000000000000246
[ 7680.138591] ffff8804253fe600 ffff8803251dfd90 ffff8803251dfd60
ffffffff818ab045
[ 7680.138595] Call Trace:
[ 7680.138601] [<ffffffff818ab045>] ? schedule+0x7c/0x90
[ 7680.138606] [<ffffffff818acf7f>] ? schedule_timeout+0x44/0x1df
[ 7680.138612] [<ffffffff810b818a>] ? load_balance+0x15c/0x7fe
[ 7680.138617] [<ffffffff810b22ed>] ? sched_clock_cpu+0xc/0xb0
[ 7680.138623] [<ffffffff81583514>] ? fence_default_wait+0x109/0x1ac
[ 7680.138628] [<ffffffff81583514>] ? fence_default_wait+0x109/0x1ac
[ 7680.138633] [<ffffffff8158303b>] ? fence_free+0xe/0xe
[ 7680.138670] [<ffffffffa000ea2b>] ? amdgpu_flip_wait_fence+0x32/0xa5
[amdgpu]
[ 7680.138708] [<ffffffffa000fae3>] ? amdgpu_flip_work_func+0x5d/0x156
[amdgpu]
[ 7680.138714] [<ffffffff810a4351>] ? process_one_work+0x194/0x29f
[ 7680.138718] [<ffffffff810a49a6>] ? worker_thread+0x276/0x360
[ 7680.138723] [<ffffffff810a4730>] ? rescuer_thread+0x2ad/0x2ad
[ 7680.138727] [<ffffffff810a85bf>] ? kthread+0xc1/0xc9
[ 7680.138731] [<ffffffff810a84fe>] ? kthread_create_on_node+0x17c/0x17c
[ 7680.138735] [<ffffffff818adf9f>] ? ret_from_fork+0x3f/0x70
[ 7680.138739] [<ffffffff810a84fe>] ? kthread_create_on_node+0x17c/0x17c
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5628 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-02-19 21:14 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 [this message]
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
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-fKMd4AMTf4@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).