This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: fhandler_dev_zero::fixup_mmap_after_fork/fixup_mmap_after_fork fails far too often on yonah


On Fri, Feb 24, 2006 at 12:23:58AM -0800, Nathan Laredo wrote:
>I'm randomly getting win32 errors 487 and 5 on a new intel yonah (core
>duo) system with 1.5.19-4, but not with a banias (original centrino)
>system.  The cygwin images are identical, and 'rebaseall' helped make
>the problem less frequent but it still happens quite often.

Please check out the project web page for links to available information:
http://cygwin.com/ .

If you don't see what you need there, then the cygwin mailing list is
the best place to make observations or get questions answered.
Information on the mailing list is available at the project web page.

For your convenience, I've reset the Reply-To: address to point to the
cygwin mailing list.  I've also Cc'ed this reply there.

>
>Some examples when trying to fork off rsync (happens on bash startup too):
>rsync: fork failed in do_recv: No child processes (10)
>rsync error: error in IPC code (code 14) at
>/home/lapo/packaging/tmp/rsync-2.6.6/main.c(552)
>      7 [main] rsync 1512 fhandler_dev_zero::fixup_mmap_after_fork:
>requested 0x4D0000 != 0x0 mem alloc base 0x450000, state 0x2000, size
>516096, Win32 error 487
>    203 [main] rsync 1512 C:\cygwin\bin\rsync.exe: *** fatal error -
>recreate_mmaps_after_fork_failed
>     12 [main] rsync 2308 child_copy: stack write copy failed,
>0x22DC80..0x230000, done 0, windows pid 2284468, Win32 error 5
>rsync: connection unexpectedly closed (8 bytes read so far)
>
>another rsync example:
>Enter passphrase for key '/home/nlaredo/.ssh/id_dsa':
>Received disconnect from 127.0.0.1: fork failed: No error
>rsync: connection unexpectedly closed (0 bytes read so far)
>
>still another rsync example:
>60 files to consider
>rsync: fork failed in do_recv: No child processes (10)
>rsync error: error in IPC code (code 14) at
>/home/lapo/packaging/tmp/rsync-2.6.6/main.c(552)
>      8 [main] ? (7264) C:\cygwin\bin\rsync.exe: *** fatal error -
>couldn't allocate heap, Win32 error 487, base 0x4A0000, top 0x4D0000,
>reserve_size 192512, allocsize 196608, page_const 4096
>     10 [main] rsync 7168 child_copy: stack write copy failed,
>0x22DC80..0x230000, done 0, windows pid 2284468, Win32 error 5
>rsync: connection unexpectedly closed (8 bytes read so far)
>rsync error: error in rsync protocol data stream (code 12) at io.c(165)
>
>I've just gotten the 1.5.19-4 source and started looking through for
>anything obvious, but the more I read the more I wish I had time to
>rewrite a lot of stuff.
>
>I'm guessing by your changelog and mail list comments that you're
>already on the problem, but I just wanted to point out that the new
>dual core processor makes the "rare" cases very very very common.
>
>-- Nathan Laredo
>laredo@gnu.org


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]