From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 01:19:10 2004 Return-Path: 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 BBCD116A4CE for ; Mon, 11 Oct 2004 01:19:10 +0000 (GMT) Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9768343D1F for ; Mon, 11 Oct 2004 01:19:10 +0000 (GMT) (envelope-from roberthuff@rcn.com) Received: from 209-6-197-67.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.197.67] helo=jerusalem.litteratus.org.litteratus.org) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #7) id 1CGoqD-0001bp-00 for current@freebsd.org; Sun, 10 Oct 2004 21:19:10 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16745.57237.472660.492897@jerusalem.litteratus.org> Date: Sun, 10 Oct 2004 21:19:17 -0400 To: current@freebsd.org X-Mailer: VM 7.17 under 21.5 (beta16) "celeriac" XEmacs Lucid Subject: "panic: spin lock entropy harvest mutex not in order list" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 01:19:10 -0000 About 2000 UTC Sunday I cvsuped system source and rebuilt. "make buildworld" went fine. (Log available) "make buildkernel" also good. (Log also available) I installed the new kernel and rebooted. When the system came up, I got: Real memory: XXXXXXXXX Avail memory: YYYYYYYYY panic: spin lock entropy harvest mutex not in order list KDB: enter: panic [thread 0] ddb> at which point neither the USB or PS/2 keyboards were recognized. (i.e. no trace or dump) I still have a workable machine (and volunteer as poster person for why the procedure in the Handbook is correct); I also have a debug kernel, dmesg (from the old kernel - no hardware changes) and kernel config available on request. I checked the mailing list archives and UPDATING and found nothing which seemed applicable. Have I just caught a hiccup in the development process? Robert Huff