xinted rsync bluescreen

[Randall R Schulz]

Dan,

It seems most likely from this that the problem is in your file system. 
When's the last time you ran CHKDSK? I seem to recall other reports that 
were for some reason associated with accessing Cygwin's /etc. I cannot 
explain this other than perhaps as simple coincidence.

I'm not familiar with exactly how much memory protection is in place in 
Windows 98. I'm under the impression that it's more than on Windows 95, 
though it is not really a fully protected environment as exists on Windows 
NT, 2K and XP. That means that it's conceivable that a putative bug in 
Cygwin could trigger a BSOD under 95 or 98 that would knock down only a 
single process under one of the other OS versions.

However, judging from the crash dump you supplied, if Cygwin is at fault, 
it's rather indirect. When memory isn't protected, a symptom can appear far 
separated in time from the actual software defect that caused it.

Still, it is pretty unlikely that this is a Cygwin bug. If the problem were 
in Cygwin, then probably others would have it, too.

Check your disks, maybe update your drivers and try fully de-activating any 
virus checkers or firewalls--they seem to be the worst culprits. Although 
it seems unlikely for the symptoms you're reporting, video drivers seem to 
be a weak spot in Windows and they seem to get updated more than any other 
class of drivers. So much so that I check the Matrox site monthly for 
driver updates.

Good luck.

Randall Schulz


At 10:18 2003-01-13, Dan Holmsand wrote:
>Sergey Okhapkin wrote:
>>net start init
>>chkconfig rsync on
>>chkconfig rsync off
>>bluescreen... Win2000. I have no rsync installed.
>>I set system environment variable CYGWIN to "nontsec", restarted init
>>service and the problem went away...
>
>I've seen this occasionally as well, but it doesn't stop there. Any access 
>of files under /etc seems to be able to occasionally trigger a blue screen 
>while init is running. A particularly sure fire way of causing the BSOD 
>seems to be running /sbin/telinit, but even viewing a file under /etc with 
>vim can sometimes be enough.
>
>The BSOD happens both using 1.3.18 and the latest snapshot, on W2K SP3, 
>with no anti-virus software running. I've seen BSODs on quite different 
>machines (both on a Compaq Proliant and on a couple of Compaq Armadas): 
>the common denominator seems to be that init is running. Init is in turn 
>running sshd, cron, xinetd, ipc-daemon and postgres.
>
>However, it might not be init (directly) that causes the BSOD; the 
>bugcheck analysis (below) seems to be at least somewhat similar to the 
>ones posted in 
><http://www.cygwin.com/ml/cygwin-xfree/2002-03/msg00060.html>, 
><http://sources.redhat.com/ml/cygwin/2001-11.t/msg00167.html> and 
><http://sources.redhat.com/ml/cygwin/2002-11/msg01369.html>
>
>My guess is that cygwin does something that sometimes triggers a windows 
>(or, rather, ntfs) bug when files under /etc are used. This is of course 
>just a wild guess.
>
>Another observation: it seems (according to Process Explorer from 
>sysinternals.com) that cygwin programs started from init keep a handle to 
>the /etc directory open. That shouldn't be needed, should it? I have no 
>idea if this has anything at all to do with the BSODs, of course...
>
>Hopefully this information might be useful to someone more familiar with 
>Cygwin and Windows internals than I am.
>
>/dan


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/