The bug completely gone after I revert machdep.c to 1.538. This commit cause bug:
-------------------------------------------------------------------- revision 1.539 date: 2002/09/30 07:02:22; author: obrien; state: Exp; lines: +10 -0 Save the FP state in the PCB as that is compatable with releng4 binaries. This is a band-aid until the KSE pthread committers get back on the ground and have their machines setup. Submitted by: eischen -------------------------------------------------------------------- Please back it out or do it properly! Additional details: it cause not only cvsupd death, but rarely cvsup signal 6 death too with this diagnostic: *** *** runtime error: *** Value out of range *** file "/tmp/a/ports/lang/ezm3/work/ezm3-1.0/libs/libm3/src/uid/Common/Time Stamp.m3", line 63 *** On Tue, Oct 01, 2002 at 19:25:43 +0400, Andrey A. Chernov wrote: > Now I constantly got cvsupd death on very recent -current. Either TCPIP or > thread changes involved, all works two days ago. Does anybody else saw > this too? > > cvsup & cvsupd on the same machine talking to each other: > > messages says: > kernel: pid 15533 (cvsupd), uid 2068: exited on signal 6 (core dumped) > > cvsup.log says: > TreeList failed: Network write failure: Connection closed -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
