From owner-freebsd-current@FreeBSD.ORG Mon Jun 28 14:25:18 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82B541065679 for ; Mon, 28 Jun 2010 14:25:18 +0000 (UTC) (envelope-from nwf@cs.jhu.edu) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) by mx1.freebsd.org (Postfix) with ESMTP id 419E38FC08 for ; Mon, 28 Jun 2010 14:25:17 +0000 (UTC) Received: from gradx.cs.jhu.edu (gradx.cs.jhu.edu [128.220.13.52]) by blaze.cs.jhu.edu (8.14.3/8.14.3) with ESMTP id o5SEPFL6027775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Jun 2010 10:25:16 -0400 (EDT) Received: from gradx.cs.jhu.edu (localhost [127.0.0.1]) by gradx.cs.jhu.edu (8.14.3/8.13.1) with ESMTP id o5SEPFIP002750; Mon, 28 Jun 2010 10:25:15 -0400 Received: (from nwf@localhost) by gradx.cs.jhu.edu (8.14.3/8.13.8/Submit) id o5SEPF5k002749; Mon, 28 Jun 2010 10:25:15 -0400 Date: Mon, 28 Jun 2010 10:25:15 -0400 From: Nathaniel W Filardo To: freebsd-current@freebsd.org Message-ID: <20100628142515.GT21929@gradx.cs.jhu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kkj3vgNzAWGjboLC" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-08-17) X-Mailman-Approved-At: Mon, 28 Jun 2010 15:44:57 +0000 Cc: Alan Cox Subject: [sparc64] [panic] cheetah_ipi_selected: CPU can't IPI itself 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: Mon, 28 Jun 2010 14:25:18 -0000 --kkj3vgNzAWGjboLC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Well, I'm back in the same town as my sparc64 and so csup'd, built, and rebooted, trying to get more information about the "vm object not owned" panic I reported a while ago. To my dismay, I now get this panic, also late enough in the boot process to be starting up jails: panic: cheetah_ipi_selected: CPU can't IPI itself cpuid = 0 KDB: stack backtrace: panic() at panic+0x1c8 cheetah_ipi_selected() at cheetah_ipi_selected+0x48 tlb_page_demap() at tlb_page_demap+0xdc pmap_copy_page() at pmap_copy_page+0x4c4 vm_fault() at vm_fault+0x13ec trap_pfault() at trap_pfault+0x190 trap() at trap+0xd0 -- data access protection tar=0x224b93 sfar=0x224550 sfsr=0x800005 %o7=0x4063398c -- userland() at 0x40633830 user trace: trap %o7=0x4063398c ... And the system hangs; I had to use the ALOM to reboot it. Sorry to not have more useful news. --nwf; --kkj3vgNzAWGjboLC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwosMsACgkQTeQabvr9Tc8E2wCfQy3mLluttdNnJ18d0QUXakFr tBoAnRE3HyeOX9gkKXj1921VYn7VXy1j =YyJ7 -----END PGP SIGNATURE----- --kkj3vgNzAWGjboLC--