From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108892] kernel BUG at kernel/time/timer.c:1137 in drm_sched_job_finish [gpu_sched]
Date: Thu, 29 Nov 2018 06:38:43 +0000 [thread overview]
Message-ID: <bug-108892-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108892
Bug ID: 108892
Summary: kernel BUG at kernel/time/timer.c:1137 in
drm_sched_job_finish [gpu_sched]
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: vicluo96@gmail.com
Created attachment 142656
--> https://bugs.freedesktop.org/attachment.cgi?id=142656&action=edit
kernel dmesg
Sometimes my AMD-2500U with amd.dc=1 crashes with the above messages in dmesg.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2222 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 reply other threads:[~2018-11-29 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 6:38 bugzilla-daemon [this message]
2018-11-29 7:35 ` [Bug 108892] kernel BUG at kernel/time/timer.c:1137 in drm_sched_job_finish [gpu_sched] bugzilla-daemon
2018-11-29 8:40 ` bugzilla-daemon
2018-11-29 9:31 ` bugzilla-daemon
2018-11-29 16:10 ` bugzilla-daemon
2018-12-06 11:58 ` bugzilla-daemon
2018-12-06 12:04 ` bugzilla-daemon
2018-12-07 5:04 ` bugzilla-daemon
2019-01-06 15:58 ` bugzilla-daemon
2019-01-06 15:59 ` bugzilla-daemon
2019-05-02 20:59 ` bugzilla-daemon
2019-11-19 9:05 ` 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-108892-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.