From owner-freebsd-current@FreeBSD.ORG Sun Jul 29 05:15:12 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 A1A3B106566B for ; Sun, 29 Jul 2012 05:15:12 +0000 (UTC) (envelope-from grog@lemis.com) Received: from w3.lemis.com (w3.lemis.com [208.86.224.149]) by mx1.freebsd.org (Postfix) with ESMTP id 6FC208FC0A for ; Sun, 29 Jul 2012 05:15:12 +0000 (UTC) Received: from eureka.lemis.com (1032.x.rootbsd.net [208.86.224.149]) by w3.lemis.com (Postfix) with ESMTP id 242333B77A for ; Sun, 29 Jul 2012 05:15:11 +0000 (UTC) Received: by eureka.lemis.com (Postfix, from userid 1004) id C102AF74EC; Sun, 29 Jul 2012 15:15:09 +1000 (EST) Date: Sun, 29 Jul 2012 15:15:09 +1000 From: Greg 'groggy' Lehey To: freebsd-current@freebsd.org Message-ID: <20120729051509.GA40138@eureka.lemis.com> References: <20120729045354.GA1054@weller-fahy.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <20120729045354.GA1054@weller-fahy.com> User-Agent: Mutt/1.4.2.3i Organization: The FreeBSD Project Phone: +61-3-5346-1370 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 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 05:15:12 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Greg -- Sent from my desktop computer. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAUxtwACgkQIubykFB6QiOY+gCfQLo/x9d2FjbYQWnyKMXH+s/1 YJsAniMb5VZj6iXzOQmlHuxA5COPXov5 =PE4n -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--