I'm sorry for the wrong link, this one should work https://gist.github.com/Kreyren/3e55e9a754e58956e1690e38b1888de7
I've manually compiled kernel-5.5 which results in this dmesg - https://gist.githubusercontent.com/Kreyren/2fa75d30e0632d73311a13c2e872cfe6/raw/78d367f890eb64026e64597091a2a2f40bdbe46a/gistfile1.txt If relevant i've used this config https://gist.githubusercontent.com/Kreyren/7b20ad875ca42381d4a0a8e5b1b26a2c/raw/171747682e49fe28cb653b2e45ee42390ca59338/gistfile1.txt (grabbed from debian) Regards, - Jacob Hrbek <https://gist.github.com/Kreyren/3e55e9a754e58956e1690e38b1888de7> On Fri, Jan 31, 2020 at 2:57 AM Liu, Zhan <[email protected]> wrote: > Okay I see. From your attached dmesg.log, issue comes from here: > > > > [ 26.265638] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 > timeout, signaled seq=1, emitted seq=2 > > [ 26.265764] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process > information: process pid 0 thread pid 0 > > [ 26.265771] [drm] GPU recovery disabled. > > > > There was a very similar issue that’s recently fixed and merged in 5.5 > kernel. I’ve noticed that you are using 5.4 kernel, so you can give 5.5 a > spin to see what happens. > > > > As for these “Green Dots” at BIOS initialization stage, the main amdgpu > driver was not loaded yet, so it shouldn’t related to amdgpu. > > > > BTW, your new findings ( > https://gist.github.com/Kreyren/3e55e9a754e58956e1690e38b1888de7) gives > me 404. Please fix the link. Good luck! > > > > Warm regards, > > Zhan > > > > > > > > *From:* Jacob Hrbek <[email protected]> > *Sent:* 2020/January/30, Thursday 5:55 PM > *To:* Liu, Zhan <[email protected]>; [email protected] > *Subject:* Re: Suspecting corrupted VBIOS after update of AMDGPU on > AMD7870 > > > > *Hello Zhan,* > > Here is it: > > https://gist.githubusercontent.com/Kreyren/e35587d8710e63e511e69d8653fd996b/raw/628df1c76ff99adab1d2161e6a20f631de101d5c/gistfile1.txt > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.githubusercontent.com%2FKreyren%2Fe35587d8710e63e511e69d8653fd996b%2Fraw%2F628df1c76ff99adab1d2161e6a20f631de101d5c%2Fgistfile1.txt&data=02%7C01%7CZhan.Liu%40amd.com%7C2fe63c116bbd4cacddc008d7a5d79126%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637160218197534666&sdata=CGBp3z6G8KJXT9cyfaJxlDlkpaDF36qTsj228KYo1bk%3D&reserved=0> > > > > Note that I'm updating previous gists with new findings ( > https://gist.github.com/Kreyren/3e55e9a754e58956e1690e38b1888de7). > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2FKreyren%2F3e55e9a754e58956e1690e38b1888de7).&data=02%7C01%7CZhan.Liu%40amd.com%7C2fe63c116bbd4cacddc008d7a5d79126%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637160218197544657&sdata=C8pB8txk8a9du6ulzG%2FA15VBF8vTXfjZ%2BG9vU9%2FFkCw%3D&reserved=0> > > > > If relevant i'm also getting these 'Green dots' at the initialization of > bios (https://linx.li/s/8j3poh2z.png > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinx.li%2Fs%2F8j3poh2z.png&data=02%7C01%7CZhan.Liu%40amd.com%7C2fe63c116bbd4cacddc008d7a5d79126%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637160218197544657&sdata=ZuobmBcSLCHK97ta%2FLG5txQCf0vN%2BS47UGRNAlPZu2s%3D&reserved=0> > ). > These dots are not present anywhere else and were not present before said > update. > > > > *Thanks,* > > - Jacob Hrbek > > > > On Thu, Jan 30, 2020 at 8:10 PM Liu, Zhan <[email protected]> wrote: > > Hi Jacob, > > > > Thant you for your bug reporting. > > > > I saw you attached xorg.log, which is great. Could you also grab dmesg.log > via SSH? > > > > Thanks, > > Zhan > > > > > > *From:* amd-gfx <[email protected]> *On Behalf Of *Jacob > Hrbek > *Sent:* 2020/January/30, Thursday 12:18 PM > *To:* [email protected] > *Subject:* Suspecting corrupted VBIOS after update of AMDGPU on AMD7870 > > > > *Hello,* > > I believe that system update that included amdgpu on debian testing (but i > am on LFS) corrupted my VBIOS on AMD7870 (+- 4 hours after the update the > GPU using AMDGPU/Radeon drivers resulted in no output). > > i'm sending this email to inform about possible bug with my findings on > https://gist.github.com/Kreyren/3e55e9a754e58956e1690e38b1888de7 > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2FKreyren%2F3e55e9a754e58956e1690e38b1888de7&data=02%7C01%7CZhan.Liu%40amd.com%7C2fe63c116bbd4cacddc008d7a5d79126%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637160218197554652&sdata=goaR7sDaBxHkmG%2Biln%2FsxEZfSqQ7KTqwbxc9FRxGGMs%3D&reserved=0> > and i would appreciate any help in excluding VBIOS corruption from the > diagnostics. > > *Thanks,* > > - Jacob Hrbek > >
_______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
