From owner-freebsd-hackers Fri Nov 1 15:20:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28087 for hackers-outgoing; Fri, 1 Nov 1996 15:20:40 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA28071 for ; Fri, 1 Nov 1996 15:20:35 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA28460; Fri, 1 Nov 1996 18:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 1 Nov 1996 18:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id NAA10073; Fri, 1 Nov 1996 13:32:16 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id NAA11813; Fri, 1 Nov 1996 13:33:10 -0500 (EST) Date: Fri, 1 Nov 1996 13:33:10 -0500 (EST) From: Thomas David Rivers Message-Id: <199611011833.NAA11813@lakes.water.net> To: roberto@keltia.freenix.fr, ponds!freefall.freebsd.org!freebsd-hackers Subject: Re: Another data point in the daily panics... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > According to Mikael Karpberg: > > Then again, I know a friends 2.1.5 machine rebooted after running 30 > > seconds of "crashme". Firing up _40_ at boot time, just for kicks, > > I've never run 40 at a time but I've never been able to take any version of > FreeBSD down with crashme. Even 386BSD 0.1 + patchkit was immune ! > > I remember running it on 386BSD for 30 minutes and killing because it was > boring. To be completely honest, Linux is generally immune too (haven't > tried recently though). Yes - that's probably the case here. Consider, for example, that crashme can run on some machines, but you can bring them down quickly with the well-known "ping attack." I'm betting that crashme won't show us anything and FreeBSD will pass this test with flying colors. However, I will still be experiencing my panics. Let me add that I'm not sure my problems are the hardware; as: 1) This problem didn't show up until 2.1. 2) This problem does show up with an aha1542B as well as IDE drive - Dave Rivers -