Date: Thu, 13 Nov 2003 23:13:25 +0800 From: "=?gb2312?B?WGluIExJL8Du9s4=?=" <delphij@frontfree.net> To: "'John Baldwin'" <jhb@FreeBSD.org>, "=?gb2312?B?J1hpbiBMSS/A7vbOJw==?=" <delphij@frontfree.net> Cc: current@freebsd.org Subject: RE: Recent -CURRENT panic (New interrupt code related?); backtrace included Message-ID: <20031113151325.8A2275299@ftp.bjpu.edu.cn> In-Reply-To: <XFMail.20031112112910.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031113151325.8A2275299>