From owner-freebsd-alpha@FreeBSD.ORG Mon Feb 13 17:26:27 2006 Return-Path: X-Original-To: freebsd-alpha@freebsd.org Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41FF216A420 for ; Mon, 13 Feb 2006 17:26:27 +0000 (GMT) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D780943D7F for ; Mon, 13 Feb 2006 17:26:16 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id k1DHQE8U025752 for ; Mon, 13 Feb 2006 11:26:14 -0600 (CST) (envelope-from rand@meridian-enviro.com) Date: Mon, 13 Feb 2006 11:26:14 -0600 Message-ID: <87u0b35fwp.wl%rand@meridian-enviro.com> From: "Douglas K. Rand" To: freebsd-alpha@freebsd.org User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: ClamAV 0.88/1286/Mon Feb 13 05:41:56 2006 on newman.meridian-enviro.com X-Virus-Status: Clean Subject: SMP problem on UP2000+ X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2006 17:26:27 -0000 I have a UP2000+ system from Microway with two 833 MHz CPUs, and it keeps freezing up on me when I run it with a SMP kernel. The hangs always seem to come at times of high disk IO, such as nightly backups or heavy MySQL usage or buildworlds. (The system does my cacti resource graphing.) I've got a debug kernel installed, but I can never break into the kernel nor do I ever get a core dump. I've experienced this problem with both 6.0 and 6_RELENG. I'm coming up on 4 days of uptime with a kernel that doesn't have SMP which is easily four times that of a kernel with SMP. I was running a gmirror of two 75 GB SCSI disks on the onboard controller, and to simply see if it was a factor I destroyed the mirror and am now only using one disk. I had hangs both with and with gmirror. Here are the messgaes I get on the console, when I get them. Sometimes the system simply hangs. panic: lockmgr: thread 0xfffffc007d9c4d20, not exclusive lock holder 0xfffffc007d9d5260 unlocking cpuid = 1 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc0000566978 ra = 0xfffffc0000566958 sp = 0xfffffe00319779f0 curthread = 0xfffffc007d99aa80 pid = 35, comm = syncer panic: trap cpuid = 0 Uptime: 15d15h9m11s fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc0000566978 ra = 0xfffffc0000566958 sp = 0xfffffe0031977638 curthread = 0xfffffc007d99aa80 pid = 35, comm = syncer panic: trap cpuid = 0 ******************************************************************************** panic: lockmgr: thread 0xfffffc007d9fcd20, not exclusive lock holder 0xfffffc0056380540 unlocking cpuid = 1 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc00004595b8 ra = 0xfffffc0000459598 sp = 0xfffffe0031943af0 curthread = 0xfffffc007d9fe540 pid = 31, comm = syncer ******************************************************************************** panic: lockmgr: thread 0xfffffc007d9fcd20, not exclusive lock holder 0xfffffc0052d76fc0 unlocking cpuid = 1 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc00004595b8 ra = 0xfffffc0000459598 sp = 0xfffffe0031943af0 curthread = 0xfffffc007d9fe540 pid = 31, comm = syncer ******************************************************************************** panic: lockmgr: thread 0xfffffc007d9dad20, not exclusive lock holder 0xfffffc00596987e0 unlocking cpuid = 1 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 1 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc000045a728 ra = 0xfffffc000045a708 sp = 0xfffffe003193baf0 curthread = 0xfffffc007d9dc2a0 pid = 30, comm = syncer ******************************************************************************** fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc000045a728 ra = 0xfffffc000045a708 sp = 0xfffffe0031983c30 curthread = 0xfffffc007d9a8540 pid = 21, comm = intr: ahc0 ******************************************************************************** panic: lockmgr: thread 0xfffffc0063496d20, not exclusive lock holder 0xfffffc0064bac540 unlocking cpuid = 0 ******************************************************************************** panic: lockmgr: thread 0xfffffc00649c47e0, not exclusive lock holder 0xfffffc0058020fc0 unlocking cpuid = 1 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 1 faulting va = 0x48 type = access violation cause = load instructon pc = 0xfffffc0000491e08 ra = 0xfffffc0000491de8 sp = 0xfffffe0031935b30 curthread = 0xfffffc007da1e7e0 pid = 32, comm = syncer ******************************************************************************** panic: lockmgr: thread 0xfffffc007da1cd20, not exclusive lock holder 0xfffffc0063ffc000 unlocking cpuid = 1 ******************************************************************************** panic: lockmgr: thread 0xfffffc007d9eba40, not exclusive lock holder 0xfffffc005e7e4fc0 unlocking cpuid = 1