Date: Tue, 17 Nov 2015 20:57:13 +0000 From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: Marius Strobl <marius@alchemy.franken.de>, Alexey Dokuchaev <danfe@freebsd.org>, "freebsd-sparc64@freebsd.org" <freebsd-sparc64@freebsd.org> Subject: Re: PCI range checking under qemu-system-sparc64 Message-ID: <564B94A9.70003@ilande.co.uk> In-Reply-To: <CAJ-Vmo=eaDCp4CoDJQu50PPSr6F3XSa0nLLj8460YhifzTEn6g@mail.gmail.com> References: <20150913180126.GC7862@alchemy.franken.de> <55F89861.1030107@ilande.co.uk> <20150916031030.GA6711@FreeBSD.org> <55F9C2B8.7030605@ilande.co.uk> <20150916211914.GD18789@alchemy.franken.de> <20150917082817.GA71811@FreeBSD.org> <55FBB662.4080708@ilande.co.uk> <20150919211420.GK18789@alchemy.franken.de> <55FDEA3C.1010804@ilande.co.uk> <20150920043630.GA36162@FreeBSD.org> <20150922221404.GA81100@alchemy.franken.de> <563F8722.9050503@ilande.co.uk> <56462A41.4030707@ilande.co.uk> <CAJ-Vmo=eaDCp4CoDJQu50PPSr6F3XSa0nLLj8460YhifzTEn6g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/11/15 16:44, Adrian Chadd wrote: > Hi > > so at this point it's just hanging, right? You can break into the > debugger, but that's it? Well it traps into the debugger by itself, but the debugger seems operable so it should be easy enough for someone with a bit of kernel knowledge to add some strategic breakpoints to an unstripped kernel at figure out at what point it starts to go wrong... > What do I do to get freebsd-head sparc64 to this point myself? :) I've just pushed the branch to https://github.com/mcayland/qemu.git (branch freebsd-sparc64) if you're interested to take a look. I normally cross-build a -CURRENT ISO with debug enabled and then boot QEMU with the ISO like this: ./qemu-system-sparc64 -cdrom freebsd.iso -boot d -nographic ATB, Mark.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564B94A9.70003>