From owner-freebsd-questions@FreeBSD.ORG  Tue Jun 17 18:43:53 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 27B5437B401
	for <freebsd-questions@freebsd.org>;
	Tue, 17 Jun 2003 18:43:53 -0700 (PDT)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A2EC643F85
	for <freebsd-questions@freebsd.org>;
	Tue, 17 Jun 2003 18:43:52 -0700 (PDT)
	(envelope-from ynshenoy@cs.ucsb.edu)
Received: from bird (bird [128.111.43.203])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id h5I1hq507848
	for <freebsd-questions@freebsd.org>;
	Tue, 17 Jun 2003 18:43:52 -0700 (PDT)
Date: Tue, 17 Jun 2003 18:43:52 -0700 (PDT)
From: Yogeshwar Shenoy <ynshenoy@cs.ucsb.edu>
X-Sender: ynshenoy@bird
To: freebsd-questions@freebsd.org
Message-ID: <Pine.GSO.4.21.0306171831370.1106-100000@bird>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Process crash on signal 4
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2003 01:43:53 -0000

Can someone throw some light on what the different reasons for signal 4 (SIGILL)
being sent to a process are? ('Illegal instruction' does not quite make sense in this case).

We are running a server that uses TCP, on Intel Xeon CPU 2.40GHz (hyperthreading disabled)
running FreeBSD 4.8-RELEASE. This process core dumped on signal 4 when
pushing ~15Mbit/sec over an em (gigabit copper) interface. Using gdb I find that the address in
the EIP register is actually the start of my own function; the stack trace does not show a frame 
for abort() either.  So I am not sure what caused this signal to be sent to the process. 

The exact same binary running on a PIII 1.2GHz (FreeBSD 4.6.2-RELEASE), using
an fxp interface has been running fine (also steadily pushing ~15Mbit/sec) for about 8 months.

The binary was compiled on a PIII machine running FreeBSD 4.4-RELEASE machine using
gcc version 2.95.3 20010315 (release) [FreeBSD], with the -O2 option. 

If this is not the correct mailing list for this question, please direct me to the
correct one. 

Thanks,
Yogeshwar.