linux-kernel - Re: IOMMU vs Ryzen embedded EMMC controller

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 27 Sep 2019 11:47:50 +0200
From:   Kurt Garloff <kurt@...loff.de>
To:     Joerg Roedel <joro@...tes.org>, Jiri Kosina <jikos@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Shah Nehal-Bakulchandra <Nehal-bakulchandra.Shah@....com>
Subject: Re: IOMMU vs Ryzen embedded EMMC controller

Hi Jörg,

On 25/09/2019 17:42, Joerg Roedel wrote:
> On Wed, Sep 25, 2019 at 05:27:32PM +0200, Jiri Kosina wrote:
>> On Sat, 21 Sep 2019, Kurt Garloff wrote:
>>> [12916.740274] mmc0: sdhci: ============================================
>>> [12916.740337] mmc0: error -5 whilst initialising MMC card
>> Do you have BAR memory allocation failures in dmesg with IOMMU on?

No. The device is *not* treated as PCI device and I still 
think that this is the source of the evil.

>> Actually, sharing both working and non-working dmesg, as well as
>> /proc/iomem contents, would be helpful.
> Yes, can you please grab dmesg from a boot with iommu enabled and add
> 'amd_iommu_dump' to the kernel command line? That should give some hints
> on what is going on.

For now I attach a dmesg and iomem from the boot with IOMMU 
enabled.
Nothing much interesting without IOMMU, sdhci-acpi there 
just works -- let me know if you still want me to send the 
kernel msg.

Thanks for looking into this!

-- 

Kurt Garloff <kurt@...loff.de>
Cologne, Germany


View attachment "iomem.iommu.txt" of type "text/plain" (3161 bytes)

View attachment "dmesg.iommu.txt" of type "text/plain" (112242 bytes)