From owner-freebsd-security Mon Mar 3 13:56:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA01027 for security-outgoing; Mon, 3 Mar 1997 13:56:06 -0800 (PST) Received: from postoffice.cso.uiuc.edu (postoffice.cso.uiuc.edu [128.174.5.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA00979 for ; Mon, 3 Mar 1997 13:55:55 -0800 (PST) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [128.174.83.167]) by postoffice.cso.uiuc.edu (8.8.5/8.8.5) with SMTP id PAA86222; Mon, 3 Mar 1997 15:55:12 -0600 Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id PAA04864; Mon, 3 Mar 1997 15:51:06 -0600 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199703032151.PAA04864@alecto.physics.uiuc.edu> Subject: Re: rebooting problems To: jseng@pobox.org.sg (James Seng) Date: Mon, 3 Mar 1997 15:51:06 -0600 (CST) Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <3.0.32.19970303081513.007018bc@student.anu.edu.au> from "James Seng" at Mar 3, 97 08:15:17 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 1. I don't think this is relevant to SECURITY, so, it should not be on this list. Agree ? 2. Even if this were relevant to security, I think, there is no need for everybody (I believe, many people have or had these problems) to post their configuration and moan about it. It does not seem to add too much information after a few have been posted. 3. Recently ( about a month ago or later), there was a thread about this in comp.unix.bsd.freebsd.misc Somebody, I believe, Joerg, mentioned that most of such problems are due to the hardware problems. 4. I myself had a similar problem. (the same symptoms: no records in /var/log/messages, looks like there is enough memory and swap, but I couldn't make world, or compile anything reasonably big..) It's gone after I replaced the memory chips. I believe, there are places more appropriate for this issues, as soon as we found that it is not security-relevant thing. REgards, IgoR > > I am running my 2.1.6-based server and it would reboot itself automatically > every now and then. The server is a Pentium-166, 128Mb RAM, 512Mb swap (and > with AHC2940 too..hmmm). The kernel is compiled to the minimum removing all > unneccessary devices. > > I wrote some script to check on the system status every minute and it is > found that the system is perfectly fine when it reboots. ie, the CPU load > is less than 1, the free RAM is over 30Mb, the swap isnt even used! It just > reboot out of the blue. > > On the other two 2.1.6-base server however (with a similar setup), which is > less heavy on RAM, it doesnt appears to have this problem. Neither does it > appears on my 2.1.5-base server. All three machines has the same hardware > (right down the harddisk and monitor). Even the kernal config file used is > the same.... > > It is driving me crazy *sigh* > > -James Seng > > At 06:22 AM 3/3/97 -0500, Security Administrator wrote: > >A quick question: > > > >Every five to six days or so my 2.1.7-based system reboots. There doesn't > seem to be ANYTHING present in the logs to explain this phenomena. > Everything seems to be stable and then it suddenly reboots. > > > >If this is something that someone else has confronted, I would love to > know how you mended the problems. > > > >My system is a P6-200 with an Adaptec 2940 Ultra SCSI-III controller, 128 > Megs > >of EDO mem, and 256 Megs of swap that has been evenly split between two > >SCSI-III drives. I did have sound support compiled in at one point, but the > >system was totally unstable. > > > >Josh Pincus > >-- > >System Security Administrator > >Computer Interest Floor > >University of Rochester > >Rochester, NY 14627 > >sadmin@roundtable.cif.rochester.edu > > > > >