Bug 105747

Summary: TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch
Product: DRI Reporter: Nayan Deshmukh <nayan26deshmukh>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: VERIFIED NOTABUG QA Contact:
Severity: normal    
Priority: medium CC: alexdeucher, nayan26deshmukh
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg for kernel v4.15
none
dmesg for amd-staging-drm-next none

Description Nayan Deshmukh 2018-03-26 11:32:29 UTC
Created attachment 138355 [details]
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.
Comment 1 Nayan Deshmukh 2018-03-26 11:35:11 UTC
Created attachment 138356 [details]
dmesg for amd-staging-drm-next
Comment 2 Alex Deucher 2018-03-26 15:53:18 UTC
Is there an actual bug you are seeing?  We no longer print the ring and IB test info in the log unless you enable verbose logging to make the driver less chatty.
Comment 3 Nayan Deshmukh 2018-03-26 16:50:18 UTC
Oh..I am seeing any bug as such, I thought the ring buffers are getting initialized. How can I get the verbose output to confirm that everything is working fine?
Comment 4 Alex Deucher 2018-03-26 17:02:40 UTC
The driver will print an error if any of the ring or IB tests fail.  It just doesn't print anything if they succeed. You can adjust the debug level by adjusting the debug module parameter for the drm.ko module.
Comment 5 Nayan Deshmukh 2018-03-27 12:56:19 UTC
It is working alright. Sorry for the unnecessary noise.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.