From owner-freebsd-current@FreeBSD.ORG  Wed Jun 16 20:53:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6D37616A4CE
	for <current@freebsd.org>; Wed, 16 Jun 2004 20:53:55 +0000 (GMT)
Received: from mailout1.informatik.tu-muenchen.de
	(mailout1.informatik.tu-muenchen.de [131.159.0.18])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D87E343D39
	for <current@freebsd.org>; Wed, 16 Jun 2004 20:53:54 +0000 (GMT)
	(envelope-from barner@in.tum.de)
Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000)
	id 2D6143EFC; Wed, 16 Jun 2004 22:52:16 +0200 (CEST)
Date: Wed, 16 Jun 2004 22:52:16 +0200
From: Simon Barner <barner@in.tum.de>
To: Doug White <dwhite@gumbysoft.com>
Message-ID: <20040616205215.GK1140@zi025.glhnet.mhn.de>
References: <20040616105706.GC1140@zi025.glhnet.mhn.de>
	<20040616133211.O16072@carver.gumbysoft.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="um2V5WpqCyd73IVb"
Content-Disposition: inline
In-Reply-To: <20040616133211.O16072@carver.gumbysoft.com>
User-Agent: Mutt/1.5.6i
X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de
cc: current@freebsd.org
Subject: Re: Bogus signal handler causes kernel panic (5.2.1-p8/i386)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jun 2004 20:53:55 -0000


--um2V5WpqCyd73IVb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> > The result is a kernel panic (back trace attached).
>=20
> You attached the backtrace of your program, which (correctly) cored on
> SIGFPE. I see no kernel panic or kernel backtrace.

Sorry for being a bit unclear. Here another attempt to shed some light
on things:

FreeBSD 5.2.1: kernel panic  -- stack trace in FreeBSD5.log
FreeBSD 4.9:   program crash -- back trace in FreeBSD4.log

Both happens on the same machine: AMD K6-III (dmesg attached).

Simon

--um2V5WpqCyd73IVb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFA0LL/Ckn+/eutqCoRAoABAJ9VlywH2esxuDWZwcB5a/udWvuYQwCgmijN
qz2eZ1mjEZ0MMFPh4XyLWXw=
=WO+F
-----END PGP SIGNATURE-----

--um2V5WpqCyd73IVb--