From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105369] HP HP ENVY x360, amdgpu, Call Trace tgn10_lock at startup, VMC page fault during runtime
Date: Fri, 09 Mar 2018 16:23:23 +0000 [thread overview]
Message-ID: <bug-105369-502-iKJkXD9pmG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105369-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105369
--- Comment #10 from cd <chris@degree.at> ---
A freeze occured while working with the laptop:
uname -r
4.16.0-rc1-085145ebf0e9
[20516.321517] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
last signaled seq=448660, last emitted seq=448663
[20516.321526] [drm] No hardware hang detected. Did some blocks stall?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1316 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-03-09 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 13:58 [Bug 105369] HP HP ENVY x360, amdgpu, Call Trace tgn10_lock at startup, VMC page fault during runtime bugzilla-daemon
2018-03-06 14:05 ` bugzilla-daemon
2018-03-06 15:27 ` bugzilla-daemon
2018-03-07 9:01 ` bugzilla-daemon
2018-03-07 9:02 ` bugzilla-daemon
2018-03-07 14:50 ` bugzilla-daemon
2018-03-07 16:57 ` bugzilla-daemon
2018-03-07 17:00 ` bugzilla-daemon
2018-03-09 9:01 ` bugzilla-daemon
2018-03-09 9:02 ` bugzilla-daemon
2018-03-09 16:23 ` bugzilla-daemon [this message]
2018-03-14 12:42 ` 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-105369-502-iKJkXD9pmG@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