From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108309] Raven Ridge 2700U system lock-up on multiple games
Date: Sat, 13 Oct 2018 08:30:07 +0000 [thread overview]
Message-ID: <bug-108309-502-PXP8MkJnNZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108309-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2596 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108309
Samantha McVey <samantham@posteo.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #142000|0 |1
is obsolete| |
--- Comment #5 from Samantha McVey <samantham@posteo.net> ---
Created attachment 142013
--> https://bugs.freedesktop.org/attachment.cgi?id=142013&action=edit
4.18.12 dmesg log, was using vulkan at the time
Seems I spoke too soon. I am uploading some logs taken with 4.18.12 while using
vulkan. Screen was fully frozen, and for example trying to mute audio would not
change the status indicator on my keyboard. Some extracts related to amdgpu
below, but the full dmesg is attached.
Oct 13 01:08:12 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, last signaled seq=1055330, last emitted seq=1055332
...
Oct 13 01:09:24 kernel: kworker/0:2: page allocation failure: order:10,
mode:0x6040c0(GFP_KERNEL|__GFP_COMP), nodemask=(null)
Oct 13 01:09:24 kernel: kworker/0:2 cpuset=/ mems_allowed=0
Oct 13 01:09:24 kernel: CPU: 0 PID: 192238 Comm: kworker/0:2 Tainted: G
C 4.18.12 #1
Oct 13 01:09:24 kernel: Hardware name: LENOVO 20MUCTO1WW/20MUCTO1WW, BIOS
R0WET34W (1.02 ) 07/05/2018
Oct 13 01:09:24 kernel: Workqueue: events do_poweroff
Oct 13 01:09:24 kernel: Call Trace:
Oct 13 01:09:24 kernel: dump_stack+0x5c/0x7b
Oct 13 01:09:24 kernel: warn_alloc+0xf7/0x180
Oct 13 01:09:24 kernel: ? _cond_resched+0x11/0x40
Oct 13 01:09:24 kernel: __alloc_pages_nodemask+0xee3/0x1030
Oct 13 01:09:24 kernel: ? __radix_tree_delete+0x7e/0xa0
Oct 13 01:09:24 kernel: cache_grow_begin+0x77/0x510
Oct 13 01:09:24 kernel: fallback_alloc+0x15c/0x1f0
Oct 13 01:09:24 kernel: ? amdgpu_vcn_suspend+0x47/0x80 [amdgpu]
Oct 13 01:09:24 kernel: __kmalloc+0x1bf/0x240
Oct 13 01:09:24 kernel: amdgpu_vcn_suspend+0x47/0x80 [amdgpu]
Oct 13 01:09:24 kernel: amdgpu_device_ip_suspend+0xbd/0x160 [amdgpu]
Oct 13 01:09:24 kernel: device_shutdown+0x13f/0x1e0
Oct 13 01:09:24 kernel: kernel_power_off+0x2c/0x60
Oct 13 01:09:24 kernel: process_one_work+0x1e0/0x3c0
Oct 13 01:09:24 kernel: worker_thread+0x44/0x3f0
Oct 13 01:09:24 kernel: kthread+0xf0/0x130
Oct 13 01:09:24 kernel: ? process_one_work+0x3c0/0x3c0
Oct 13 01:09:24 kernel: ? kthread_flush_work_fn+0x10/0x10
Oct 13 01:09:24 kernel: ret_from_fork+0x22/0x40
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4093 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:[~2018-10-13 8:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 2:07 [Bug 108309] Raven Ridge 2700U system lock-up on multiple games bugzilla-daemon
2018-10-10 20:13 ` bugzilla-daemon
2018-10-12 4:40 ` bugzilla-daemon
2018-10-12 4:42 ` bugzilla-daemon
2018-10-12 7:51 ` bugzilla-daemon
2018-10-12 7:51 ` bugzilla-daemon
2018-10-13 0:54 ` bugzilla-daemon
2018-10-13 8:30 ` bugzilla-daemon [this message]
2018-10-13 8:31 ` bugzilla-daemon
2018-10-13 11:13 ` bugzilla-daemon
2018-10-13 11:25 ` bugzilla-daemon
2019-04-14 17:26 ` bugzilla-daemon
2019-06-07 16:54 ` bugzilla-daemon
2019-07-01 22:12 ` bugzilla-daemon
2019-11-19 8:58 ` 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-108309-502-PXP8MkJnNZ@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).