https://bugs.winehq.org/show_bug.cgi?id=52535
Bug ID: 52535 Summary: wine: Unhandled page fault on execute access to 00007FEBBDDFAA00 at address 00007FEBBDDFAA00 (thread 0148), starting debugger... Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: alois.schloegl@gmail.com Distribution: ---
After installing wine-7.1 (staging) according to these instructions https://wiki.winehq.org/Debian on new, powerful machine, and start a new wineprefix, I see this error message.
... 0088:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 00ec:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00ec:err:winediag:nodrv_CreateWindow The explorer process failed to start. wine: configuration in L"/nfs/scistore/schloegl/.wine" has been updated. wine: Unhandled page fault on execute access to 00007FEBBDDFAA00 at address 00007FEBBDDFAA00 (thread 0148), starting debugger... wine: Unhandled page fault on execute access to 00007F95DEDBDA00 at address 00007F95DEDBDA00 (thread 015c), starting debugger...
and than waits, an there is no obvious progress. No dialog window about "wine configuration of .wine is being updated, please wait" is shown.
When I stop the session, and login in again, ~/.wine is partially generated. and "wineboot -i" the following is shown:
$ wineboot -i 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.1 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. wine: Unhandled page fault on execute access to 00007F7D0A5A3A00 at address 00007F7D0A5A3A00 (thread 0068), starting debugger... wine: Unhandled page fault on execute access to 00007F9AF9D15510 at address 00007F9AF9D15510 (thread 00c4), starting debugger... wine: Unhandled page fault on execute access to 00007FD301331A00 at address 00007FD301331A00 (thread 00d8), starting debugger... wine: Unhandled page fault on execute access to 00007FBED1E63510 at address 00007FBED1E63510 (thread 00ec), starting debugger...
0108:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0108, blocked by 0100, retrying (60 sec) 0110:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0110, blocked by 00e0, retrying (60 sec) 0114:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0114, blocked by 0034, retrying (60 sec) 010c:err:sync:RtlpWaitForCriticalSection section 0000000170067620 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 010c, blocked by 00f4, retrying (60 sec)
I tried also wine-devel (7.1) and wine-stable(7.0) with the same result.
The software is Debian11 with cuda Driver Version: 470.103, like we have it installed on several other machines as well. The main difference is that this is a rather powerful machine: (128 threads, 1 TB RAM, 8xA40 GPU's).
$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 43 bits physical, 48 bits virtual CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 2 Core(s) per socket: 32 Socket(s): 2 NUMA node(s): 2 Vendor ID: AuthenticAMD CPU family: 23 Model: 49 Model name: AMD EPYC 7452 32-Core Processor Stepping: 0 Frequency boost: enabled CPU MHz: 1497.039 CPU max MHz: 3364.3550 CPU min MHz: 1500.0000 BogoMIPS: 4700.33 Virtualization: AMD-V L1d cache: 2 MiB L1i cache: 2 MiB L2 cache: 32 MiB L3 cache: 256 MiB NUMA node0 CPU(s): 0-31,64-95 NUMA node1 CPU(s): 32-63,96-127 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Full AMD retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_ts c rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cm p_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_ l3 cdp_l3 hw_pstate sme ssbd mba sev ibrs ibpb stibp vmmcall sev_es fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xs avec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_s cale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip rdpid overflow_recov succor smca root@gpu230:~# nvidia-smi Thu Feb 10 18:08:21 2022 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 470.103.01 Driver Version: 470.103.01 CUDA Version: 11.4 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 NVIDIA A40 On | 00000000:01:00.0 Off | 0 | | 0% 25C P8 11W / 300W | 36MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 1 NVIDIA A40 On | 00000000:25:00.0 Off | 0 | | 0% 25C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 2 NVIDIA A40 On | 00000000:41:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 3 NVIDIA A40 On | 00000000:61:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 4 NVIDIA A40 On | 00000000:81:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 5 NVIDIA A40 On | 00000000:A1:00.0 Off | 0 | | 0% 23C P8 11W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 6 NVIDIA A40 On | 00000000:C1:00.0 Off | 0 | | 0% 23C P8 19W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ | 7 NVIDIA A40 On | 00000000:E1:00.0 Off | 0 | | 0% 23C P8 20W / 300W | 4MiB / 45634MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+
Do you have any idea what is wrong here ? Let me know if I should run further tests.
https://bugs.winehq.org/show_bug.cgi?id=52535
--- Comment #1 from Alois Schlögl alois.schloegl@gmail.com ---
This is not a bug in wine, but some other software (glxinfo, glxgears) is also affected on this platform. Sorry for the noise.
https://bugs.winehq.org/show_bug.cgi?id=52535
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|wine: Unhandled page fault |wine crashes on start |on execute access to | |00007FEBBDDFAA00 at address | |00007FEBBDDFAA00 (thread | |0148), starting debugger... | Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #2 from Gijs Vermeulen gijsvrm@gmail.com --- Resolving.
https://bugs.winehq.org/show_bug.cgi?id=52535
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Gijs Vermeulen gijsvrm@gmail.com --- Closing.