From owner-freebsd-current@FreeBSD.ORG  Thu Nov 13 07:51:23 2003
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 EECEB16A4CE; Thu, 13 Nov 2003 07:51:23 -0800 (PST)
Received: from ftp.bjpu.edu.cn (ftp.bjpu.edu.cn [202.112.78.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CCD8B43FBF; Thu, 13 Nov 2003 07:51:22 -0800 (PST)
	(envelope-from delphij@frontfree.net)
Received: by ftp.bjpu.edu.cn (Postfix, from userid 426)
	id E7A2752D3; Thu, 13 Nov 2003 23:13:25 +0800 (CST)
Received: from srv (unknown [202.112.73.151])
	by ftp.bjpu.edu.cn (Postfix) with ESMTP
	id 8A2275299; Thu, 13 Nov 2003 23:13:25 +0800 (CST)
From: "=?gb2312?B?WGluIExJL8Du9s4=?=" <delphij@frontfree.net>
To: "'John Baldwin'" <jhb@FreeBSD.org>,
	"=?gb2312?B?J1hpbiBMSS/A7vbOJw==?=" <delphij@frontfree.net>
Date: Thu, 13 Nov 2003 23:13:25 +0800
Organization: Frontfree Technology Network
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <XFMail.20031112112910.jhb@FreeBSD.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Thread-Index: AcOpOi6CGzJL/ERhRke7HB7fsZnIoAAvhv+A
Message-Id: <20031113151325.8A2275299@ftp.bjpu.edu.cn>
cc: current@freebsd.org
Subject: RE: Recent -CURRENT panic (New interrupt code related?);
	backtrace included
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: Thu, 13 Nov 2003 15:51:24 -0000

Yes I have device apic enabled, and after setting options NO_MIXED_MODE, =
the
problem persists. However, fortunatelly, the spurious.patch seemed to =
solved
the problem, and the system has been up for 9 hours without panic'ing as =
I
described before.

Do you need me to test atpic.patch as well?=20

-----Original Message-----
From: John Baldwin [mailto:jhb@FreeBSD.org]=20
Sent: Thursday, November 13, 2003 12:29 AM
To: Xin LI/=C0=EE=F6=CE
Cc: current@freebsd.org
Subject: RE: Recent -CURRENT panic (New interrupt code related?); =
backtrace
included


> Do you have 'device apic' enabled?  If so, can you try using 'options
NO_MIXED_MODE'.
> Barring that, can you try
http://www.FreeBSD.org/~jhb/patches/spurious.patch and if that doesn't =
work
> http://www.FreeBSD.org/~jhb/patches/atpic.patch?