From owner-freebsd-current@FreeBSD.ORG Sun Jul 29 06:29:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56ADC106564A; Sun, 29 Jul 2012 06:29:58 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C86F08FC0A; Sun, 29 Jul 2012 06:29:57 +0000 (UTC) Received: by obbun3 with SMTP id un3so8957224obb.13 for ; Sat, 28 Jul 2012 23:29:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w+WTNCV58Z/V5Neq+ACEFPN4J9M8DFVhswsP63nAziA=; b=ogsrMzIxeLJ4e0NCLhd+cTd60u9aH+sEtv76o3jO2SXGZaOvOsDRJ0RhebCuLDS/Q/ wInK2lpeXRyGaE1KXAAO753qT+ExglRoYlbMqnidey/tqVPapWkr+MPVpl+c/+4FyX6D ximGUU3J67PQtJ5R0iDnJ0iYNHTIJKnlDGN+rvBkX2QwI9iWIpggDJYKH2KVPY2uKFPG opeRjNREJS/seXVee7KOZNmXYf64FVY5glPC1OkhwUHEjwT8cB1A0HhvTgPOHAYPZ1qc CP1RYHvxgGCV+i79a8RVQESwPA5adJZ1TYsvJnRN8Li6hBbYhrbfIM6pVVH6K94rV1g9 iqwA== MIME-Version: 1.0 Received: by 10.60.29.230 with SMTP id n6mr11229725oeh.22.1343543397123; Sat, 28 Jul 2012 23:29:57 -0700 (PDT) Received: by 10.76.84.7 with HTTP; Sat, 28 Jul 2012 23:29:57 -0700 (PDT) In-Reply-To: <20120729051509.GA40138@eureka.lemis.com> References: <20120729045354.GA1054@weller-fahy.com> <20120729051509.GA40138@eureka.lemis.com> Date: Sat, 28 Jul 2012 23:29:57 -0700 Message-ID: From: Garrett Cooper To: "Greg 'groggy' Lehey" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: Panic on boot after svn update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 29 Jul 2012 06:29:58 -0000 On Sat, Jul 28, 2012 at 10:15 PM, Greg 'groggy' Lehey wrote: > On Sunday, 29 July 2012 at 0:53:55 -0400, David J. Weller-Fahy wrote: >> So, I recently updated and encountered a panic on boot which is >> reproducible, and wanted to see if anyone's encountered this before I >> file a PR. I found a problem in (I think) recent changes to the e1000 >> driver. I'm running FreeBSD 10-CURRENT as a VirtualBox guest. >> >> #v+ >> FreeBSD fork-pooh 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r238764: Sat Jul 28 17:21:47 EDT 2012 root@fork-pooh:/usr/obj/usr/src/sys/GENERIC amd64 >> #v- >> >> I have the Adapter Type set to, "Intel PRO/1000 MT Desktop (82540EM)", and the >> following card is detected by pciconf. >> ... >> Updating motd:. >> Starting ntpd. >> panic: _mtx_lock_sleep: recursed on non-recursive mutex em0 @ /usr/src/sys/dev/e1000/if_lem.c:881 > > Me too The panic message is identical, and I'm also running > in VirtualBox. My version string (from strings on the kernel) is: > > FreeBSD 10.0-CURRENT #4: Sat Jul 28 09:45:10 EST 2012 > root@swamp.lemis.com:/usr/obj/src/FreeBSD/svn/head/sys/GENERIC > > Note that this is a different EST (UTC+10). > > I have a dump, but I can't get much sense out of it: > > kgdb: kvm_read: invalid address (0x354540a) > #0 0x00000000 in ?? () > > I'm currently rebuilding the system, but it looks as if that won't > help much. One interesting point is that the first panic happened > after installing the new image (from yesterday's sources) while I was > trying to reboot with the old kernel, dating back to > > FreeBSD swamp.lemis.com 10.0-CURRENT FreeBSD 10.0-CURRENT #3: Sun May 13 14:34:43 EST 2012 root@swamp.lemis.com:/usr/obj/src/FreeBSD/svn/head/sys/GENERIC i386 See this thread: http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035593.html . -Garrett