On Friday 12 January 2001  1:17 pm, Ben Harris wrote:
> On Fri, 12 Jan 2001, Chris Gilbert wrote:
> > Done, compiles (note that I've only just synced up recently so it's
> > source from about 9 or 10pm)  but it does have a sys/arch/arm dir :)
>
> Check that (e.g.) machine/varargs.h just contains "#include
> <arm/varargs.h>".  If it does, then you've got the post-header-merge
> version.

Ok will do

> > Currently I'm having fun chasing a bug with UBC, or probably the pmap/uvm
> > stuff, seems that if we've got maxproc above some val between 96 and 104
> > (at 104 it actually hangs, doesn't find the root device, above this it
> > does fail with UBC_init error) UBC_init fails, note that I'm about to
> > chase it with UVMHISTORY and _PRINT (although the PRINT bit makes booting
> > really really slow, but at least I've got it narrowed down a bit, anyone
> > know of a less painful way to chase this kind of bug?).
>
> You don't need to turn on history printing -- you can call uvm_hist() or
> uvmhist_dump() from DDB.  What's the precise panic message, anyway?

ahh, great.  Panic message is:
panic: ubc_init: failed to map ubc_object

call to uvm_hist shows that:
uvm_map is called with:
map=0xf01b22b8,m *startp=0x0, size=8388608, flags=0x41727

this calls uvm_map_findspace
it gets a:
<- failed (off end)
calling recursively, no align

calls it again, and again gets failed (off end)
uvm_map reports that uvm_map_findspace has failed.

trying uvmhist_dump causes a translation fault (section).

> > Yep, I spotted that files.arm32 had changed, so did a reconfig.
>
> There'll be more changes there as I merge in the .c files...

Ok I'll do a compile as I spot the changes happen :)

Cheers,
Chris