From owner-freebsd-stable Sun Jul 23 10:38: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fnal.gov (heffalump.fnal.gov [131.225.9.20]) by hub.freebsd.org (Postfix) with ESMTP id 8E22737BCA0 for ; Sun, 23 Jul 2000 10:38:01 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from nova.fnal.gov ([131.225.18.207]) by smtp.fnal.gov (PMDF V6.0-24 #44770) with ESMTP id <0FY50079IVNCTH@smtp.fnal.gov> for freebsd-stable@FreeBSD.ORG; Sun, 23 Jul 2000 12:38:00 -0500 (CDT) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.1) with ESMTP id MAA28020; Sun, 23 Jul 2000 12:37:59 -0500 (CDT) Date: Sun, 23 Jul 2000 12:37:59 -0500 (CDT) From: Tim Zingelman Subject: Re: 4.1-RC panic when loading dnetc (distributed.net client) In-reply-to: <004c01bff4c6$1786dec0$0100a8c0@cascade> X-Sender: tez@nova.fnal.gov To: "Thomas T. Veldhouse" Cc: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Authentication-warning: nova.fnal.gov: tez owned process doing -bs Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jul 2000, Thomas T. Veldhouse wrote: > I am using the 4.63 dnetc native FreeBSD version of the distributed.net > client. Here is what happens: > ... > panic: page fault More details are needed when you can... I am running the same client (installed from ports) with no problem on 4.1-RC 7/23/2000 and can't duplicate the problem. Cut from dmesg: Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D+ Processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 127238144 (124256K bytes) Cut from dnetc logfile: dnetc v2.8010-463-CTR-00071200 for FreeBSD (FreeBSD 4.1-RC). Cut from dnetc.ini: [display] detached=yes progress-indicator=off [logging] log-file-limit=2MB log-file=/tmp/dnetc.log log-file-type=fifo - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message