From owner-freebsd-sparc64@freebsd.org Thu Sep 17 08:48:42 2015 Return-Path: Delivered-To: freebsd-sparc64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 422EB9CE8C8 for ; Thu, 17 Sep 2015 08:48:42 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 32E101141; Thu, 17 Sep 2015 08:48:42 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 3115C1405; Thu, 17 Sep 2015 08:48:42 +0000 (UTC) Date: Thu, 17 Sep 2015 08:48:42 +0000 From: Alexey Dokuchaev To: Mark Cave-Ayland Cc: Marius Strobl , "freebsd-sparc64@freebsd.org" Subject: Re: PCI range checking under qemu-system-sparc64 Message-ID: <20150917084842.GA78467@FreeBSD.org> References: <55EC2E8D.4020803@ilande.co.uk> <20150906124859.GA14919@FreeBSD.org> <20150907203152.GA70457@alchemy.franken.de> <55EDFE00.9090109@ilande.co.uk> <20150913022143.GA7862@alchemy.franken.de> <20150913103940.GA60101@FreeBSD.org> <20150913180126.GC7862@alchemy.franken.de> <55F89861.1030107@ilande.co.uk> <20150916031030.GA6711@FreeBSD.org> <55F9C2B8.7030605@ilande.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55F9C2B8.7030605@ilande.co.uk> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 08:48:42 -0000 On Wed, Sep 16, 2015 at 08:27:52PM +0100, Mark Cave-Ayland wrote: > [...] > Also how does the boot log compare with a complete boot log -- often > looking at what the next line is on a complete boot log gives a hint as > where things are going wrong. I've boot with boot_verbose=1; most of the new output looks unrelated. One extra line is printed after IPsec init message befor the hang: IPsec: Initialized Security Association Processing. lo0: bpf attached KDB: enter: Break to debugger [ thread pid 11 tid 100004 ] Stopped at kdb_enter+0x80: ta %xcc, 1 db> show intrcnt pil11: filter 3 vec2027: uart0 3 db> Backtrace looks the same as in my previous email to Marius, yet there are some interrupts shown this time. ./danfe