From owner-freebsd-questions Sat Sep 30 17:29:43 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA24199 for questions-outgoing; Sat, 30 Sep 1995 17:29:43 -0700 Received: from vespucci.iquest.com (root@vespucci.iquest.com [199.170.120.42]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA24194 for ; Sat, 30 Sep 1995 17:29:40 -0700 Received: from [204.177.193.231] (n4hhe.ampr.org [204.177.193.231]) by vespucci.iquest.com (8.6.9/8.6.9) with SMTP id TAA16039; Sat, 30 Sep 1995 19:29:32 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 30 Sep 1995 19:29:34 -0500 To: questions@freefall.freebsd.org From: dkelly@iquest.com (David Kelly) Subject: Re: Mysterious reboot...any ideas? Cc: rlenk@widget.xmission.com Sender: owner-questions@FreeBSD.org Precedence: bulk Ron Lenk said: >After doing a build of FreeBSD stable on Sept. 12th, my machine ran >smoothly for 13 days, before it rebooted mysteriously this afternoon, >while I was editing a message in emacs. > >At the bottom of the screen, I got a "Fatal error (1)" message, which >I later discovered came from emacs. Several seconds later ( not more >than 5 ) the familiar messages "...syslogd: exiting on signal 15", >followed by "syncing disks..." and "Rebooting..." were printed on >the console as if I had done a "reboot", or killed init. > >I was the only person logged in at the time, and I am the only one with >root access here, so I'm certain that nobody rebooted the machine on >purpose. It looks to me as if init just died. > >Any ideas would be appreciated. I had the same problem, and also posted it here. Same vintage FreeBSD-stable too. The difference was that I could reproduce the problem every 4 to 12 hours while crunching large numerical codes in 8M core with 64M swap. Eventually recompiled with the kernel debugger so at least the system froze with a death message. Never saw it die with the same task running, or same address, or interupt mask, or nothing. Error was always the same, "Segmentation Violation in Kernel Space" (signal 12?) or some such. Reverting to 2.0.5R seems to have solved my problems. Stange that another similar system had no problems at all, same task, same FreeBSD. I partly suspect the motherboard. -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@iquest.com ============================================================= The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.