From owner-svn-src-all@FreeBSD.ORG Tue May 31 22:16:08 2011 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29964106564A; Tue, 31 May 2011 22:16:07 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id F07BB8FC1A; Tue, 31 May 2011 22:16:06 +0000 (UTC) Received: by wwc33 with SMTP id 33so5173973wwc.31 for ; Tue, 31 May 2011 15:16:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=t8V3nfW2V3v/DKm3Ql7WN5zR7I+6WEhZmvu2grW1IxQ=; b=ikFTCPW4ObnZ7iRDom8DxJDeDE8SOnj8/2L5JcBwgr0xWegFYevgtaukt38kaBmiKI XN6d/cMBr4UHHabklGmlEFkcZqFcGQV3veDwdqpuZUDV+sJkQqYjjWkoX2DKuzdArGl5 k9ZCOcqTTFpHNuwr+0AHwOsC9/p3C/FhcRpEI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=A4J42FrduTf1kM0lYc2peZ0XXDw7jz5Fs+PDMN9LwJ+Drqv3gxcCGqNQNCnTMvpwuG THjoPHveiJlXWRF2pTYuf0z76HIdNYzAMLOi6jXakBCzCL1PDuLfq6U2hjoKcUjBoI6p eDmflV9E3670JwYuGoPIT46eHEJ9qsHlZZY1Q= MIME-Version: 1.0 Received: by 10.216.221.158 with SMTP id r30mr4199047wep.50.1306880165766; Tue, 31 May 2011 15:16:05 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.216.93.193 with HTTP; Tue, 31 May 2011 15:16:05 -0700 (PDT) In-Reply-To: <20110531221122.GA58836@nargothrond.kdm.org> References: <201105311729.p4VHTwrZ033296@svn.freebsd.org> <20110531214618.GA57498@nargothrond.kdm.org> <20110531221122.GA58836@nargothrond.kdm.org> Date: Tue, 31 May 2011 15:16:05 -0700 X-Google-Sender-Auth: fjohNvmx0_OopfwXg8uRDUEsbI0 Message-ID: From: mdf@FreeBSD.org To: "Kenneth D. Merry" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r222537 - in head/sys: kern sys X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 22:16:08 -0000 On Tue, May 31, 2011 at 3:11 PM, Kenneth D. Merry wrote: > On Tue, May 31, 2011 at 15:02:37 -0700, mdf@FreeBSD.org wrote: >> On Tue, May 31, 2011 at 2:46 PM, Kenneth D. Merry wrot= e: >> > On Tue, May 31, 2011 at 14:00:18 -0700, mdf@FreeBSD.org wrote: >> >> On Tue, May 31, 2011 at 10:29 AM, Kenneth D. Merry = wrote: >> >> > Author: ken >> >> > Date: Tue May 31 17:29:58 2011 >> >> > New Revision: 222537 >> >> > URL: http://svn.freebsd.org/changeset/base/222537 >> >> > >> >> > Log: >> >> > ?Fix apparent garbage in the message buffer. >> >> > >> >> > ?While we have had a fix in place (options PRINTF_BUFR_SIZE=3D128) = to fix >> >> > ?scrambled console output, the message buffer and syslog were still= getting >> >> > ?log messages one character at a time. ?While all of the characters= still >> >> > ?made it into the log (courtesy of atomic operations), they were of= ten >> >> > ?interleaved when there were multiple threads writing to the buffer= at the >> >> > ?same time. >> >> >> >> This seems to panic my box with "lock "msgbuf" 0xfffffe0127ffffe0 >> >> already initialized". >> >> >> >> Unfortunately, though I booted with a fresh CURRENT this morning >> >> successfully, both /boot/kernel and /boot/kernel.old give this panic. >> >> To add insult to injury, when the kernel drops into the debugger, my >> >> keyboard input no longer works so I can't get a stack, etc. >> > >> > Uh-oh! >> > >> >> So: >> >> >> >> 1) Is there anything else I can do to help debug this? >> >> 2) how can I resurrect this box without a reinstall? >> >> >> >> I will try to repro on a virtual machine so I have a snapshot to come= back to. >> > >> > My guess is that this is an issue with the message buffer reinitializa= tion >> > path. ?lock_init() (called by mtx_init()) has an assert to make sure t= hat >> > the lock is initialized, and that is just a flag check. >> > >> > Since the spin lock is part of the message buffer structure, if it is = held >> > over from a previous boot, the LO_INITIALIZED flag may still be set. >> > >> > Try power cycling the machine. ?If it is an issue with re-initializati= on, >> > that should clear the memory and allow you to boot. >> >> Hmm, apparently my previous presses of the power button weren't long >> enough. =A0I let it sit off for 20 seconds and it boots okay now. > > Okay, so it probably is the re-initialization code. =A0Can you try this p= atch > and see if it survives a warm boot? =A0I also changed the initialization > path, so we don't get tripped up by garbage left in memory. This patch survived a warm reboot (shutdown -r now). > Also, does the debugger work now that it has booted successfully? The debugger (or rather, my keyboard in the debugger) works on a successful boot. I used sysctl debug.kdb.enter=3D1 to test it. Thanks, matthew