From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199585] New: AMDGPU related kernel dump in /home/kernel/COD/linux/mm/slub.c:296 after monitors power off
Date: Wed, 02 May 2018 05:19:00 +0000 [thread overview]
Message-ID: <bug-199585-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=199585
Bug ID: 199585
Summary: AMDGPU related kernel dump in
/home/kernel/COD/linux/mm/slub.c:296 after monitors
power off
Product: Drivers
Version: 2.5
Kernel Version: 4.16.6
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: jaszhix@gmail.com
Regression: No
Created attachment 275707
--> https://bugzilla.kernel.org/attachment.cgi?id=275707&action=edit
dmesg
Using three monitors, one connected via display port, one DVI, and one HDMI.
After they reach the display timeout and power off, the machine hard locks
leaving a kernel bug stacktrace.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-05-02 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 5:19 bugzilla-daemon [this message]
2018-05-02 5:19 ` [Bug 199585] AMDGPU related kernel dump in /home/kernel/COD/linux/mm/slub.c:296 after monitors power off bugzilla-daemon
2018-05-02 5:22 ` bugzilla-daemon
2018-05-02 5:23 ` bugzilla-daemon
2018-05-02 5:25 ` bugzilla-daemon
2018-05-02 5:30 ` bugzilla-daemon
2018-05-02 5:32 ` bugzilla-daemon
2018-05-02 6:04 ` bugzilla-daemon
2018-05-02 6:25 ` bugzilla-daemon
2018-05-04 15:08 ` bugzilla-daemon
2018-07-15 10:32 ` 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-199585-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.