From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch
Date: Mon, 26 Mar 2018 11:32:29 +0000 [thread overview]
Message-ID: <bug-105747-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105747
Bug ID: 105747
Summary: TOPAZ: ring buffers not getting initialized with the
amd-staging-drm-next branch
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: nayan26deshmukh@gmail.com
Created attachment 138355
--> https://bugs.freedesktop.org/attachment.cgi?id=138355&action=edit
dmesg for kernel v4.15
Everything was working fine with v4.15. But the ring buffers don't seem to be
initialized with amd-staging-drm-next branch from Alex's tree. I am attaching
the output of "dmesg | grep 'amd\|drm'" for both cases. the dmesg_v415 is
kernel v4.15.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2449 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-03-26 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 11:32 bugzilla-daemon [this message]
2018-03-26 11:35 ` [Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch bugzilla-daemon
2018-03-26 15:53 ` bugzilla-daemon
2018-03-26 16:50 ` bugzilla-daemon
2018-03-26 17:02 ` bugzilla-daemon
2018-03-27 12:56 ` 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-105747-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.