Date: Thu, 17 Sep 2015 08:48:42 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> Cc: Marius Strobl <marius@alchemy.franken.de>, "freebsd-sparc64@freebsd.org" <freebsd-sparc64@freebsd.org> Subject: Re: PCI range checking under qemu-system-sparc64 Message-ID: <20150917084842.GA78467@FreeBSD.org> In-Reply-To: <55F9C2B8.7030605@ilande.co.uk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150917084842.GA78467>