From owner-freebsd-current Mon Dec 10 10:57: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 53DCF37B41C for ; Mon, 10 Dec 2001 10:56:58 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id fBAIuwo50278 for current@FreeBSD.ORG; Mon, 10 Dec 2001 10:56:58 -0800 (PST) (envelope-from david) Date: Mon, 10 Dec 2001 10:56:58 -0800 (PST) From: David Wolfskill Message-Id: <200112101856.fBAIuwo50278@bunrab.catwhisker.org> To: current@FreeBSD.ORG Subject: Re: panic: blockable sleep lock (sleep mutex) with today's -CURRENT In-Reply-To: <200112101802.fBAI2O850051@bunrab.catwhisker.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Mon, 10 Dec 2001 10:02:24 -0800 (PST) >From: David Wolfskill >I managed to get a panic on my (SMP) "build machine" on the first reboot >after building -CURRENT.... Well, the laptop finshed building & booting from (nearly) the same sources, so I suspect either hardware or an SMP issue -- more likely the former. (Machine didn't come out of the panic; said it was rebooting, but then got: Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot <-- Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs timeout stopping cpus cpu_reset: Restarting BSP cpu_reset: Failed to restart BSP and it remains rather catatonic at this point. Sorry for the noise, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message