IO_PAGE_FAULTS when enabling IOMMU in coreboot for ASUS F2A85-M

2013-10-14 Thread Paul Menzel
Dear Linux folks, Rudolf Marek pushed a patch for review to enable the IOMMU in coreboot for the ASUS F2A85-M [1]. With this patch applied, Linux, I think 3.10-rc1, shows IO_PAGE_FAULT messages. $ dmesg […] [0.00] ACPI: IVRS bf144e10 00070 (v02 AMD AMDI

Re: [PATCH] iommu/amd: Fix event counter availability check

2020-05-31 Thread Paul Menzel
caf310d16cc5e2f851c048cd597f5437013368 Thank you very much for fixing this issue, which is almost two years old for me. Tested-by: Paul Menzel MSI MSI MS-7A37/B350M MORTAR with AMD Ryzen 3 2200G Link: https://lore.kernel.org/linux-iommu/20180727102710.ga6...@8bytes.org/ Kind regards, Paul [1

[PATCH] iommu/amd: Print extended features in one line to fix divergent log levels

2020-06-16 Thread Paul Menzel
oglevel. */ #define pr_cont(fmt, ...) \ printk(KERN_CONT fmt, ##__VA_ARGS__) So, remove the line break, so only one line is logged. Fixes: 3928aa3f57 ("iommu/amd: Detect and enable guest vAPIC support") Cc: Suravee Suthikulpanit Cc: iommu@lists.linux-foundation.org Signed-off-by: Paul Men

Messages to kexec@ get moderated (was: Crash kernel with 256 MB reserved memory runs into OOM condition)

2019-08-15 Thread Paul Menzel
Dear Dave, On 13.08.19 04:46, Dave Young wrote: > On 08/13/19 at 10:43am, Dave Young wrote: […] > The question is to Paul, also it would be always good to cc kexec mail > list for kexec and kdump issues. kexec@ was CCed in my original mail, but my messages got moderated. It’d great if you ch

Re: Crash kernel with 256 MB reserved memory runs into OOM condition

2019-09-04 Thread Paul Menzel
Dear Dave, Thank you for your replies. On 2019-08-13 04:54, Dave Young wrote: > On 08/13/19 at 10:46am, Dave Young wrote: >> On 08/13/19 at 10:43am, Dave Young wrote: >>> On 08/12/19 at 11:50am, Michal Hocko wrote: >>>> On Mon 12-08-19 11:42:33, Paul Menzel wro

Re: Crash kernel with 256 MB reserved memory runs into OOM condition

2019-08-12 Thread Paul Menzel
Dear Michal, On 12.08.19 11:50, Michal Hocko wrote: > On Mon 12-08-19 11:42:33, Paul Menzel wrote: >> On a Dell PowerEdge R7425 with two AMD EPYC 7601 (total 128 threads) and >> 1 TB RAM, the crash kernel with 256 MB of space reserved crashes. >> >> Please find the

Re: [PATCH] iommu/amd: Fix event counter availability check

2021-02-21 Thread Paul Menzel
Dear Alexander, Am 01.06.20 um 04:48 schrieb Paul Menzel: […] Am 31.05.20 um 09:22 schrieb Alexander Monakov: Adding Shuah Khan to Cc: I've noticed you've seen this issue on Ryzen 2400GE; can you have a look at the patch? Would be nice to know if it fixes the problem for you too.

Re: [PATCH] iommu/amd: Fix event counter availability check

2021-02-21 Thread Paul Menzel
Dear Suravee, Am 17.09.20 um 19:55 schrieb Alexander Monakov: On Tue, 16 Jun 2020, Suravee Suthikulpanit wrote: Instead of blindly moving the code around to a spot that would just work, I am trying to understand what might be required here. In this case, the init_device_table_dma()should not

Re: [PATCH] iommu/amd: Fix event counter availability check

2021-02-24 Thread Paul Menzel
Dear Suravee, Thank you for your reply. Am 22.02.21 um 18:59 schrieb Suravee Suthikulpanit: This fix has been accepted in the upstream recently. https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/commit/?h=x86/amd Indeed. Linux pulled also pulled this [1]. Could you please g

Re: [PATCH] iommu/amd: Fix event counter availability check

2021-02-26 Thread Paul Menzel
[cc: +suravee, +jörg] Dear Alex, dear Shuah, dear Suravee, dear Jörg, Am 03.06.20 um 08:54 schrieb Alexander Monakov: On Tue, 2 Jun 2020, Shuah Khan wrote: I changed the logic to read config to get max banks and counters before checking if counters are writable and tried writing to all. The

[PATCH] Revert "iommu/amd: Fix performance counter initialization"

2021-03-03 Thread Paul Menzel
: David Coe Cc: iommu@lists.linux-foundation.org Signed-off-by: Paul Menzel --- drivers/iommu/amd/init.c | 45 ++-- 1 file changed, 11 insertions(+), 34 deletions(-) diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c index 9126efcbaf2c..af195f11d254

Re: [PATCH] Revert "iommu/amd: Fix performance counter initialization"

2021-03-18 Thread Paul Menzel
Dear Jörg, dear Suravee, Am 03.03.21 um 15:10 schrieb Alexander Monakov: On Wed, 3 Mar 2021, Suravee Suthikulpanit wrote: Additionally, alternative proposed solutions [1] were not considered or discussed. [1]:https://lore.kernel.org/linux-iommu/alpine.lnx.2.20.13.2006030935570.3...@monopod.i

Re: [PATCH] iommu/amd: Fix extended features logging

2021-04-10 Thread Paul Menzel
e same solution is used in EFI and uvesafb drivers. Thank you for fixing this. Fixes: 9a295ff0ffc9 ("iommu/amd: Print extended features in one line to fix divergent log levels") Signed-off-by: Alexander Monakov Cc: Paul Menzel Cc: Joerg Roedel Cc: Suravee Suthikulpanit Cc: iommu@lists

[PATCH] iommu/amd: Put newline after closing bracket in warning

2021-04-12 Thread Paul Menzel
er Signed-off-by: Paul Menzel --- drivers/iommu/amd/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c index 321f5906e6ed..f7e31018cd0b 100644 --- a/drivers/iommu/amd/init.c +++ b/drivers/iommu/amd/init.c @@ -1837,7 +1837,7

AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).

2021-04-12 Thread Paul Menzel
Dear Linux folks, On the Dell OptiPlex 5055, Linux warns about an EFR mismatch in the firmware. ``` […] [0.00] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 […] [1.479774] smpboot: CPU0: AMD Ryzen 5 PRO 1500 Quad-Core Processor (family: 0x17, model: 0x1

Re: [RESEND PATCH v2] iommu/amd: Fix extended features logging

2021-05-12 Thread Paul Menzel
lt; ARRAY_SIZE(feat_str); ++i) { if (iommu_feature(iommu, (1ULL << i))) pr_cont(" %s", feat_str[i]); base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717 Reviewed-by: Paul Menzel Kind regards, Paul ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu

Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).

2021-09-14 Thread Paul Menzel
[Cc: +Dell Linux kernel client team] Dear Linux folks, Am 12.04.21 um 20:07 schrieb Paul Menzel: On the Dell OptiPlex 5055, Linux warns about an EFR mismatch in the firmware. ``` […] [    0.00] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 […] [    1.479774

Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).

2021-09-14 Thread Paul Menzel
[Cc: +Mario from AMD] Dear Jörg, Am 14.09.21 um 14:09 schrieb Jörg Rödel: On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50). The reason is most likely that the latest firmware still reports a

Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).

2021-09-14 Thread Paul Menzel
[Use Mario’s current address] Am 15.09.21 um 00:15 schrieb Paul Menzel: [Cc: +Mario from AMD] Dear Jörg, Am 14.09.21 um 14:09 schrieb Jörg Rödel: On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50

Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).

2021-09-15 Thread Paul Menzel
Dear Jörg, Am 15.09.21 um 10:30 schrieb Jörg Rödel: Mainly DELL should look at this, because it is their BIOS which is responsible for this inconsistency. I am not so sure about that, as today’s (x86) firmware often consists of platform initialization (PI) code (or firmware support package (

Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).

2021-09-15 Thread Paul Menzel
Dear Linux folks, Am 15.09.21 um 00:17 schrieb Paul Menzel: [Use Mario’s current address] Am 15.09.21 um 00:15 schrieb Paul Menzel: [Cc: +Mario from AMD] Am 14.09.21 um 14:09 schrieb Jörg Rödel: On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns

I got an IOMMU IO page fault. What to do now?

2021-10-25 Thread Paul Menzel
Dear Linux folks, On a Dell OptiPlex 5055, Linux 5.10.24 logged the IOMMU messages below. (GPU hang in amdgpu issue #1762 [1] might be related.) $ lspci -nn -s 05:00.0 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340

Re: I got an IOMMU IO page fault. What to do now?

2021-10-25 Thread Paul Menzel
Dear Christian, Thank you for your reply. On 25.10.21 13:23, Christian König wrote: not sure how the IOMMU gives out addresses, but the printed ones look suspicious to me. Something like we are using an invalid address like -1 or similar. Can you try that on an up to date kernel as well?

Re: I got an IOMMU IO page fault. What to do now?

2021-10-27 Thread Paul Menzel
Dear Robin, On 25.10.21 18:01, Robin Murphy wrote: On 2021-10-25 12:23, Christian König wrote: not sure how the IOMMU gives out addresses, but the printed ones look suspicious to me. Something like we are using an invalid address like -1 or similar. FWIW those look like believable DMA add

How to reduce PCI initialization from 5 s (1.5 s adding them to IOMMU groups)

2021-11-05 Thread Paul Menzel
Dear Linux folks, On a PowerEdge T440/021KCD, BIOS 2.11.2 04/22/2021, Linux 5.10.70 takes almost five seconds to initialize PCI. According to the timestamps, 1.5 s are from assigning the PCI devices to the 142 IOMMU groups. ``` $ lspci | wc -l 281 $ dmesg […] [2.918411] PCI: Using host b

Re: How to reduce PCI initialization from 5 s (1.5 s adding them to IOMMU groups)s

2021-11-05 Thread Paul Menzel
Dear Linux folks, Am 05.11.21 um 12:56 schrieb Paul Menzel: On a PowerEdge T440/021KCD, BIOS 2.11.2 04/22/2021, Linux 5.10.70 takes almost five seconds to initialize PCI. According to the timestamps, 1.5 s are from assigning the PCI devices to the 142 IOMMU groups. ``` $ lspci | wc -l 281

Re: How to reduce PCI initialization from 5 s (1.5 s adding them to IOMMU groups)

2021-11-06 Thread Paul Menzel
Dear Bjorn, Thank you for your quick reply. Am 05.11.21 um 19:53 schrieb Bjorn Helgaas: On Fri, Nov 05, 2021 at 12:56:09PM +0100, Paul Menzel wrote: On a PowerEdge T440/021KCD, BIOS 2.11.2 04/22/2021, Linux 5.10.70 takes almost five seconds to initialize PCI. According to the timestamps

Re: How to reduce PCI initialization from 5 s (1.5 s adding them to IOMMU groups)

2021-11-09 Thread Paul Menzel
Dear Krzysztof, Thank you for your reply. Am 08.11.21 um 18:18 schrieb Krzysztof Wilczyński: On a PowerEdge T440/021KCD, BIOS 2.11.2 04/22/2021, Linux 5.10.70 takes almost five seconds to initialize PCI. According to the timestamps, 1.5 s are from assigning the PCI devices to the 142 IOMMU g

Re: How to reduce PCI initialization from 5 s (1.5 s adding them to IOMMU groups)

2021-11-09 Thread Paul Menzel
Dear Robin, Thank you for your reply. Am 09.11.21 um 16:31 schrieb Robin Murphy: On 2021-11-06 10:42, Paul Menzel wrote: Am 05.11.21 um 19:53 schrieb Bjorn Helgaas: On Fri, Nov 05, 2021 at 12:56:09PM +0100, Paul Menzel wrote: On a PowerEdge T440/021KCD, BIOS 2.11.2 04/22/2021, Linux

[PATCH] iommu/amd: Fix typo in *glues … together* in comment

2021-12-17 Thread Paul Menzel
Signed-off-by: Paul Menzel --- drivers/iommu/amd/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/amd/init.c b/drivers/iommu/amd/init.c index 1eacd43cb436..29d55a99c39f 100644 --- a/drivers/iommu/amd/init.c +++ b/drivers/iommu/amd/init.c @@ -1523,7 +1523,7

nvme: IO_PAGE_FAULT logged with Intel SSDPEKKF512G8

2022-01-18 Thread Paul Menzel
Dear Linux folks, On a Dell OptiPlex 5055 with an Intel SSDPEKKF512G8, Linux 5.10.82 reported an IO_PAGE_FAULT error. This is the first and only time this has happened. $ dmesg --level=err [4.194306] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0x

Re: nvme: IO_PAGE_FAULT logged with Intel SSDPEKKF512G8

2022-01-18 Thread Paul Menzel
Dear Keith, Thank you for your quick response. Am 18.01.22 um 17:53 schrieb Keith Busch: On Tue, Jan 18, 2022 at 03:32:45PM +0100, Paul Menzel wrote: On a Dell OptiPlex 5055 with an Intel SSDPEKKF512G8, Linux 5.10.82 reported an IO_PAGE_FAULT error. This is the first and only time this has

Re: MSI B350M MORTAR: `AMD-Vi: Unable to write to IOMMU perf counter.` and `pci 0000:00:00.2: can't derive routing for PCI INT A`

2018-07-23 Thread Paul Menzel
Dear Jörg, On 07/20/18 14:31, Jörg Rödel wrote: > On Tue, Jul 17, 2018 at 06:02:07PM +0200, Paul Menzel wrote: >> $ dmesg >> […] >> [0.145696] calling pci_iommu_init+0x0/0x3f @ 1 >> [0.145719] AMD-Vi: Unable to write to IOMMU perf counter. > > This i

Re: MSI B350M MORTAR: `AMD-Vi: Unable to write to IOMMU perf counter.` and `pci 0000:00:00.2: can't derive routing for PCI INT A`

2018-07-27 Thread Paul Menzel
Dear Jörg, On 07/27/18 10:27, Jörg Rödel wrote: > On Mon, Jul 23, 2018 at 12:09:37PM +0200, Paul Menzel wrote: >>> or the BIOS did not enable the performance counter feature in the IOMMU >>> hardware. >> >> Is it possible to check that from the OS side?