From owner-freebsd-bugs@FreeBSD.ORG  Sun Jul 13 00:26:21 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3820A37B401; Sun, 13 Jul 2003 00:26:21 -0700 (PDT)
Received: from defiant.apana.org.au (defiant.apana.org.au [203.11.114.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2D29E43FB1; Sun, 13 Jul 2003 00:26:19 -0700 (PDT)
	(envelope-from dean@odyssey.apana.org.au)
Received: from Mushka.odyssey.apana.org.au (mushka.apana.org.au
	[203.11.114.10])
	by defiant.apana.org.au (8.9.3/8.9.3) with ESMTP id PAA92531;
	Sun, 13 Jul 2003 15:26:16 +0800 (WST)
Message-Id: <5.2.1.1.2.20030713152429.00ae3570@odyssey.apana.org.au>
X-Sender: dean@odyssey.apana.org.au
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sun, 13 Jul 2003 15:25:25 +0800
To: Kris Kennaway <kris@FreeBSD.org>, kris@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
From: Dean Hollister <dean@odyssey.apana.org.au>
In-Reply-To: <200307130710.h6D7A5FU009141@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: i386/43978: Kernel Panics in 4.7-STABLE with 486 CPUs
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2003 07:26:21 -0000
X-List-Received-Date: Sun, 13 Jul 2003 07:26:21 -0000

At 00:10 13/07/2003 -0700, Kris Kennaway wrote:

>This sounds like a bug was temporarily introduced into 4.7-STABLE.
>Chances are it was fixed soon thereafter - does the problem persist
>with 4.8-RELEASE?

This is way old, going back to October. IIRC, the bug was in the ISA 
handling code or thereabouts, which was fixed pretty quickly once 
discovered. This FR is safe to just close now, given its age.

Regards,

d.