[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.

WineHQ Bugzilla wine-bugs at winehq.org
Mon Sep 30 09:30:07 CDT 2019


https://bugs.winehq.org/show_bug.cgi?id=47731

--- Comment #24 from Sveinar Søpler <cybermax at dexter.no> ---
(In reply to Steve Ebey from comment #23)
> Still crashed. Not sure what else to try.

Not really sure what else to try. Might try toggling the BIOS option IOMMU to
see if it is creating some weirdness, but i doubt it would be that.

> Quote from https://download.nvidia.com/XFree86/Linux-x86_64/340.104/README/dma_issues.html

On AMD's AMD64 platform, the size of the IOMMU can be configured in the system
BIOS or, if no IOMMU BIOS option is available, using the 'iommu=memaper' kernel
parameter. This kernel parameter expects an order and instructs the Linux
kernel to create an IOMMU of size 32 MB^order overlapping physical memory. If
the system's default IOMMU is smaller than 64 MB, the Linux kernel
automatically replaces it with a 64 MB IOMMU.

To reduce the risk of stability problems as a result of IOMMU space exhaustion
on the X86-64 platform, the NVIDIA Linux driver internally limits its use of
these interfaces. By default, the driver will not use more than 60 MB of IOMMU
space, leaving at least 4 MB for the rest of the system (assuming a 64 MB
IOMMU).

I only mention this, as the use of "IOMMU" has come up as a troubleshooting
thing on various DXVK posts. It might not be in the right direction, but
probably will not hurt to try? :)

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.


More information about the wine-bugs mailing list