Date: Tue, 19 Dec 2006 11:32:30 +1300 From: Andrew Turner <andrew@fubar.geek.nz> To: grehan@freebsd.org Cc: freebsd-ppc@freebsd.org Subject: Re: FreeBSD on an Efika Message-ID: <20061219113230.34182787@hermies.int.fubar.geek.nz> In-Reply-To: <4586CA29.10803@freebsd.org> References: <20061218104841.72ba51ea@hermies.int.fubar.geek.nz> <4585CCC1.7050005@freebsd.org> <20061218222327.308dca53@hermies.int.fubar.geek.nz> <4586CA29.10803@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Dec 2006 09:04:41 -0800 Peter Grehan <grehan@freebsd.org> wrote: > Hi Andrew, > > > I'm getting correct values from mem_regions. I can read from the > > physical address. > > What values are you getting back ? Does it look like what the > system should have ? For reg I'm getting the range 0x0 - 0x8000000. For available I'm getting the ranges 0x19111e4 - 0x02000000 and 0x24ff000 - 0x08000000. These are consistent with the values retrieved from the open firmware prompt. > Did you read as well as write the physical value ? Yes I can read and write to the physical address. > > > It is reading from msgbufp where it stop working. > > What're the virtual/physical values used when creating the msgbuf > mapping with pmap_kenter() in machdep.c:powerpc_init() ? The physical address is 0x1922000, the virtual address is 0xd0005000. > After that > mapping has been created, can you read/write to the buffer in that > routine ? Attempting to read or write to the value causes the kernel to stop. > Do you end up in the trap handler if you touch msgbuf ? Not as far as I can tell. > > pmap_kenter() is fundamental to the operation of the system and > probably OK, so something else must be afoot. > > later, > > Peter. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061219113230.34182787>