Date: 09 Jan 2003 17:46:52 +0000 From: Doug Rabson <dfr@nlsystems.com> To: Arun Sharma <adsharma@unix-os.sc.intel.com> Cc: freebsd-ia64@FreeBSD.ORG Subject: Re: Running on SKI ? Message-ID: <1042134412.30715.18.camel@builder02.qubesoft.com> In-Reply-To: <20030108183729.A31452@unix-os.sc.intel.com>
index | next in thread | previous in thread | raw e-mail
On Thu, 2003-01-09 at 02:37, Arun Sharma wrote:
> I tried to run on SKI and found a bunch of issues:
>
> 1) machdep.c: Assertion failure
>
> #ifndef SKI
> /* Map the memory mapped I/O Port space */
> KASSERT(ia64_port_base != 0,
> ("%s: no I/O port memory region", __func__));
> map_port_space();
> #endif
I haven't seen this but then I haven't tried to run a kernel in SKI for
months.
>
> 2) Writing to ar.fcr gives a general exception. I had to comment it out:
>
> swtch.s:
>
> //mov ar.fcr=r16
This I know about. The ia32 support in SKI is pretty broken right now.
>
> 3) Alternate data TLB faults in msgaddchar. This is where I got stuck.
>
> 4) The SKI config file needs COMPAT_FREEBSD4 - otherwise the code doesn't
> compile.
>
> Also, other unrelated questions:
>
> - Is there a way to make symbols work with SKI ? symlist shows the
> symbols for dfr's bootloader, but not for the kernel.
I have a SKI command file which carefully runs the bootloader up to the
first instruction of the kernel and then breaks. You can find it in
src/sys/ia64/skiload/skiload.cmd. You should be using skiload to load
the kernel rather than the ancient linux-derived bootloader I started
with. This might be the cause of your msgaddchar problems, I guess.
>
> - Is there a way to make boot_verbose work with this bootloader ?
With skiload, use boot -v as usual.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1042134412.30715.18.camel>
