| Bug ID | 105760 |
|---|---|
| Summary | [4.17-drm-wip] RIP: smu7_populate_single_firmware_entry.isra.= 6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930 |
| Product | DRI |
| Version | DRI git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Keywords | regression |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | taijian@posteo.de |
Created attach= ment 138374 [details] recovered journal of boot attempt I am trying out the linux-4.17-drm-next kernel line from https://cgit.freedesktop.org/~agd5f/linux/log/?h=3Ddrm-next-4.17-wip<= /a> and with the latest build (commit 576e538e5fe6ac103cde6b269c6210985b026689) my systemc no longer boots to the graphical target and instead hard freezes after loading= the initramfs. A recovered journal is attached.
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?
| What | Removed | Added |
|---|---|---|
| See Also | https://bugs.freedesktop.org/show_bug.cgi?id=3D104854 |
| What | Removed | Added |
|---|---|---|
| Summary | [4.17-drm-wip] RIP: smu7_populate_single_firmware_entry.isra= .6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930 | [4.17-rc1] RIP: smu7_populate_single_firmware_entry.isra.6+0= x57/0xc0 [amdgpu] RSP: ffffa17901efb930 |
After upgrading my testing kernel to 4.17-rc1, the problem sti= ll persists and the system remains unbootable.
| What | Removed | Added |
|---|---|---|
| Severity | normal | critical |
| Priority | medium | high |
| What | Removed | Added |
|---|---|---|
| See Also | https://bugs.freedesktop.org/show_bug.cgi?id=3D105883 |
Is the driver build as a module or built into the kernel?
It is build as a module and then embedded in the initramfs.
If I wanted to try to embed amdgpu in the kernel for testing, = how would I even go about doing that? Simply editing my config file from =3Dm to =3Dy does n= ot seem to do anything.
| What | Removed | Added |
|---|---|---|
| Attachment #138374 is obsolete | 1 |
Created attach=
ment 138890 [details]
recovered journal of boot attempt
OK, trying out the latest git code from drm-next-4.18-wip up to and includi=
ng
commit 37d6cbfb550ebde65ec12291ec9ec03f87cd0aff, we seem to be getting a
step further in the boot process. Now the initramfs seems to hand over fine=
to
GDM, I can select my user entry and enter my login password. However, the
screen then freezes upon trying to start the user session (Xorg, haven't tr=
ied
Wayland so far). Error messages look very similar to before.
OK, the issue still persists with 4.17rc2. Same as before, I c= an boot into cli but trying to start X results in a hung system because X cannot access the dGPU.=20 For reference, my firmware is current as of=20 Qs linux-firmware local/linux-firmware 20180402.8c1e439-1
| What | Removed | Added |
|---|---|---|
| CC | mathieu.dutour@gmail.com |
*** Bug 106513 has been marked as a du= plicate of this bug. ***
This seems to be fixed an the current drm-next-4.18-wip branch= .
| What | Removed | Added |
|---|---|---|
| CC | ratcheer@gmail.com |
*** Bug 106402 has been marked as a du= plicate of this bug. ***
Created attachment 139668= [details] dmesg after resume I still get the backtrace on drm-next-4.18-wip, unfortunately. (note that I have also cherry-picked the last patch from https://bu= gzilla.kernel.org/show_bug.cgi?id=3D199693 to make resume work at all) On a side node, I also see that lspci hangs when running this kernel. System: Arch Linux Intel Kably Lake Refresh (i7-8550U), Intel UHD 620 + Radeon Pro WX 3100.
Have you tried again on any of the 4.18rc? I am currently test= ing 4.18-rc2 and altough I have some other bug there, this one seems to be gone for me.
Thanks, but no time for that. Reverted to 17.10 Le lun. 25 juin 2018 =C3=A0 00:31, <bugzilla-daemon@freedesktop.org> a =C3=A9crit= : > *Commen= t # 13 <https://bugs.freedesktop.org/show_= bug.cgi?id=3D105760#c13> on > bug 105760 <https://bugs.freedesktop.org/show_bug.= cgi?id=3D105760> from > taijian@posteo.de <= ;taijian@posteo.de> * > > Have you tried again on any of the 4.18rc? I am = currently testing 4.18-rc2 and > altough I have some other bug there, this one seems to be gone for me.= > > ------------------------------ > You are receiving this mail because: > > - You are on the CC list for the bug. > >
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | WORKSFORME |
| What | Removed | Added |
|---|---|---|
| Resolution | WORKSFORME | --- |
| Status | RESOLVED | REOPENED |
| What | Removed | Added |
|---|---|---|
| Attachment #139668 is obsolete | 1 |
Created attachment 140356=
[details]
dmesg after resume
OK, over at bug 107045 we agreed I'd start bis= ecting this starting from 4.16. I'll report back once I find something, but it'll be a while...