Re: xinted rsync bluescreen

Re: xinted rsync bluescreen

[Bruce Dobrin]

hmmm,  that didn't seem to help,  but things I did notice:

if I "net stop init"
/usr/sbin/chkconfig rsync on
net start init

and I add:
rsync     873/tcp
in services file,  everything works just fine.

I seem to be able to chkconfig on/off all but rsync while init is running.
I've tryed this now on 6 machines (NT, 2K, XP) of all different configs and
it bluescreens on all.

----- Original Message -----
From: "Sergey Okhapkin" <sos@sokhapkin.dyndns.org>
To: "'Bruce Dobrin'" <dobrin@imageworks.com>; <cygwin@cygwin.com>
Sent: Thursday, January 09, 2003 12:23 PM
Subject: RE: xinted rsync bluescreen


> Try "chmod a+w /etc/xinetd.d"
>
> > -----Original Message-----
> > From: cygwin-owner@cygwin.com
> > [mailto:cygwin-owner@cygwin.com] On Behalf Of Bruce Dobrin
> > Sent: Thursday, January 09, 2003 2:42 PM
> > To: cygwin@cygwin.com
> > Subject: xinted rsync bluescreen
> >
> >
> > I'm setting up rsyncd on a 1.3.18 win2000 and an XP box
> >
> > I've setup xinetd and init etc,  when I "chkconfig rsync on"
> > I get an immediate bluescreen.  is this a known issue? (and
> > is there a known fix?). didn't see anything in the mailing
> > list on rsync and bluescreen or crash or xinet pertaining to
> > this problem.
> >
> > Thanks
> > Bruce
> > dobrin@imageworks.com
> >
> >
> > --
> > 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/
> >
>
>
>
> --
> 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/
>

RE: xinted rsync bluescreen

[Sergey Okhapkin]

Try "chmod a+w /etc/xinetd.d"

> -----Original Message-----
> From: cygwin-owner@cygwin.com
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Bruce Dobrin
> Sent: Thursday, January 09, 2003 2:42 PM
> To: cygwin@cygwin.com
> Subject: xinted rsync bluescreen
>
>
> I'm setting up rsyncd on a 1.3.18 win2000 and an XP box
>
> I've setup xinetd and init etc,  when I "chkconfig rsync on"
> I get an immediate bluescreen.  is this a known issue? (and
> is there a known fix?). didn't see anything in the mailing
> list on rsync and bluescreen or crash or xinet pertaining to
> this problem.
>
> Thanks
> Bruce
> dobrin@imageworks.com
>
>
> --
> 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/
>

Re: xinted rsync bluescreen

[Rui Carmo]

Erm... I can't help with the blue screens, but if you can mount the 
filesystems you want to sync, there is an alternative called "ssync" 
(Google or Freshmeat for it) that runs OK in cygwin (I recall patching 
a utime() check or something similar, but it's a fairly straightforward 
matter).

Best of luck,

R.

On Friday, Jan 10, 2003, at 00:46 Europe/Lisbon, Bruce Dobrin wrote:

> hmmm,  that didn't seem to help,  but things I did notice:
>
> if I "net stop init"
> /usr/sbin/chkconfig rsync on
> net start init
>
> and I add:
> rsync     873/tcp
> in services file,  everything works just fine.
>
> I seem to be able to chkconfig on/off all but rsync while init is 
> running.
> I've tryed this now on 6 machines (NT, 2K, XP) of all different 
> configs and
> it bluescreens on all.
>
> ----- Original Message -----
> From: "Sergey Okhapkin" <sos@sokhapkin.dyndns.org>
> To: "'Bruce Dobrin'" <dobrin@imageworks.com>; <cygwin@cygwin.com>
> Sent: Thursday, January 09, 2003 12:23 PM
> Subject: RE: xinted rsync bluescreen
>
>
>> Try "chmod a+w /etc/xinetd.d"
>>
>>> -----Original Message-----
>>> From: cygwin-owner@cygwin.com
>>> [mailto:cygwin-owner@cygwin.com] On Behalf Of Bruce Dobrin
>>> Sent: Thursday, January 09, 2003 2:42 PM
>>> To: cygwin@cygwin.com
>>> Subject: xinted rsync bluescreen
>>>
>>>
>>> I'm setting up rsyncd on a 1.3.18 win2000 and an XP box
>>>
>>> I've setup xinetd and init etc,  when I "chkconfig rsync on"
>>> I get an immediate bluescreen.  is this a known issue? (and
>>> is there a known fix?). didn't see anything in the mailing
>>> list on rsync and bluescreen or crash or xinet pertaining to
>>> this problem.
>>>
>>> Thanks
>>> Bruce
>>> dobrin@imageworks.com
>>>
>>>
>>> --
>>> 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/
>>>
>>
>>
>>
>> --
>> 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/
>>
>
>
> --
> 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/

Re: xinted rsync bluescreen

[Sergey Okhapkin]

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...

Sergey Okhapkin
Somerset, NJ
----- Original Message -----
From: "Bruce Dobrin" <dobrin@imageworks.com>
To: "Sergey Okhapkin" <sos@sokhapkin.dyndns.org>; <cygwin@cygwin.com>
Sent: Thursday, January 09, 2003 7:46 PM
Subject: Re: xinted rsync bluescreen


> hmmm,  that didn't seem to help,  but things I did notice:
>
> if I "net stop init"
> /usr/sbin/chkconfig rsync on
> net start init
>
> and I add:
> rsync     873/tcp
> in services file,  everything works just fine.
>
> I seem to be able to chkconfig on/off all but rsync while init is running.
> I've tryed this now on 6 machines (NT, 2K, XP) of all different configs
and
> it bluescreens on all.
>
> ----- Original Message -----
> From: "Sergey Okhapkin" <sos@sokhapkin.dyndns.org>
> To: "'Bruce Dobrin'" <dobrin@imageworks.com>; <cygwin@cygwin.com>
> Sent: Thursday, January 09, 2003 12:23 PM
> Subject: RE: xinted rsync bluescreen
>
>
> > Try "chmod a+w /etc/xinetd.d"
> >
> > > -----Original Message-----
> > > From: cygwin-owner@cygwin.com
> > > [mailto:cygwin-owner@cygwin.com] On Behalf Of Bruce Dobrin
> > > Sent: Thursday, January 09, 2003 2:42 PM
> > > To: cygwin@cygwin.com
> > > Subject: xinted rsync bluescreen
> > >
> > >
> > > I'm setting up rsyncd on a 1.3.18 win2000 and an XP box
> > >
> > > I've setup xinetd and init etc,  when I "chkconfig rsync on"
> > > I get an immediate bluescreen.  is this a known issue? (and
> > > is there a known fix?). didn't see anything in the mailing
> > > list on rsync and bluescreen or crash or xinet pertaining to
> > > this problem.
> > >
> > > Thanks
> > > Bruce
> > > dobrin@imageworks.com
> > >
> > >
> > > --
> > > 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/
> > >
> >
> >
> >
> > --
> > 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/
> >
>
>
> --
> 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/
>

xinted rsync bluescreen

[Bruce Dobrin]

I'm setting up rsyncd on a 1.3.18 win2000 and an XP box

I've setup xinetd and init etc,  when I "chkconfig rsync on" I get an
immediate bluescreen.  is this a known issue? (and is there a known fix?).
didn't see anything in the mailing list on rsync and bluescreen or crash or
xinet pertaining to this problem.

Thanks
Bruce
dobrin@imageworks.com

Re: xinted rsync bluescreen

[Dan Holmsand]

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




Here is a typical bugcheck analysis from windbg:


IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pagable (or completely invalid) address 
at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8045505d, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  00000014 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP:
nt!PsChargePoolQuota+50
8045505d 0374bb10         add     esi,[ebx+edi*4+0x10]

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

TRAP_FRAME:  bddd6710 -- (.trap ffffffffbddd6710)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000020 
edi=00000001
eip=8045505d esp=bddd6784 ebp=bddd6798 iopl=0         nv up ei pl zr na 
po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000 
efl=00010246
nt!PsChargePoolQuota+50:
8045505d 0374bb10         add  esi,[ebx+edi*4+0x10] 
ds:0023:00000014=????????
Resetting default context

LAST_CONTROL_TRANSFER:  from 80495801 to 8045505d

STACK_TEXT:
bddd6798 80495801 ff974b40 00000001 00000020 nt!PsChargePoolQuota+0x50
bddd683c bfeed999 81a73368 81a49bc8 e27e2b98 
nt!FsRtlNotifyFullReportChange+0x46d
bddd6ab8 bfeeaa06 bddd6b00 ff93c508 81a49800 Ntfs!NtfsCommonCleanup+0x2061
bddd6c30 8041f79f 81a49800 ff93c508 ff93e108 Ntfs!NtfsFsdCleanup+0x113
bddd6c44 8049bb90 80067c64 81aa9040 00000001 nt!IopfCallDriver+0x35
bddd6c78 804a50e5 ff93e1c0 81a49800 00120196 nt!IopCloseFile+0x275
bddd6ca4 8044f718 ff93e1c0 ff93e0f4 ff93e108 
nt!ObpDecrementHandleCount+0x13c
bddd6d58 80465091 000000bc 00000000 00000000 nt!NtClose+0x1f0
bddd6d58 77f8376e 000000bc 00000000 00000000 nt!KiSystemService+0xc4
WARNING: Frame IP not in any known module. Following frames may be wrong.
0022fc0c 00000000 00000000 00000000 00000000 0x77f8376e


FOLLOWUP_IP:
nt!PsChargePoolQuota+50
8045505d 0374bb10         add     esi,[ebx+edi*4+0x10]

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!PsChargePoolQuota+50

MODULE_NAME:  nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  3d366b8b

STACK_COMMAND:  .trap ffffffffbddd6710 ; kb

BUCKET_ID:  0xA_nt!PsChargePoolQuota+50



--
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/

Re: 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/

Re: xinted rsync bluescreen

[Pierre A. Humblet]

On Mon, Jan 13, 2003 at 10:39:31AM -0800, Randall R Schulz wrote:
> 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.

Cygwin processes keep a handle to /etc, opened with 
FindFirstChangeNotification and then duplicated.

Pierre

--
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/

Re: xinted rsync bluescreen

[Randall R Schulz]

Pierre,

Do you think the handle to /etc that each (is it each or all?) cygwin 
process retains is an ingredient in triggering this symptom? Why would that 
be and why would it happen to but a few of the many Cygwin users?

Randall Schulz


At 10:33 2003-01-13, Pierre A. Humblet wrote:
>On Mon, Jan 13, 2003 at 10:39:31AM -0800, Randall R Schulz wrote:
> > 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.
>
>Cygwin processes keep a handle to /etc, opened with
>FindFirstChangeNotification and then duplicated.
>
>Pierre


--
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/

Re: xinted rsync bluescreen

[Dan Holmsand]

Randall,

Randall R Schulz wrote:
> 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.

Chkdsk was the first thing I tried (both on the Proliant and on the 
Armadas). No difference, I'm afraid.

> 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.

I'm running Win2k.

> 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.

I'm not saying it is a bug in Cygwin! It just seems quite likely to me 
that Cygwin is trigging a bug in Windows when sysvinit is running (since 
Cygwin always is involved when the bsod happens - and I haven't had any 
crashes otherwise). This is of course guesswork on my part.

> 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.

I have never had any anti-virus software installed on any of the 
machines bsoding. I've updated all the machines involved (including 
drivers), even if it seems unlikely that the drivers are at fault (since 
the proliant and armada use completely different sets of drivers).

> Good luck.

Thanks!

/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/

Re: xinted rsync bluescreen

[Pierre A. Humblet]

On Mon, Jan 13, 2003 at 10:59:16AM -0800, Randall R Schulz wrote:
> Pierre,
> 
> Do you think the handle to /etc that each (is it each or all?) cygwin 
> process retains is an ingredient in triggering this symptom? 

AFAICT the handle is opened when starting cygwin and is inherited by
child processes. It is used in a WaitForSingleObject call.
The purpose is to rescan /etc/{passwd,goup} after changes.
It's unlikely to be a coincidence, given the previous e-mails!

> Why would that 
> be and why would it happen to but a few of the many Cygwin users?

Good questions! Perhaps init has more subprocesses (wild guess).

Pierre

--
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/

Re: xinted rsync bluescreen

[Dan Holmsand]

Pierre,

Pierre A. Humblet wrote:
> AFAICT the handle is opened when starting cygwin and is inherited by
> child processes. It is used in a WaitForSingleObject call.
> The purpose is to rescan /etc/{passwd,goup} after changes.
> It's unlikely to be a coincidence, given the previous e-mails!

That's extremely interresting.

> Good questions! Perhaps init has more subprocesses (wild guess).

Even wilder guess: init starts a lot of processes whose parent process 
terminate while their children keep running. Perhaps the combination of 
this, the inherited handle and, possibly, user context switching becomes 
to much for poor old windows?

/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/

Re: xinted rsync bluescreen

[Randall R Schulz]

Dan,

Sorry. I'm obviously confused. (Did a Windows 98 user report a similar 
problem recently?)

But surely in a fully protected OS such as 2K, a user-level DLL such as 
Cygwin cannot either directly or indirectly cause a blue-screen. Well, I 
suppose "cause" is open to interpretation, especially in conjunction with 
"indirectly," but without a doubt, Cygwin cannot be _blamed_ for a BSOD, right?


Anyway, here's a possible clue: The "Windows 2000 Pro Resource Kit" (book), 
on page 1539-1540, mentions both "buggy device driver" and "[buggy] system 
service" as potential culprits in an IRQL_NOT_LESS_OR_EQUAL BSOD. I'm not 
sure how a service could do this, but perhaps it suggests a way to proceed 
in diagnosing the problem.

The virtual address of the code generating the fault, 8045505d, is, 
according to "Inside Microsoft Windows 2000" 3rd. ed., in the range of 
addresses reserved to "Kernel and executive; HAL and Boot drivers."

Frankly, I'm out of my depth already.

Randall Schulz


At 10:59 2003-01-13, Dan Holmsand wrote:
>Randall,
>
>Randall R Schulz wrote:
>>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.
>
>Chkdsk was the first thing I tried (both on the Proliant and on the 
>Armadas). No difference, I'm afraid.
>
>>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.
>
>I'm running Win2k.
>
>>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.
>
>I'm not saying it is a bug in Cygwin! It just seems quite likely to me 
>that Cygwin is trigging a bug in Windows when sysvinit is running (since 
>Cygwin always is involved when the bsod happens - and I haven't had any 
>crashes otherwise). This is of course guesswork on my part.
>
>>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.
>
>I have never had any anti-virus software installed on any of the machines 
>bsoding. I've updated all the machines involved (including drivers), even 
>if it seems unlikely that the drivers are at fault (since the proliant and 
>armada use completely different sets of drivers).
>
>>Good luck.
>
>Thanks!
>
>/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/

Re: xinted rsync bluescreen

[Bruce Dobrin]

Don't know if this will help,  but I went through 3 machines running init
and rsync (nt, 2000 and XP)  and all of them , at one time or another, I
could trigger the blue screen by something as innocuous as :  ( with rsync
on) Stop init, rm /etc/rc.d/rsync, exit shell,  BSOD.  I think it odd that I
had this issue even when init was no longer running,  and not until I exited
the shell.  It didn't always happen ( I think it may be related to if rsync
had been called at anytime...) but it was nasty enough that in some cases I
couldn't even touch the etc/rc.d/rsync file with vim without eventually
crashing.  I'm over my head on this one...

----- Original Message -----
From: "Pierre A. Humblet" <pierre.humblet@ieee.org>
To: <cygwin@cygwin.com>
Sent: Monday, January 13, 2003 10:58 AM
Subject: Re: xinted rsync bluescreen


> On Mon, Jan 13, 2003 at 10:59:16AM -0800, Randall R Schulz wrote:
> > Pierre,
> >
> > Do you think the handle to /etc that each (is it each or all?) cygwin
> > process retains is an ingredient in triggering this symptom?
>
> AFAICT the handle is opened when starting cygwin and is inherited by
> child processes. It is used in a WaitForSingleObject call.
> The purpose is to rescan /etc/{passwd,goup} after changes.
> It's unlikely to be a coincidence, given the previous e-mails!
>
> > Why would that
> > be and why would it happen to but a few of the many Cygwin users?
>
> Good questions! Perhaps init has more subprocesses (wild guess).
>
> Pierre
>
> --
> 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/
>


--
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/

Re: xinted rsync bluescreen

[Bruce Dobrin]

Oh,  and all of the 3 test boxes were completely different hardware (nt on a
Boxx tech machine, 2k on an IBM workstation,  and XP on a dell laptop).
----- Original Message -----
From: "Bruce Dobrin" <dobrin@imageworks.com>
To: "Pierre A. Humblet" <pierre.humblet@ieee.org>; <cygwin@cygwin.com>
Sent: Monday, January 13, 2003 11:28 AM
Subject: Re: xinted rsync bluescreen


> Don't know if this will help,  but I went through 3 machines running init
> and rsync (nt, 2000 and XP)  and all of them , at one time or another, I
> could trigger the blue screen by something as innocuous as :  ( with rsync
> on) Stop init, rm /etc/rc.d/rsync, exit shell,  BSOD.  I think it odd that
I
> had this issue even when init was no longer running,  and not until I
exited
> the shell.  It didn't always happen ( I think it may be related to if
rsync
> had been called at anytime...) but it was nasty enough that in some cases
I
> couldn't even touch the etc/rc.d/rsync file with vim without eventually
> crashing.  I'm over my head on this one...
>
> ----- Original Message -----
> From: "Pierre A. Humblet" <pierre.humblet@ieee.org>
> To: <cygwin@cygwin.com>
> Sent: Monday, January 13, 2003 10:58 AM
> Subject: Re: xinted rsync bluescreen
>
>
> > On Mon, Jan 13, 2003 at 10:59:16AM -0800, Randall R Schulz wrote:
> > > Pierre,
> > >
> > > Do you think the handle to /etc that each (is it each or all?) cygwin
> > > process retains is an ingredient in triggering this symptom?
> >
> > AFAICT the handle is opened when starting cygwin and is inherited by
> > child processes. It is used in a WaitForSingleObject call.
> > The purpose is to rescan /etc/{passwd,goup} after changes.
> > It's unlikely to be a coincidence, given the previous e-mails!
> >
> > > Why would that
> > > be and why would it happen to but a few of the many Cygwin users?
> >
> > Good questions! Perhaps init has more subprocesses (wild guess).
> >
> > Pierre
> >
> > --
> > 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/
> >
>
>
> --
> 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/
>


--
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/

Re: xinted rsync bluescreen

[Dan Holmsand]

Pierre A. Humblet wrote:
> AFAICT the handle is opened when starting cygwin and is inherited by
> child processes. It is used in a WaitForSingleObject call.
> The purpose is to rescan /etc/{passwd,goup} after changes.
> It's unlikely to be a coincidence, given the previous e-mails!

That seems to be it!  [touching wood]

I added a "return 0" at the top of init_cygheap::etc_changed() (so that 
the whole FindFirstChangeNotification/DuplicateHandle business never 
happens). So far, no crashes - despite my best efforts running chkconfig 
rsync on/off, /sbin/telinit 3/1.

Thanks for the hint!

/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/

Re: xinted rsync bluescreen

[Dan Holmsand]

Update:

I have now tested my hacked cygwin1.dll (without the 
FindFirstChangeNotification of "/etc" stuff) quite extensively, on three 
different machines that previously experienced quite frequent BSODs when 
init was running.

No BSODs so far!

Thus, it seems quite obvious to me that the code in 
init_cygheap::etc_changed is to "blame"; it must trigger some obscure 
windows bug that sometimes causes a bsod when files under /etc are accessed.

/dan



Dan Holmsand wrote:
> That seems to be it!  [touching wood]
> 
> I added a "return 0" at the top of init_cygheap::etc_changed() (so that 
> the whole FindFirstChangeNotification/DuplicateHandle business never 
> happens). So far, no crashes - despite my best efforts running chkconfig 
> rsync on/off, /sbin/telinit 3/1.
> 
> Thanks for the hint!
> 
> /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/

Re: xinted rsync bluescreen

[Danilo Turina]

Yes!!!!! Finally someone found the problem with writing in /etc and BSOD!!!!
Thank you very much!

Dan Holmsand wrote:
> Update:
> 
> I have now tested my hacked cygwin1.dll (without the 
> FindFirstChangeNotification of "/etc" stuff) quite extensively, on three 
> different machines that previously experienced quite frequent BSODs when 
> init was running.
> 
> No BSODs so far!
> 
> Thus, it seems quite obvious to me that the code in 
> init_cygheap::etc_changed is to "blame"; it must trigger some obscure 
> windows bug that sometimes causes a bsod when files under /etc are 
> accessed.
> 
> /dan
> 
> 
> 
> Dan Holmsand wrote:
> 
>> That seems to be it!  [touching wood]
>>
>> I added a "return 0" at the top of init_cygheap::etc_changed() (so 
>> that the whole FindFirstChangeNotification/DuplicateHandle business 
>> never happens). So far, no crashes - despite my best efforts running 
>> chkconfig rsync on/off, /sbin/telinit 3/1.
>>
>> Thanks for the hint!
>>
>> /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/

Re: xinted rsync bluescreen

[Danilo Turina]

I also have a very similar problem (writing in /etc when X is running, 
always cause a BSOD, regardless of antivirus packages), if I can have 
that hacked cygwin1.dll I can try it on my systems and tell if it's the 
same problem.

Ciao,

		Danilo Turina

Dan Holmsand wrote:
> Update:
> 
> I have now tested my hacked cygwin1.dll (without the 
> FindFirstChangeNotification of "/etc" stuff) quite extensively, on three 
> different machines that previously experienced quite frequent BSODs when 
> init was running.
> 
> No BSODs so far!
> 
> Thus, it seems quite obvious to me that the code in 
> init_cygheap::etc_changed is to "blame"; it must trigger some obscure 
> windows bug that sometimes causes a bsod when files under /etc are 
> accessed.
> 
> /dan
> 
> 
> 
> Dan Holmsand wrote:
> 
>> That seems to be it!  [touching wood]
>>
>> I added a "return 0" at the top of init_cygheap::etc_changed() (so 
>> that the whole FindFirstChangeNotification/DuplicateHandle business 
>> never happens). So far, no crashes - despite my best efforts running 
>> chkconfig rsync on/off, /sbin/telinit 3/1.
>>
>> Thanks for the hint!
>>
>> /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/

Re: xinted rsync bluescreen

[Dan Holmsand]

Danilo,

Danilo Turina wrote:
> I also have a very similar problem (writing in /etc when X is running, 
> always cause a BSOD, regardless of antivirus packages), if I can have 
> that hacked cygwin1.dll I can try it on my systems and tell if it's the 
> same problem.

Sure. I'll send you one in private mail.

/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/

Re: xinted rsync bluescreen

[Danilo Turina]

Dan Holmsand wrote:
> Danilo,
> 
> Danilo Turina wrote:
> 
>> I also have a very similar problem (writing in /etc when X is running, 
>> always cause a BSOD, regardless of antivirus packages), if I can have 
>> that hacked cygwin1.dll I can try it on my systems and tell if it's 
>> the same problem.
> 
> 
> Sure. I'll send you one in private mail.
> 
> /dan

Thank you. I tried the patched cygwin1.dll and BSOD not occurred (even 
with McAfee enabled).

After replacing the original cygwin1.dll BSOD not occurred anymore.
But note that this happened to me also in the past, i.e. in some cases 
(e.g. entirely disabling antivirus or with other tries) I was able to 
avoid BSOD.

When this happened to me, restoring the original conditions did not 
immediately cause BSOD to reappear immediately, but only after a while.

Unfortunately I'm unable to understand what made the BSOD reappear (or 
what delayed it). I only had the sensation that once avoided the BSOD 
the first time, the system does not BSOD anymore even if the previous 
situation is restored (I think until a reboot). It is somewhat like the 
first time an handle must be requested or some resource must be 
allocated if this succeeds, the next time the system does not need 
anymore to perform that operation.

Ciao,

			Danilo



--
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/

RE: xinted rsync bluescreen

[lhall]

There have been issues with rsync in the past, though I don't recall
reported bluescreen issues.  Still, bluescreening is a problem with the
underlying O/S and/or drivers, not an application specific issue really 
(although sometimes applications can work around O/S problems of this
type).  
I'd suggest reviewing the email archives for rsync problems/solutions in 
general and making sure your O/S is up-to-date with all service packs and 
reasonable patches.  Ditto for your system's peripheral drivers.  A review 
of the MS knowledge base for bluescreen issues is probably also in order.  
If none of that turns up anything interesting, perhaps the output of strace 
may prove useful in the direction of trying to find a way to work around
the O/S issue, unless you're inclined to build and run a full debug version 
of these apps and Cygwin.

Larry

Original Message:
-----------------
From: Bruce Dobrin dobrin@imageworks.com
Date: Thu, 9 Jan 2003 11:42:20 -0800
To: cygwin@cygwin.com
Subject: xinted rsync bluescreen


I'm setting up rsyncd on a 1.3.18 win2000 and an XP box

I've setup xinetd and init etc,  when I "chkconfig rsync on" I get an
immediate bluescreen.  is this a known issue? (and is there a known fix?).
didn't see anything in the mailing list on rsync and bluescreen or crash or
xinet pertaining to this problem.

Thanks
Bruce
dobrin@imageworks.com


--
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/


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .