Date: Wed, 09 Sep 2015 21:18:57 +0100 From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: John Baldwin <jhb@FreeBSD.org>, "freebsd-sparc64@freebsd.org" <freebsd-sparc64@freebsd.org> Subject: Re: PCI range checking under qemu-system-sparc64 Message-ID: <55F09431.4080807@ilande.co.uk> In-Reply-To: <20150907092310.GA67083@FreeBSD.org> References: <557DA6D5.4070800@FreeBSD.org> <557DCF54.7020606@ilande.co.uk> <A88F6A52-FA8A-4669-A2D6-23374F8E26BB@FreeBSD.org> <557DF887.20508@ilande.co.uk> <20150906110308.GA68829@FreeBSD.org> <55EC2E8D.4020803@ilande.co.uk> <20150906124859.GA14919@FreeBSD.org> <55EC3949.1020508@ilande.co.uk> <20150906134245.GA21410@FreeBSD.org> <55EC4C43.9050700@ilande.co.uk> <20150907092310.GA67083@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/09/15 10:23, Alexey Dokuchaev wrote:
> On Sun, Sep 06, 2015 at 03:22:59PM +0100, Mark Cave-Ayland wrote:
>> On 06/09/15 14:42, Alexey Dokuchaev wrote:
>>> Hmm, I'm running GENERIC, so it looks like everything should be already
>>> there, no? At least by looking at ./conf/files.sparc64 I don't see what
>>> else ("device ???") should I add to it to get su/kb_ps2 support...
>>
>> I'm afraid I'm not really a BSD person, but a quick browse at the source
>> on github suggests you need these drivers:
>>
>> https://github.com/freebsd/freebsd/blob/master/sys/dev/uart/uart_bus_ebus.c
>> https://github.com/freebsd/freebsd/blob/master/sys/dev/atkbdc/atkbdc_ebus.c
>
> Right, both of them are compiled-in by default.
>
>> It also looks like you'd need to hack atkbdc_ebus.c to allow "kb_ps2" as
>> a device name rather than just trying to match on "8042", although this
>> could potentially be fixed by renaming the device in OpenBIOS moving
>> forwards as long as it doesn't cause any regressions.
>
> I've patched it to allow "kb_ps2", and removed some stuff like INVARIANTS,
> WITNESS, IPSEC, etc. in faint hope to eliminate problematic code path, but
> it did not help: it still hangs, apparently in the same place.
>
> I'll try to trim kernel config a bit more, and of course would welcome any
> other ideas/patches to try, thanks!
I should add that if you can sprinkle some debug statements or similar
around to find out exactly where the attach is failing and post the
results here, that would be extremely helpful until I can get my FreeBSD
environment back up and running again.
ATB,
Mark.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55F09431.4080807>