From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105760] [4.17-drm-wip] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930 Date: Fri, 30 Mar 2018 16:04:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0587044204==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2AB066E92E for ; Fri, 30 Mar 2018 16:04:44 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0587044204== Content-Type: multipart/alternative; boundary="15224258840.E7f7fA5b.12956" Content-Transfer-Encoding: 7bit --15224258840.E7f7fA5b.12956 Date: Fri, 30 Mar 2018 16:04:44 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105760 --- Comment #1 from taijian@posteo.de --- OK, I think I've managed to narrow this one down a bit. If I build the kernel from commit 09695ad78f1f5f315c7e9c5090f0c7b846a43690, which is also tagged as 'drm-next-4.17', then everything is shiny. However,= if I go one step beyond that, which is commit 33d009cd889490838c5db9b9339856c9e3d3facc - being the rebasing of drm-next-4.17-wip onto David Airlie's drm-next branch after he merged AMD's drm-next-4.17 into his branch, then things to belly up and the kernel does = not boot anymore. Now, what I do not get is how the rebase to a tree that includes stuff that= is not amdgpu would bork up the ability of amdgpu to load it's firmware? --=20 You are receiving this mail because: You are the assignee for the bug.= --15224258840.E7f7fA5b.12956 Date: Fri, 30 Mar 2018 16:04:44 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 1 on bug 10576= 0 from taijian@posteo.d= e 
OK, I think I've managed to narrow this one down a bit.

If I build the kernel from commit 09695ad78f1f5f315c7e9c5090f0c7b846a43690,
which is also tagged as 'drm-next-4.17', then everything is shiny. However,=
 if
I go one step beyond that, which is commit
33d009cd889490838c5db9b9339856c9e3d3facc - being the rebasing of
drm-next-4.17-wip onto David Airlie's drm-next branch after he merged AMD's
drm-next-4.17 into his branch, then things to belly up and the kernel does =
not
boot anymore.

Now, what I do not get is how the rebase to a tree that includes stuff that=
 is
not amdgpu would bork up the ability of amdgpu to load it's firmware?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15224258840.E7f7fA5b.12956-- --===============0587044204== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0587044204==--