Re: SOD/Reboot on win32 when doing svn co

[Mark <mw...@gmail.com>]

I agree, but I would also recomend that you check your anti-virus software
itself.  I had almost exactly this problem and by running Driver Verifier, I
was able to narrow it down to a particular driver that when stressed, which
subversion appears to do, it would cause the machine to reboot.

In my case it was Norton Anti-Virus.  I removed all Norton/Symantec software
from my computer and it has been rock solid ever since.

-mark

On 6/27/06, jason@subversus.org <ja...@subversus.org> wrote:
>
>   This sounds very much like an anti-virus problem.  I would recommend
> checking the file out from the server, taking a copy of it to your machine,
> and then checking the file with your anti-virus software.  I suspect that
>  doing this will show the file in question to contain a virus signature
> (whether or not it is actually "infected" is another issue altogether).
>
>
>
> *From:* Alexander Ogol [mailto:alexander@ogol.info]
> *Sent:* Tuesday, June 27, 2006 6:34 PM
> *To:* users@subversion.tigris.org
> *Subject:* SOD/Reboot on win32 when doing svn co
>
>
>
> Hello,
>
>
>
> we have stable NT blue screen on client machine when doing checkout using
> SVN:
>
>
>
> Error code 1000007f, parameter1 00000008, parameter2 f87cfd70, parameter3
> 00000000, parameter4 00000000.
>
>
>
>
>
> Both Server and Client are 1.3.1 on WinXP SP2; tried to access using svn
> and local protocols
>
> I have converted our CVS repository to SubVersion, and now on my machine
> and machine of nearest developer we have SOD when trying to checkout
>
> svn co svn://server/project/trunk
>
> SOD is when process tries to checkout one specific binary file (.doc)
>
> svnadmin restore and svnadmin verify doesn't show anything problematic.
> (and there was no checkins after proceeding with cvs2svn)
>
> If I do checkout from the server (I mean computer where svn server is
> setted up) or from other our servers, there are no problems at all.. (with
> both svn and local protocols)
>
> I have tried to create local repository on problematic machine with files
> in problematic directory (added /doc directory), but all works correctly
> with this new repository
>
>
>
> I fear that problems can be related to antivirus DrWeb Enterprise Agent,
> which is turned on on our computers, but I'm not sure (in fact, some of our
> servers also have it, I need check it)
>
>
>
> Had you anything related? What can we do?
>
>
>



-- 
-mark