Date: Tue, 28 May 1996 12:07:41 +0200 (MET DST) From: grog@lemis.de (Greg Lehey) To: gurney_j@resnet.uoregon.edu Cc: hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: signal 4? Message-ID: <199605281007.MAA23299@allegro.lemis.de> In-Reply-To: <Pine.BSF.3.91.960527200218.976E-100000@nike.efn.org> from "John-Mark Gurney" at May 27, 96 08:09:57 pm
next in thread | previous in thread | raw e-mail | index | archive | help
John-Mark Gurney writes: > > what exactly is signal 4? >From <sys/signal.h>: #define SIGHUP 1 /* hangup */ #define SIGINT 2 /* interrupt */ #define SIGQUIT 3 /* quit */ #define SIGILL 4 /* illegal instruction (not reset when caught) */ > recently I have been getting this quite often... if it is a normal > command that hits a sig 4 it usally hangs the machine after a few > seconds... could it be a memory timing problem? or possible > something else? > > I'm running a Conner CFP1060S with three cdrom drives on an Adaptec > 2840... also is two 4port AST compatible async cards... the ethernet > card is a ne2000 clone... I'm running 2.2-960323-SNAP on it.... I'm > thinking of upgrading the machine to 2.1-STABLE but I currently don't > have enough disk space to make it... Doesn't ring a bell with me. It would be interesting to see where it hits--is the instruction really illegal? It's not a very common occurrence, so maybe you do have hardware problems. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605281007.MAA23299>