Re: [SOLVED] Dangerously looking glitch (4.0-STABLE)

2000-04-06 Thread Maxim Sobolev
Thanks to all who replied - problem has been solved by replacing long-served P100 with newest K6-200. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-06 Thread Maxim Sobolev
Soren Schmidt wrote: > It seems Maxim Sobolev wrote: > > > > I've tried it on my home machine and failed to reproduce also. However it is > > strange, because if it is the CPU/Memory problem, then there should be other signs > > - random applications crashes, spontaneous reboots etc., but machine

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-05 Thread Jon Hamilton
In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote: } Frank Nobis wrote: } } > On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: } > > } > > up clean. I think you have a hardware problem somewhere :( } > } > That is very likely a hardwre problem. I have a nfs server under 3.4-S } >

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-05 Thread Soren Schmidt
It seems Maxim Sobolev wrote: > > I've tried it on my home machine and failed to reproduce also. However it is > strange, because if it is the CPU/Memory problem, then there should be other signs > - random applications crashes, spontaneous reboots etc., but machine is pretty > stable - up and ru

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-05 Thread Maxim Sobolev
Jon Hamilton wrote: > In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote: > } This is a multi-part message in MIME format. > } --3D64CAE46133EFA188180FFD > } Content-Type: text/plain; charset=koi8-r > } Content-Transfer-Encoding: 7bit > } > } Hi, > } > } I've tried to track down why

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-05 Thread Maxim Sobolev
Frank Nobis wrote: > On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: > > > > up clean. I think you have a hardware problem somewhere :( > > That is very likely a hardwre problem. I have a nfs server under 3.4-S > here running, It was easy to crash the system with much I/O over nfs

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-05 Thread Frank Nobis
On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: > > up clean. I think you have a hardware problem somewhere :( That is very likely a hardwre problem. I have a nfs server under 3.4-S here running, It was easy to crash the system with much I/O over nfs on a 100M Ethernet connection.

Re: Dangerously looking glitch (4.0-STABLE)

2000-04-05 Thread Jon Hamilton
In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote: } This is a multi-part message in MIME format. } --3D64CAE46133EFA188180FFD } Content-Type: text/plain; charset=koi8-r } Content-Transfer-Encoding: 7bit } } Hi, } } I've tried to track down why my own script which is cleaning non-

Dangerously looking glitch (4.0-STABLE)

2000-04-04 Thread Maxim Sobolev
Hi, I've tried to track down why my own script which is cleaning non-matching distfiles from time to time produce incorrect results (just cvsup'ed 4.0). After some digging I've found that this bug could be easily reproduced by doing "find -exec md5" on large set of files several times consequient