dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu
Date: Sat, 11 Feb 2017 17:28:25 +0000	[thread overview]
Message-ID: <bug-99387-502-fb8f7w6LYt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99387-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1630 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99387

--- Comment #16 from Marco <mpiazza@gmail.com> ---
Created attachment 129516
  --> https://bugs.freedesktop.org/attachment.cgi?id=129516&action=edit
oops with the two patche applied

Patch does not cleanly apply on 4.9.9
but it's easy to port.

But the result is the same.
Find to attached oops with patch applied.

Debugging the faulting instruction (amdgpu_pm_compute_clocks+0x424/0x640
[amdgpu])
lead to:

Reading symbols from drivers/gpu/drm/amd/amdgpu/amdgpu_pm.o...done.
(gdb) list *(amdgpu_pm_compute_clocks+0x424/0x640)
0x1a50 is in amdgpu_pm_compute_clocks
(drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c:1280).
1275    {
1276            struct drm_device *ddev = adev->ddev;
1277            struct drm_crtc *crtc;
1278            struct amdgpu_crtc *amdgpu_crtc;
1279    
1280            if (!adev->pm.dpm_enabled)
1281                    return;
1282    
1283            if (adev->pp_enabled) {
1284                    int i = 0;
(gdb) 
1285    
1286                    if (adev->mode_info.num_crtc)
1287                            amdgpu_display_bandwidth_update(adev);
1288    
1289                    for (i = 0; i < AMDGPU_MAX_RINGS; i++) {
1290                            struct amdgpu_ring *ring = adev->rings[i];
1291                            if (ring && ring->ready)
1292                                    amdgpu_fence_wait_empty(ring);
1293                    }
1294    

Fualty line seems to be:
1280            if (!adev->pm.dpm_enabled)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2603 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

  parent reply	other threads:[~2017-02-11 17:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 19:05 [Bug 99387] Kernel 4.9: Kaveri + Hainan choked on boot using amdgpu bugzilla-daemon
2017-01-12 19:47 ` bugzilla-daemon
2017-01-12 22:50 ` bugzilla-daemon
2017-01-12 22:53 ` bugzilla-daemon
2017-01-13  0:57 ` bugzilla-daemon
2017-01-13  3:12 ` bugzilla-daemon
2017-01-13  3:59 ` bugzilla-daemon
2017-01-13  6:00 ` bugzilla-daemon
2017-01-27 15:34 ` bugzilla-daemon
2017-01-28 19:08 ` bugzilla-daemon
2017-02-04  4:47 ` bugzilla-daemon
2017-02-04  4:59 ` bugzilla-daemon
2017-02-04  6:10 ` bugzilla-daemon
2017-02-10 22:20 ` bugzilla-daemon
2017-02-10 22:24 ` bugzilla-daemon
2017-02-10 23:13 ` bugzilla-daemon
2017-02-11 17:28 ` bugzilla-daemon [this message]
2017-02-15  1:29 ` bugzilla-daemon
2017-02-21 21:39 ` bugzilla-daemon
2017-02-24 18:22 ` bugzilla-daemon
2017-03-07  4:27 ` bugzilla-daemon
2017-03-07 14:55 ` 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-99387-502-fb8f7w6LYt@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;
as well as URLs for NNTP newsgroup(s).