From owner-freebsd-current Tue Mar 26 10:25:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA04919 for current-outgoing; Tue, 26 Mar 1996 10:25:12 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA04914 for ; Tue, 26 Mar 1996 10:25:08 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id NAA25541; Tue, 26 Mar 1996 13:25:42 -0500 (EST) Date: Tue, 26 Mar 1996 13:25:33 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org Subject: Like clockwork... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... At 1:15pm, today, 23:47hrs after its last reboot, my -current machine just died. The panic again was ed_start()+0x315 (how does one decode the 0x315 part, btw?) Now, the funny thing about it...current process is cron? current process is what started as the system panick'd, no? if not, what exactly is current process? Normally current process came up as being 'telnetd' or 'ypbind', which would make some sort of sense with this bug. Right now, this "bug" is preventing me from making any use of -current...the machine has no activity on it, no servers running on it, and no users using it. Its just sitting beside me idle. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc