On Tuesday 12 August 2003 10:39, D.J. Heap wrote:
> Bernd.Hofner@gmx.net wrote:
> > The bluescreen occured on my notebook, NOT on the repository server!
> > The bluescreen and the repository problem are NOT related, because the
> > bluescreen took place
> > well after the repository crash and in a different configuration (new
> > svn version, new repository location),
> > that is still working after the bluescreen.
> > And this has been the first bluescreen for ages! This seems strange,
> > don't you think?
> > I didn't install new hardware or drivers.
>
> Just because you didn't install anything new doesn't mean it isn't a bad
> driver or failing hardware...maybe Subversion stresses it more than you
> were or it's hardware just starting to fail. Applications cannot
> directly cause bluescreens and TSVN and Subversion are just normal
> applications (that do a ton of disk activity). Of course, a bug in
> Windows or a driver could be hit by Subversion and cause a
> bluescreen...but that is hardly Subversion's problem. Did you take note
> of the module and error code on the bluescreen? Sometimes that is a
> good hint.
DJ is right about this. I develop Windows Device Drivers for a living, and I
can say without hesitation that there are a great many 3rd party device
driver developers who do things wrong. It may work normally under a typical
load, but unless they're stressing it and running it on several different
systems (a dual CPU machine for instance), then it could very well have
problems. Unfortunately, it seems that the only way to guarantee that
they've done this is if the driver has been signed (WHQL approved). Most 3rd
party developers don't do this since it's tough, and time consuming.
There is a great tool to help track down these issues. Windows 2000 has a
utility called 'verifier' that will do some testing to make sure drivers are
adhering to the standard. Just run it from the run box and it will bring up
a wizard to help configure it. I would recommend that you verify all drivers
and that you make sure to enable I/O level 1 checking, and special pool. If
a driver fails to do something properly, it will bluescreen the system. Take
note of the reason and copy down the information about the bugcheck number
and it's parameters. You can look up what they mean on Microsoft's site.
As a side note, we've been using subversion for a year now and haven't had any
problems with the repositories (I believe we have 4 up and running now) on
Windows machines.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 13 00:27:21 2003