From owner-freebsd-current@FreeBSD.ORG Tue Jun 29 19:31:23 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 32249106564A for ; Tue, 29 Jun 2010 19:31:23 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id B7E2B8FC0A for ; Tue, 29 Jun 2010 19:31:22 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id o5TJVJZc012852; Tue, 29 Jun 2010 21:31:19 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id o5TJVJBR012851; Tue, 29 Jun 2010 21:31:19 +0200 (CEST) (envelope-from marius) Date: Tue, 29 Jun 2010 21:31:19 +0200 From: Marius Strobl To: Nathaniel W Filardo Message-ID: <20100629193118.GA11601@alchemy.franken.de> References: <20100628142515.GT21929@gradx.cs.jhu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628142515.GT21929@gradx.cs.jhu.edu> User-Agent: Mutt/1.4.2.3i Cc: Alan Cox , freebsd-current@freebsd.org Subject: Re: [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: Tue, 29 Jun 2010 19:31:23 -0000 On Mon, Jun 28, 2010 at 10:25:15AM -0400, Nathaniel W Filardo wrote: > 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. Could please give the following patch a try? http://people.freebsd.org/~marius/sparc64_pin_ipis.diff If that doesn't fix the above panic I have no clue how this can happen apart from the per-CPU pages getting corrupted. Marius