[Bug 44432] New: AArch64: assertion fail in alloc_pages_vprot
https://bugs.winehq.org/show_bug.cgi?id=44432 Bug ID: 44432 Summary: AArch64: assertion fail in alloc_pages_vprot Product: Wine Version: 3.0 Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: piotr.caban(a)gmail.com Distribution: --- Wine sometimes fail to start in qemu_aarch64 + ubuntu16.04 because of assertion fail in alloc_pages_vprot function. It looks like it's related to address space limit being set incorrectly in virtual_init: #ifdef _WIN64 address_space_limit = (void *)(((1UL << 47) - 1) & ~page_mask); After changing it to: address_space_limit = (void*)(((1UL << 48) - 1) & ~page_mask); wine starts successfully. According to arm8 documentation 48-bit virtual memory addressing is used. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de --- Comment #1 from André H. <nerv(a)dawncrow.de> --- See https://www.winehq.org/pipermail/wine-devel/2017-November/119629.html Which does the opposite of your suggestion Maybe we should detect it more dynamical -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|AArch64: assertion fail in |AArch64: assertion fail in |alloc_pages_vprot |alloc_pages_vprot with | |qemu_aarch64 Ubuntu 16.04 CC| |focht(a)gmx.net --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, is this still a problem with Ubuntu 18.x or 20.x builds for aarch64? Also what does "Wine sometimes fail to start" mean? Wine builtin applications? If yes, what's the Linux kernel version and kernel config settings related to VA bits (CONFIG_ARM64_VA_BITS_xxx). https://source.winehq.org/git/wine.git/blob/056c9df854817670dc4fb9c095cba29c... Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 --- Comment #3 from Alexandre Julliard <julliard(a)winehq.org> --- I expect that it's fixed by 5b1fc819081dd52225fb9df0ee07bbdc9b23ca19. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 --- Comment #4 from Piotr Caban <piotr.caban(a)gmail.com> --- There was assertion failure in alloc_pages_vprot. I've seen it while trying to run some wine tests. I'm expecting it to be fixed now. I'll update the bug after retesting but I don't think it will be meaningful taking in account that I will need to switch to clang and update to newer version of ubuntu. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 Piotr Caban <piotr.caban(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |5b1fc819081dd52225fb9df0ee0 | |7bbdc9b23ca19 --- Comment #5 from Piotr Caban <piotr.caban(a)gmail.com> --- It works now (in Ubuntu 20.04, wine compiled with clang). Marking as fixed by 5b1fc819081dd52225fb9df0ee07bbdc9b23ca19 (I didn't check if this is the patch that actually fixed it). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.10. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 Steve Ebey <eaglecomputers.ok(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eaglecomputers.ok(a)gmail.com --- Comment #7 from Steve Ebey <eaglecomputers.ok(a)gmail.com> --- neboot.exe: unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed. plorer.exe: unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed. Wine staging 5.10, from fedora 32 distro repo at winehq. Running AMD Fx 8350, 32 gig ram, Geforce 1050 with 2gig ram. Problem started with wine staging 5.8 and has not been fixed yet. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44432 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #8 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Steve Ebey from comment #7)
neboot.exe: unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed. plorer.exe: unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed.
Wine staging 5.10, from fedora 32 distro repo at winehq. Running AMD Fx 8350, 32 gig ram, Geforce 1050 with 2gig ram. Problem started with wine staging 5.8 and has not been fixed yet.
This is bug 49326, which is unrelated. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla