lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <YYBS7q/VUjbTuZYO@llamedos.localdomain>
Date:   Mon, 1 Nov 2021 20:49:50 +0000
From:   Ken Moffat <zarniwhoop@...world.com>
To:     "Zhu, James" <James.Zhu@....com>
Cc:     "Deucher, Alexander" <Alexander.Deucher@....com>,
        "Zhang, Yifan" <Yifan1.Zhang@....com>,
        "Kuehling, Felix" <Felix.Kuehling@....com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: amdgpu hang on picasso

On Mon, Nov 01, 2021 at 06:32:11PM +0000, Zhu, James wrote:
> [AMD Official Use Only]
> 
> Hi Kent,
> 
 just Ken, not Kent

> You also can share /var/log/kern.log
> 
> I saw some issue from your attached log:
> 
> [    2.135852] amdgpu 0000:09:00.0: Direct firmware load for amdgpu/picasso_ta.bin failed with error -2
> [    2.135854] amdgpu 0000:09:00.0: amdgpu: psp v10.0: Failed to load firmware "amdgpu/picasso_ta.bin"
> [    2.135856] amdgpu 0000:09:00.0: amdgpu: PSP runtime database doesn't exist
> Can you try latest firmwre?
> 

I didn't know that newer firmware was available, what I had dates
from when I got this box.  I've just downloaded
linux-firmware-20211027.tar.gz, last time I looked at firmware I
needed to get the individual files.  So, I didn't have that
picasso_ta and I do now.  But it still doesn't load - the mention of
a runtime database makes me think it might be for wifi ?  If so,
this machine is wired only.

> [    2.308871] amdgpu 0000:09:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x10438a380 flags=0x0070]
> Can you try adding amd_iommu=off in grub option?
> 
I forgot to do that until I came to reply.  I've attached the kernel
log from running with only the updated firmware as sys.log.gz

Turning off the iommu was pretty disastrous, screen went blank
before I could login.  Turns out it had oopsed (from 2.316893
seconds in the attached sys.log.iommu_off.gz).

Thanks.

żen


Download attachment "sys.log.gz" of type "application/x-gunzip" (19277 bytes)

Download attachment "sys.log.iommu_off.gz" of type "application/x-gunzip" (18123 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ