Problem with wine preloader: Warning: failed to reserve range 00000000-60000000
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wine |
Invalid
|
Medium
|
|||
wine (Baltix) |
New
|
Undecided
|
Unassigned | ||
wine (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Wine Team | ||
Bug Description
Binary package hint: wine
Run wine or winecfg with or without arguments.
Feisty 7.04
wine 0.9.33
Related branches
CVE References
Stephan Rügamer (sruegamer) wrote : | #1 |
Changed in wine: | |
assignee: | nobody → ubuntu-wine |
Bart Kroon (bart-kroon) wrote : | #2 |
I already removed the ~/.wine directory during testing and it doesn't even get created when I run wine:
bart@pc67243857
ls: .wine: No such file or directory
bart@pc67243857
preloader: Warning: failed to reserve range 00000000-60000000
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
bart@pc67243857
wine winebrowser wineconsole winedump winegcc winemaker wineprefixcreate wineserver
wine-auto winebuild winecpp winefile wine-kthread winemine wine-preloader wineshelllink
wineboot winecfg winedbg wineg++ winelauncher winepath wine-pthread winhelp
bart@pc67243857
preloader: Warning: failed to reserve range 00000000-60000000
wine: failed to initialize: /usr/lib/
bart@pc67243857
i486-linux-gnu-gcc: no input files
winegcc: i486-linux-gnu-gcc failed.
bart@pc67243857
preloader: Warning: failed to reserve range 00000000-60000000
wine: failed to initialize: /usr/lib/
bart@pc67243857
preloader: Warning: failed to reserve range 00000000-60000000
wine: failed to initialize: /usr/lib/
bart@pc67243857
ls: .wine: No such file or directory
bart@pc67243857
Do you want me to test something else?
Scott Ritchie (scottritchie) wrote : | #3 |
Hmmm....
Do you by any chance have some special security settings enabled? It looks like there's a problem with prelink doing its thing.
Bart Kroon (bart-kroon) wrote : Re: [Bug 114025] Re: Problem with wine preloader: Warning: failed to reserve range 00000000-60000000 | #4 |
Security is as out-of-the-box. I installed Edgy then after some months when
Feisty became the stable version I upgraded to Feisty.
LAN is by Ethernet with DHCP and Internet is via a proxy but I don't think
you need internet to run wine.
I'm not the only one having this error:
http://
Wish I could help more but I have no clue about this error myself,
Bart
2007/5/29, Scott Ritchie <email address hidden>:
>
> Hmmm....
>
> Do you by any chance have some special security settings enabled? It
> looks like there's a problem with prelink doing its thing.
>
> --
> Problem with wine preloader: Warning: failed to reserve range
> 00000000-60000000
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
-------
Bart Kroon
Sint Jansstraat 24
5507 ND Veldhoven (Oerle)
msn: <email address hidden>
Tel.: +31 40 2377667
GSM: +31 6 27248320
http://
Bart Kroon (bart-kroon) wrote : | #5 |
Plz remove my signature if possible. I made a mistake with my e-mailprogram.
Scott Ritchie (scottritchie) wrote : | #6 |
Are things working for you in Gutsy?
Bart Kroon (bart-kroon) wrote : | #7 |
Solved now
2007/10/23, Scott Ritchie <email address hidden>:
>
> Are things working for you in Gutsy?
>
> --
> Problem with wine preloader: Warning: failed to reserve range
> 00000000-60000000
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
-------
Bart Kroon
Sint Jansstraat 24
5507 ND Veldhoven (Oerle)
msn: <email address hidden>
Tel.: +31 40 2377667
GSM: +31 6 27248320
http://
zjaak (zjaakie) wrote : | #8 |
Ive got the problem now.. So how did you solve it??
Dan Kegel (dank) wrote : | #9 |
zjaak, what version of Ubuntu and what version of Wine are you using?
Nemes Ioan Sorin (nemes-sorin) wrote : | #10 |
I have to subscribe to this bug, Hardy Heron up to date, wine-0.9.52 || No problems with wine-0.9.51
Roderick B. Greening (roderick-greening) wrote : | #11 |
I have this too under Hardy Heron with wine 0.9.52, but not when it was 0.9.51. What is an appropriate way to revert to 0.9.51 to verify problem does not exist under 0.9.51? I tried to PIN 0.9.51 with a 1001 priority, but I believe that 0.9.51 is not in the repo now.
Dan Kegel (dank) wrote : | #12 |
On Jan 8, 2008 12:23 PM, Roderick Greening <email address hidden> wrote:
> I have this too under Hardy Heron with wine 0.9.52, but not when it was
> 0.9.51. What is an appropriate way to revert to 0.9.51 to verify problem
> does not exist under 0.9.51? I tried to PIN 0.9.51 with a 1001 priority,
> but I believe that 0.9.51 is not in the repo now.
You can grab gutsy's 0.9.51 from
http://
it will probably work on Hardy.
Let me know if that works for you.
Kees Cook (kees) wrote : | #13 |
This is likely related to the extra security changes added to /etc/sysctl.conf (vm.mmap_min_addr = 65536). As a work-around, set this to 0. Hopefully wine can be built in a way that it doesn't have to reserve the lower 64k all the time.
Brian Murray (brian-murray) wrote : | #14 |
I tried the workaround mentioned by Kees and set '/proc/
wine: Unhandled page fault on read access to 0x00000000 at address 0xf7da5d03 (thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0xf7da5d03).
I can provide a full register dump, stack dump and backtrace if needed.
Changed in wine: | |
importance: | Undecided → High |
status: | New → Confirmed |
Brian Murray (brian-murray) wrote : | #15 |
- crash report Edit (14.0 KiB, text/plain)
Here is the crash with /proc/sys/
Brian Murray (brian-murray) wrote : | #16 |
The error is slightly different with /proc/sys/
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
wine: Unhandled page fault on read access to 0x00000000 at address 0xf7d81d03 (thread 0009), starting debugger...
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0xf7d81d03).
From there on out it is the same except for the memory locations.
Brian Murray (brian-murray) wrote : | #17 |
I've been unable to reproduce this on my laptop however, even with mmap_min_addr set to the default winecfg will warn but continue to execute.
Test-tools (roland-verifysoft) wrote : | #18 |
Hello,
I downgraded on hardy from .55 to .51-winehq, as advised above, still the preloader warning:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
But the program works after that....
Roland
Launchpad Janitor (janitor) wrote : | #19 |
This bug was fixed in the package wine - 0.9.56-0ubuntu1
---------------
wine (0.9.56-0ubuntu1) hardy; urgency=low
* New upstream release (LP: #197588)
- Proper handling of OpenGL/Direct3D windows with menu bars.
- Stubs for all the d3dx9_xx dlls.
- Several graphics optimizations.
- Many installer fixes.
- Improved MIME message support.
- Lots of bug fixes.
* debian/rules:
- reset LDFLAGS to let wine not crash anymore, (LP: #191575)
thx to Albert Damen <email address hidden> who came up with this solution.
(http://
- adjust dh_strip call (LP: #185513)
* debian/control:
- remove gcc-3.4 build-dep
- get rid of quilt
* cleaned debian/patches
* Add finnish translation to desktop files (LP: #196916)
* dlls/winealsa.
- let wine use the default alsa device
(http://
* Preloader warning (preloader: Warning: failed to reserve range
00000000-
-- Stephan Hermann <email address hidden> Fri, 22 Feb 2008 20:10:36 +0100
Changed in wine: | |
status: | Confirmed → Fix Released |
In Wine Bugzilla #12516, Michael Abbott (michael-araneidae) wrote : | #20 |
Every run of wine on my system (including wineprefixcreate on a freshly created prefix directory) produces the following messages several times:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
As the message requests, I am reporting it.
This is running Ubuntu Hardy Heron beta with wine version 0.9.59, or as it reports it:
$ wine --version
preloader: Warning: failed to reserve range 00000000-60000000
wine-0.9.59
$
In Wine Bugzilla #12516, Hans-meelstraat (hans-meelstraat) wrote : | #21 |
I'm seeing the same thing on recent Fedora kernels. This command works
around the problem:
$ sudo sysctl -w vm.mmap_min_addr=0
To make this setting permanent, add this line to /etc/sysctl.conf:
vm.mmap_min_addr=0
In Wine Bugzilla #12516, Michael Abbott (michael-araneidae) wrote : | #22 |
> $ sudo sysctl -w vm.mmap_min_addr=0
>
> To make this setting permanent, add this line to /etc/sysctl.conf:
> vm.mmap_min_addr=0
That's very helpful. I think this page http://
Of course, this means that the message from Wine needs to change. Presumably if it's really a problem then it actually needs to be fixed by the user (or the wine install? ... probably a bad idea).
zegenie (zegenie) wrote : | #23 |
This error is back with 0.9.59
Changed in wine: | |
status: | Fix Released → New |
zegenie (zegenie) wrote : | #24 |
- dump from gnome-terminal Edit (1.8 KiB, text/plain)
I get this error when trying to run winecfg on a clean hardy install.
Roberto Cássio Jr. (rcsdnj) wrote : | #25 |
0.9.59 gives the same problem here, too.
Changed in wine: | |
status: | New → Confirmed |
sixtysevenfordpu (stephen-c-moss) wrote : | #26 |
I have two instances of Hardy Heron, 8.04 Beta, one on AMD system, the other on dual proc Intel P3 1mhz system, both are at the same Linux kernel and same version of Wine:
Neither "wineconfig" nor "winecfg" work on this version:
Linux badge 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
wine-0.9.59
Both "wineconfig" and "winecfg" work on this version after reporting bunch of warnings and messages:
Linux doubledog 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
wine-0.9.59
NOTE: I made the above "vm.mmap_min_addr = 0" change to /etc/sysctl.conf on both systems.
I see that on both systems any Windows application that worked in Gutsy Gibon (wine 0.9.51?) start and run without errors on Hardy Heron (wine 0.9.59).
When I install a new Windows program, I do see:
$ wine KEYDC6PLMLPC.exe
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
In the above example, the Windows program installer runs and no further messages like above appear in Konsole. In this example I don't believe the install will complete as it is looking to install "Microsoft DirectX Feb2006 Runtime", "Microsoft Visual C++ 2005 Redistributable Package (x86)", "Microsoft Media Format 9 Series Runtime" and "Microsoft .Net Framework 3.0 x86".
I haven't tried installing other Windows Applications as of yet.
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #27 |
(In reply to comment #2)
> > $ sudo sysctl -w vm.mmap_min_addr=0
> >
> > To make this setting permanent, add this line to /etc/sysctl.conf:
> > vm.mmap_min_addr=0
>
> That's very helpful. I think this page
> http://
> of this setting and probably why it's changed recently.
>
> Of course, this means that the message from Wine needs to change. Presumably
> if it's really a problem then it actually needs to be fixed by the user (or
> the wine install? ... probably a bad idea).
>
I sent a patch to wine-patches:
http://
Justin M. (legendarysim) wrote : | #28 |
I get this same here on the latest (0.9.59) version of WIne. Some applications will give me this error and work and some applications will give me this error and not work at all.
In Wine Bugzilla #12516, Michael Abbott (michael-araneidae) wrote : | #29 |
> http://
The problem with the message in this patch is that it doesn't give the user much help: the key is of course to look in /proc/sys/
I'd suggest changing the text "edit /etc/sysctl.conf" to the more helpful "add the line vm.mmap_min_addr=0 to /etc/sysctl.conf".
Any chance of somebody marking this as CONFIRMED?!
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #30 |
Confirming.
Dan Kegel (dank) wrote : | #31 |
I filed an upstream bug,
http://
though it's possible it can't be fixed in wine alone.
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #32 |
*** Bug 12548 has been marked as a duplicate of this bug. ***
Stephan Rügamer (sruegamer) wrote : | #33 |
Lowering Importance, because it's not harming anyone or destroying the system ;)
After all, it's right, the error came back with .59 :( At least for wine32 on amd64...
I'll check later on my i386, if it's there, too
Regards,
\sh
Changed in wine: | |
importance: | High → Medium |
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #34 |
For completeness, here's the summary I wrote in the dup bug:
The problem
http://
prompted distributions to raise the default for /proc/sys/
or even DEFAULT_
This causes the following error message when starting (some?) wine apps:
Problem with wine preloader: Warning: failed to reserve range
00000000-60000000
See discussion:
https:/
http://
http://
You can check to see if you're on an affected system
by doing "cat /proc/sys/
is nonzero, you're probably running into this.
To work around the problem temporarily, you can change this value
with the command
sudo sysctl -w vm.mmap_min_addr=0
but that value gets reset at boot. To work around the problem more
persistantly, also edit the file /etc/sysctl.conf like this:
# protect bottom 64k of memory from mmap to prevent NULL-dereference
# attacks against potential future kernel security vulnerabilities.
# (Added in kernel 2.6.23.)
-vm.mmap_min_addr = 65536
+vm.mmap_min_addr = 0
http://
a value of 4096 for this.
"Advanced Windows", 3rd edition, says that the memory area 0 to 4095
is not mapped anyway in windows (it's a guard page).
So maybe when Wine is installed, we could somehow change that value
to 4096, and have Wine's preloader happily continue if it can't
map the bottom page of RAM.
Richard (rullger) wrote : | #35 |
It might not be trashing anything but it prevents me from running any Windows programs on my i386. I'm running v0.9.59 packaged with Ubuntu 8.04. Is it possible to drop back to an earlier version that would work with this setup?
Dan Kegel (dank) wrote : | #36 |
Probably not, because the problem comes from a change to the kernel more than from wine.
Have you tried the
sudo sysctl -w vm.mmap_min_addr=0
workaround?
zegenie (zegenie) wrote : | #37 |
Well, after running that command, trying to run winecfg or any wine app does not produce the address errors which it previously did.
Not sure what's affected by that command (explanation appreciated), but looks like it's "back to normal" again :)
thanks.
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #38 |
Alexandre committed a fix today, which makes some progress:
preloader: Warning: failed to reserve range 00000000-00010000
http://
http://
http://
sixtysevenfordpu (stephen-c-moss) wrote : | #39 |
A little more investigation on my part. Found that rather than start winecfg from a Linux Shell prompt, I am able to get that to start on either my AMD system or the Dual Proc Intel by using "Kmenu --> Wine --> Configure Wine" option
Jeremy Vies (jeremy.vies) wrote : | #40 |
The proposed workaround (sudo sysctl -w vm.mmap_min_addr=0) worked for me.
A little investigation made me found this new entry in sysctl.conf:
# protect bottom 64k of memory from mmap to prevent NULL-dereference
# attacks against potential future kernel security vulnerabilities.
# (Added in kernel 2.6.23.)
vm.mmap_min_addr = 65536
I guess it is part of the problem...
In Wine Bugzilla #12516, Alan (mrintegrity) wrote : | #41 |
Hi,
>You can check to see if you're on an affected system
>by doing "cat /proc/sys/
>is nonzero, you're probably running into this.
I think you mean "cat /proc/sys/
Tim Besard (maleadt) wrote : | #42 |
+1 on this bug, and it's a serious one, as it prevented me from running certain applications in wine (like Office 2007) !
Dan Kegel (dank) wrote : | #43 |
A partial workaround was checked in three days ago:
http://
Does that help, Tim?
Richard (rullger) wrote : | #44 |
Thanks for your reply dankegel.
The default of 65536 displays the following errors:
preloader: Warning: failed to reserve range 00000000-60000000
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
err:progress:
fixme:ole:
The suggested value of 4096 displays the following errors
preloader: Warning: failed to reserve range 00000000-60000000
preloader: Warning: failed to reserve range 00000000-60000000
preloader: Warning: failed to reserve range 00000000-60000000
preloader: Warning: failed to reserve range 00000000-60000000
preloader: Warning: failed to reserve range 00000000-60000000
err:progress:
fixme:ole:
The workaround, sudo sysctl -w vm.mmap_min_addr=0 displays the following errors:
err:progress:
fixme:ole:
Richard.
Dan Kegel (dank) wrote : | #45 |
Thanks... but we could guess those messages already. What we're
interested in is whether your app works any better yet with wine from git.
Also, which apps are you trying?
Richard (rullger) wrote : | #46 |
I am trying to get Wordens Telechart 2007 working.
It installed and starts up but after a very short period of time it just disappears with no error messages or crash. One time the graphics became garbled and it hung the system. I've tried making minor changes to the graphics tab in the Wine configuration program but haven't found a solution.
I'm just starting out with Wine so I'll need to have a thorough read through the documentation.
Dan Kegel (dank) wrote : | #47 |
Hanging the system is an indication of bad graphics drivers.
Please take this question to the general Ubuntu or Wine discussion forums.
I don't know of anybody who has Telechart working. I would have
tried but they ask for a credit card.
zegenie (zegenie) wrote : | #48 |
I don't have any problems running applications with wine, even when the error messages are showing, and I've tried the whole range of applications I normally try. So I don't think this error is stopping anything important - to me it's just an annoyance. I've read that 0.9.59 has some regressions, but AFAIKT I'm not affected. Oh, and the sysctl fix did it for me as well.
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #49 |
*** Bug 12645 has been marked as a duplicate of this bug. ***
Dan F (aindfan) wrote : | #50 |
I have upgraded to the latest version (0.9.60) in Ubuntu Hardy and there is now a slightly different Preloader error. It reads:
preloader: Warning: failed to reserve range 00000000-00010000
I experienced the original preloader error message in 0.9.59 as well. The sysctl workaround gets rid of the error in this version just like in the previous one.
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #51 |
*** Bug 12746 has been marked as a duplicate of this bug. ***
Puchti (puchta-h-deactivatedaccount) wrote : | #52 |
i have the same problem. its the first time i use wine at all..
ubuntu 8.04 amd64 - wine 0.9.59
notepad and winecfg worked, but several warnings like
"preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
i've tried the fix "sudo sysctl -w vm.mmap_min_addr=0" - no more warnings.
later i will try to get CS1.6 working..
liuxl (anglesccs) wrote : | #53 |
preloader: Warning: failed to reserve range 00000000-00010000
Fabio Marzocca (thesaltydog) wrote : | #54 |
A workaround is this:
sudo sysctl -w vm.mmap_min_addr=0
But it will switch back to previous situation at each boot.
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #55 |
The URL to send users to for explanations about this is
http://
Kai Blin (kai.blin) wrote : | #56 |
Same cause, we just split up the loading of the low memory ranges a bit more.
Note that this is caused by Ubuntu security defaults, not by Wine, and it's not an error but a warning. Use the workaround described above.
Fabio Marzocca (thesaltydog) wrote : | #57 |
@Kai,
I agree it is a warning, but it disables wine applications to be run...
Dan Kegel (dank) wrote : | #58 |
Fabrio, with current wine, only DOS or Win16 apps need the workaround, I think;
regular win32 apps are fine. Also, you don't have to give that command at each
boot if you change /etc/sysctl.conf to make it permanent.
We are now directing users who run into this problem to the page
http://
which has the workaround, including the /etc/sysctl.conf change.
In Wine Bugzilla #12516, Lei Zhang (thestig-google) wrote : | #59 |
*** Bug 12797 has been marked as a duplicate of this bug. ***
Changed in wine: | |
status: | Unknown → Confirmed |
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #60 |
*** Bug 12815 has been marked as a duplicate of this bug. ***
t.cornall (xerxesdaphat) wrote : | #61 |
It doesn't seem to just affect DOS/WIN16 -- it was causing MS Word 2000 to crash after a few seconds, under both wine 0.9.60 and, interestingly, Crossover Office.
The change to /etc/sysctl.conf fixes it. Thanks for the information.
Andre Brait (andrebrait) wrote : | #62 |
Have someone tried to disable apparmor?
It started to happen in Feisty, isn't it?
Andre Brait (andrebrait) wrote : | #63 |
Forget abou that...
I couldn't try because AppArmor in builtin in HArdy, but changing the value in /etc/sysctl.conf seems to be the only alternative
Motin (motin) wrote : | #64 |
Will this be fixed in future versions of wine and/or the kernel?
The comments on this setting in sysctl.conf is:
# protect bottom 64k of memory from mmap to prevent NULL-dereference
# attacks against potential future kernel security vulnerabilities.
# (Added in kernel 2.6.23.)
vm.mmap_min_addr = 65536
... and I kinda like protections against "future kernel security vulnerabilities", for whatever impact it may or may not have on my system's security.
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #65 |
*** Bug 12847 has been marked as a duplicate of this bug. ***
Lubosz Sarnecki (lubosz) wrote : | #66 |
In Wine Bugzilla #12516, Alexandre Julliard (julliard) wrote : | #67 |
*** Bug 12867 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Christoph Korn (c-korn) wrote : | #68 |
Will there be a fix for this in wine?
I do not like the option to open "potential future kernel security vulnerabilities".
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #69 |
It's possible we could avoid mapping the very
lowest page (I've read Windows does this);
that would make the workaround be a little less
insecure.
MuddBuddha (thomas-packers) wrote : | #70 |
I tried the work around, but still end up with an error:
err:seh:
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #71 |
(In reply to comment #17)
> Will there be a fix for this in wine?
The fix is already in Wine since version 0.9.60.
> I do not like the option to open "potential future kernel security
> vulnerabilities".
In the most cases there is no potential security problems, there are
speculations about them. In this case not mapping a zero page can
potentially increase security for 0.001% applications, which are so
buggy, that nobody would use them anyway.
Erik de Castro Lopo (erikd) wrote : Re: [Bug 114025] Re: Problem with wine preloader: Warning: failed to reserve range 00000000-60000000 | #72 |
MuddBuddha wrote:
> I tried the work around, but still end up with an error:
>
> err:seh:
> eip 7bc3b381 esp 00240fc8 stack 0x240000-
Thats a different error and is unrelated to the previous one.
Erik
--
-------
Erik de Castro Lopo
-------
"You don't have make it your sole purpose in life, but could you at
least sacrifice a rubber chicken upon the altar of literacy?"
-- TackHead on Slashdot
In Wine Bugzilla #12516, Christoph Korn (c-korn) wrote : | #73 |
(In reply to comment #19)
> (In reply to comment #17)
> > Will there be a fix for this in wine?
> The fix is already in Wine since version 0.9.60.
I use version 0.9.61 on Ubuntu 8.04 and still run into the error:
preloader: Warning: failed to reserve range 00000000-00010000
In Wine Bugzilla #12516, Lei Zhang (thestig-google) wrote : | #74 |
*** Bug 12698 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #75 |
(In reply to comment #20)
> I use version 0.9.61 on Ubuntu 8.04 and still run into the error:
> preloader: Warning: failed to reserve range 00000000-00010000
That's not an error, just a warning.
In Wine Bugzilla #12516, James Gregory-Monk (jamgregory) wrote : | #76 |
For a warning, it seems pretty fatal to me when I tried to run Tomb Raider Legend and Tomb Raider Anniversary.
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #77 |
*** Bug 8534 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #78 |
If you can build from source, try building current git;
http://
might help.
In Wine Bugzilla #12516, Alexandre Julliard (julliard) wrote : | #79 |
*** Bug 13041 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #80 |
*** Bug 13043 has been marked as a duplicate of this bug. ***
rja (rajeshjadvani) wrote : | #81 |
I'm using Ubuntu Hardy 64-bit. I tried the work around, and this allows winecfg to work, but the Age of Mythology installer refuses to run.
rajeshja@
rajeshja@
rajeshja@
wine: creating configuration directory '/home/
Could not load Mozilla. HTML rendering will be disabled.
wine: '/home/
rajeshja@
rajeshja@
fixme:font:
fixme:font:
fixme:font:
wine: Unhandled page fault on write access to 0x7bc42f27 at address 0x7e8262c1 (thread 001e), starting debugger...
Unhandled exception: page fault on write access to 0x7bc42f27 in 32-bit code (0x7e8262c1).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:7e8262c1 ESP:0033f210 EBP:0033f238 EFLAGS:00210202( - 00 - -RI1)
EAX:7bc42ed7 EBX:7e82aec8 ECX:0033f244 EDX:00000000
ESI:00132098 EDI:00000000
Stack dump:
0x0033f210: 00020026 00000000 0033f2e0 004214e3
0x0033f220: 00020026 00000000 00000000 7e82629a
0x0033f230: 7ee1770c 00020026 0033f2e0 0042139f
0x0033f240: 00132098 00132098 00449346 00020026
0x0033f250: 00000100 00020026 00000000 0033f2e0
0x0033f260: 7ee1770c 7b88eda6 7ee37520 00000003
Backtrace:
=>1 0x7e8262c1 ImmDestroyConte
2 0x0042139f in ebu6af (+0x2139f) (0x0033f2e0)
3 0x7edf6608 in user32 (+0xa6608) (0x0033f320)
4 0x7edfa6f5 in user32 (+0xaa6f5) (0x0033f7f0)
5 0x7edfb020 in user32 (+0xab020) (0x0033f830)
6 0x7ed81fa7 DefDlgProcW+0x87() in user32 (0x0033f860)
7 0x7edf47ca WINPROC_
8 0x7edf4eae WINPROC_
9 0x7edfb231 in user32 (+0xab231) (0x0033f910)
10 0x7edbd15a in user32 (+0x6d15a) (0x0033f980)
11 0x7edc040d in user32 (+0x7040d) (0x0033f9e0)
12 0x7edc087a SendMessageW+0x4a() in user32 (0x0033fa20)
13 0x7ed8785c in user32 (+0x3785c) (0x0033fbf0)
14 0x7ed88a86 CreateDialogInd
15 0x7ed88bb1 CreateDialogInd
16 0x00448f17 in ebu6af (+0x48f17) (0x00000001)
17 0x00000000 (0x00000000)
0x7e8262c1 ImmDestroyConte
Modules:
Module Address Debug info Name (75 modules)
PE 400000- 504000 Export ebu6af
PE 10000000-10204000 Deferred ebu8dc
ELF 7b800000-7b92c000 Deferred kernel32<elf>
\-PE 7b820000-7b92c000 \ kernel32
ELF 7bc00000-7bca5000 Deferred ntdll<elf>
\-PE 7bc10000-7bca5000 \ ntdll
ELF 7bf00000-7bf03000 Deferred <wine-loader>
ELF 7e3bb000-7e3ed000 Deferred uxtheme<elf>
\-PE 7e3c0000-7e3ed000 \ uxtheme
ELF 7e3ed000-7e401000 Deferred midimap<elf>
\-PE 7e3f0000-7e401000 \ midimap
ELF 7e401000-7e427000 Deferred msacm32<elf>
\-PE 7e410000-7e427000 \ msacm32
ELF 7e427000-7e43e000 Deferr...
In Wine Bugzilla #12516, Vitaliy-bugzilla (vitaliy-bugzilla) wrote : | #82 |
*** Bug 13123 has been marked as a duplicate of this bug. ***
This problem is also unrelated to this bug report. A workaround currently exists at http://
In Wine Bugzilla #12516, Ansus (neptunia) wrote : | #84 |
The workaround does not work in FC9.
In Wine Bugzilla #12516, mback (mback) wrote : | #85 |
$ wine --version
preloader: Warning: failed to reserve range 00000000-60000000
wine-0.9.59
$
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #86 |
(In reply to comment #30)
> $ wine --version
> preloader: Warning: failed to reserve range 00000000-60000000
> wine-0.9.59
Your Wine version is too old, current release is rc1. If you would carefully
read the comments in this bug I'd notice that.
In Wine Bugzilla #12516, Ansus (neptunia) wrote : | #87 |
Where to get Wine newer than 0.9.58 for Fedora Core 9 or newer than 0.9.59 for Ubuntu 7.10?
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #88 |
(In reply to comment #32)
> Where to get Wine newer than 0.9.58 for Fedora Core 9 or newer than 0.9.59 for
> Ubuntu 7.10?
Ask that question on the support list of your distribution.
In Wine Bugzilla #12516, Alexandre Julliard (julliard) wrote : | #89 |
*** Bug 13454 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #90 |
*** Bug 13444 has been marked as a duplicate of this bug. ***
huschy (kannibalenfleisch) wrote : | #91 |
Had the same message. Was gone when I used root: sudo -i
Dan Kegel (dank) wrote : | #92 |
Right, that's expected, but it's bad to run wine apps as root. For one thing, it contaminates your .wine directory with files owned by root, for another, it makes it easier to get infected with rootkits and the like.http://
Mike Mackintosh (mike-mackintosh) wrote : | #93 |
Seems to be same bug.
splug@SplugBox:~$ winecfg
preloader: Warning: failed to reserve range 00000000-60000000
wine: creating configuration directory '/home/
preloader: Warning: failed to reserve range 00000000-60000000
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
Could not load Mozilla. HTML rendering will be disabled.
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
wine: '/home/splug/.wine' created successfully.
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
err:dosmem:
preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #94 |
*** Bug 13668 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Angel Guzman Maeso (shakaran) wrote : | #95 |
In rc1, rc2 and rc3 I have not seen this problem in ubuntu 8.04. I think that this solved.
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #96 |
(In reply to comment #37)
> In rc1, rc2 and rc3 I have not seen this problem in ubuntu 8.04. I think that
> this solved.
>
Fixes have been put in for most apps, but some dos/win16 apps still trigger it.
In Wine Bugzilla #12516, Kevin DeKorte (kdekorte) wrote : | #97 |
The problem now affects wine on Fedora 8. And picasa 2.7.3736-15 triggers the warning message. The work around for mmap_min_addr does work. Just annoying to have wine working correctly and then to have it break.
In Wine Bugzilla #12516, Ansus (neptunia) wrote : | #98 |
Civilization I for Windows hangs on startup.
The game shows splash screen and plays intro music, but does not react on mouse
clicks (normally mouse click should skip intro). After music is over, the game
simply stucks with its splash screen window still displayed.
In console it displays an error message:
wine: Unhandled page fault on read access to 0x0000000c at address 0x605ad6ae
(thread 0019), starting debugger...
Unhandled exception: page fault on read access to 0x0000000c in 32-bit code
(0x605ad6ae).
The game ran well under Wine 1.0-rc1 after the mmap_min_addr workaround (although with some minor bugs) on the same system, so this bug is either because of post-rc1 changes or because of Fedora 9 post-release updates (regression testing did not help, the bug was present in all test attempts). Under Ubuntu 8.04 with Wine 1.0-rc4 also works well.
In Wine Bugzilla #12516, Kristian Rasmussen (krasmussen) wrote : | #99 |
I've applied the vm.mmap_min_addr fix, but after the update my dictionary (Gyldendals Danish-English) now crashes with this - I'm guessing its related to this bug (full log attached):
wine: Unhandled page fault on read access to 0xffffffff at address 0x12cf:0x0000143c (thread 0031), starting debugger...
Unhandled exception: page fault on read access to 0xffffffff in 16-bit code (12cf:143c).
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #100 |
Nah, that looks like a different problem, please create a new bug for it.
Scott Ritchie (scottritchie) wrote : | #101 |
Is there a proper way to configure a system such that ONLY Wine has access to this memory? This would be an ideal default.
Dan Kegel (dank) wrote : | #102 |
Not that I know of.
FWIW, other similar apps are also affected:
qemu: http://
dosemu: http://
So whatever solution you go for, coordinate it with the owners of those other packages.
In Wine Bugzilla #12516, Alexandre Julliard (julliard) wrote : | #103 |
*** Bug 14396 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Brian Walker (bfuzze) wrote : | #104 |
Re: Comment #373 and #38:
I did encounter this error in Ubuntu 8.04 Hardy, running any command thusfar.
Comment #1 seems to resolve:
$ sudo sysctl -w vm.mmap_min_addr=0
To make this setting permanent, add this line to /etc/sysctl.conf:
vm.mmap_min_addr
Dr D J Clark (djc-online) wrote : | #105 |
I have a old 16bit Win program NewSOED that I don't use often. Starting it with the following script prevents the workaround being too permanent but removes some of the inconvenience.
# mmap_min_
# echo $mmap_min_addr
# if [ $mmap_min_addr != '0' ]
# then
# echo "*** 16bit windows program, setting: ***"
# echo " sysctl -w vm.mmap_min_addr=0"
# sudo sysctl -w vm.mmap_min_addr=0
# fi
# wine "c:\PROGRAMS\
In Wine Bugzilla #12516, Scott Ritchie (scottritchie) wrote : | #106 |
Distro packagers should have a new way to workaround this problem if their system is using the newest procps.
You can place your own custom file to override /etc/sysctl.conf settings in /etc/sysctl.d/
So, here we put a small file containing:
vm.mmap_min_addr = 0
The problem, however, is that this exposes a bug in sysctl - namely, it loads the /etc/sysctl.d/ folder BEFORE /etc/sysctl.conf, making the new folder useless. Hopefully this will be fixed soon: https:/
Launchpad Janitor (janitor) wrote : | #107 |
This bug was fixed in the package wine - 1.0.0-1ubuntu8
---------------
wine (1.0.0-1ubuntu8) intrepid; urgency=low
* create debian/
- now Wine can access the lower 64k of memory (LP: #114025)
* debian/rules: add rules for installing wine.sysctl.conf
* debian/wine.dirs.*: add /etc/sysctl.d folder
* debian/
* remove non arch-specific .install and .dirs files.
* debian/
- so no reboot is required for Wine's sysctl.conf setting
-- Scott Ritchie <email address hidden> Thu, 07 Aug 2008 04:28:31 -0700
Changed in wine: | |
status: | Confirmed → Fix Released |
Scott Ritchie (scottritchie) wrote : | #108 |
Unfortunately, the above package doesn't quite fix this in Intrepid, due to this bug in procps: https:/
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #109 |
What's the current status of this bug? Haven't heard much about it lately...
In Wine Bugzilla #12516, JeremiahFlerchinger (flerchjj) wrote : | #110 |
I don't experience this error with every run of Wine (nor have I ever). Still I encountered the "Preloader Page Zero Problem" on some apps. The issue may relate to DOS, Win3.1, or Win98 apps that try to access VGA directly.
I am using Ubuntu 8.04 and running "sudo sysctl -w vm.mmap_min_addr=0" still corrects the issue after any restart.
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #111 |
(In reply to comment #47)
> I don't experience this error with every run of Wine (nor have I ever). Still
> I encountered the "Preloader Page Zero Problem" on some apps. The issue may
> relate to DOS, Win3.1, or Win98 apps that try to access VGA directly.
And Wine can do nothing about this.
> I am using Ubuntu 8.04 and running "sudo sysctl -w vm.mmap_min_addr=0" still
> corrects the issue after any restart.
That's the only way to fix it, in order to avoid doing this after a restart
follow the suggestion in the comments above.
In Wine Bugzilla #12516, JeremiahFlerchinger (flerchjj) wrote : | #112 |
> And Wine can do nothing about this.
I didn't say Wine could or should. I was just replying to Austin that the condition still exists.
It is not a big concern of mine, just a minor annoyance and possibly a concern for individuals unaware of the issue or how to work around it.
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #113 |
This doesn't show up too much anymore, and for the few times it's needed, it's not a Wine bug. Marking invalid.
In Wine Bugzilla #12516, Austin English (austinenglish) wrote : | #114 |
Closing.
In Wine Bugzilla #12516, Scott Ritchie (scottritchie) wrote : | #115 |
Wouldn't Wine, in an ideal world, be able to run these applications even with the memory restrictions? I could be wrong, but I thought Dosbox manages to do it somehow.
In Wine Bugzilla #12516, Vincent Povirk (madewokherd) wrote : | #116 |
(In reply to comment #52)
> Wouldn't Wine, in an ideal world, be able to run these applications even with
> the memory restrictions? I could be wrong, but I thought Dosbox manages to do
> it somehow.
DOSBox does CPU emulation so its own memory layout isn't essential.
Changed in wine: | |
status: | Confirmed → Invalid |
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #117 |
*** Bug 20880 has been marked as a duplicate of this bug. ***
In Wine Bugzilla #12516, Esd45 (esd45) wrote : | #118 |
This technically is a bug in wine, now that wine includes kernel API emulation.
This is actually part of a much larger limitation of not being able to access underlying hardware functions.
Obviously going full emulation would not be an option.
However, the better options would be to utilize a modified variant of Xen to handle the remapping of memory, IO and processor functions to the state and location of a standard win32 system.
Both the APIC and the Virtualization extensions can do this very efficiently, and it's not like we would be remapping standard program memory, or even emulating all the hardware.
No matter what the solution is remapping-based emulation of these functions is the ideal solution.
This would provide a lot of added features for hardware-reliant programs including the ability to secure device access for programs
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #119 |
(In reply to comment #55)
> This technically is a bug in wine, now that wine includes kernel API emulation.
Wine does not include the kernel API emulation, why do you think it does?
In Wine Bugzilla #12516, Esd45 (esd45) wrote : | #120 |
I should clarify that, I should say that now there is implementation of some essential kernel API functions.
Emulating the full kernel API would be a ridiculous waist of time, especially since a huge portion of it is completely hidden from programs. Clearly kernel emulation is far from the way to describe it.
However, come to think of it a full fix for the cause of this bug, as I described, enable doing a bug for bug memory map replication, something that would be classified as an enhancement.
It would allow for more efficient handling of Direct X, and better isolation of platform specific code relating to Host OS kernel memory mapping.
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #121 |
This bug is about running DOS applications which is impossible without
an ability to access page 0. I have no idea why you think this somehow
may improve DirectX or anything else.
In Wine Bugzilla #12516, Esd45 (esd45) wrote : | #122 |
What I meant to say was not this limitation was interfering with Direct X performance, but the larger limitation it is symptomatic of.
Basically Wine's entire memory mapping and memory access capabilities on all modes is entirely limited by the Host OS.
While this is fine for now, it will not be good in the long term, as this limitation puts Wine at the mercy of the host OS when choosing how programs see memory, and what shared memory methods are used.
While this is all fine if the host OS is providing optimal methods for doing things. Wine should create a universal means to direct the OS on how to handle memory remapping for Wine, and a variety of transparent fall-backs for when the Host OS is incapable of doing what is necessary to properly match bug for bug Win32 specifications. Without this, bug for bug matching of the memory mapping of all access modes used by drivers and programs will be literally impossible.
Basically, I'm saying it's better to stomp one big bug, than stomp out all it's children. We have the first small bug here that is symptomatic of a much larger limitation. Making plans to defeat that limitation in the long run, could save us hassles down the road, and greatly improve performance.
As of how this relates to Direct X. The current Direct X drivers are greatly limited by Wine's shared memory access. By improving the memory mapping methods used in all segments of Wine, we can pave the way for improvements in that department. It's basically that some of the limitations on how Direct X is implemented are limited by memory mapping capabilities as well. Just like this bug is caused by those same limitations, even if the limitation is impacting a completely different subsection.
In Wine Bugzilla #12516, Dmitry-codeweavers (dmitry-codeweavers) wrote : | #123 |
It appears to me that you have no idea what you are talking about, just like
you don't know where the message in the summary of this bug is printed and why.
Please stop confusing yourself and others.
In Wine Bugzilla #12516, Dan Kegel (dank) wrote : | #124 |
Agreed... Robert, you seem to be throwing out the baby with the bathwater,
or prematurely optimizing, or something. Please pick some more measurable
problem to work on.
In Wine Bugzilla #12516, Esd45 (esd45) wrote : | #125 |
You are probably right, since we don't know the nature of other limitations we will encounter in memory access.
The first bug one may not represent the nature of future ones, so making a universal preemptive fix for this and all future related issues may not be worth the effort if it doesn't necessarily prevent future bugs, or even lay groundwork for fixing them. Until we see a pattern in Host OS limitation bugs, we won't know what would be effective other than workarounds
Changed in wine: | |
importance: | Unknown → Medium |
Strange,
can you delete your ~/.wine directory first, and try again, just because there is no such crash ... most of time, you have old config stuff in your .wine dir.
Regards,
\sh