[9fans] no free mount rpc buffer

[9fans] no free mount rpc buffer

[forsyth]

i don't think SEGMAPSIZE will make a big difference (it's just the size
of an array, and i have used tiny machines with a large SEGMAPSIZE).
don't configure #b, and bump up kernelpercent if necessary.

>> (you can put some of it in the plan9.ini file on the boot diskette, though i don't think
>> the details are documented.)

>seeing nothing about nvram except for the key stuff which reads/write to disk. I'll look at

i might have been more helpful: see /sys/src/9/boot/ip.c,
and its use of readfile("#e/...", ...), knowing that the plan9.ini values
are visible in the environment, #e.

[9fans] no free mount rpc buffer

[James]

> the kernel has run out of memory and thus buffer space.
> the EOFs probably result from that, too.
> i'd check the allocation sizes printed at startup.
> you can see the current state of allocation by typing
> 	control-t control-t x
> on the console.
> since the system has only just started, it seems likely
> that it is confused about how much memory it has got
> (or reserved for the kernel).

The easiest solution by far, and for only $20.00, was to upgrade the
system to a whopping 8mb simm. Everything runs fine now. =)

Jim

[9fans] no free mount rpc buffer

[James]

> (you can put some of it in the plan9.ini file on the boot diskette, though i don't think
> the details are documented.)

I remembered you talking about diskless cpu servers, but I was looking around the code and
seeing nothing about nvram except for the key stuff which reads/write to disk. I'll look at
b.com next, I guess.

> since the system has only just started, it seems likely
> that it is confused about how much memory it has got
> (or reserved for the kernel).

Ah. I had changed SEGMAPSIZE to 64 awhile ago. Perhaps that's causing
the problem -- this machine only has 4 megs (I turned off dns, but left
everything else in).


Jim

[9fans] no free mount rpc buffer

[forsyth]

>>and I'm wondering if one of the problems is the fact that I don't have
>>a prep'ed disk, and therefore have no nvram location to read/write.

no, it will simply prompt for the information it needs.
(you can put some of it in the plan9.ini file on the boot diskette, though i don't think
the details are documented.)
most of my cpu servers are diskless, with just a boot diskette.

>>   aux/listen: no free mount rpc buffer
>>    bind: no free mount rpc buffer

the kernel has run out of memory and thus buffer space.
the EOFs probably result from that, too.
i'd check the allocation sizes printed at startup.
you can see the current state of allocation by typing
	control-t control-t x
on the console.
since the system has only just started, it seems likely
that it is confused about how much memory it has got
(or reserved for the kernel).

[9fans] no free mount rpc buffer

[James]

What I'm trying to do is install a new cpu server, and once it is up
and running make it into the bootp/auth server.  I am having a hard time
and I'm wondering if one of the problems is the fact that I don't have
a prep'ed disk, and therefore have no nvram location to read/write.

I've got a boot floppy with a bb bootsectore, and the files b.com,
9pccpudisk, and a plan9.ini. The floppy boots up just fine, and asks me
for the network config (just like my normal auth server) and then it asks
for the nvram info:

	password: <my fs password>
	authid: root (I use 'root' instead of bootes on my current cpu/auth server)
	authdom: stanford.edu (???? I *think* this is what I used before)
	
It seems to take this, it obviously mounts the fs because it executes
the /bin/cpurc and prints out some messages in it, but then it spews
forth various errors:

    aux/listen: no free mount rpc buffer
    bind: no free mount rpc buffer
    aux/icmp: no free mount rpc buffer
    bind: no free mount rpc buffer
    bind: no free mount rpc buffer
    rc: file /rc/bin/cpurc: line 65: token EOF: syntax error
    rc: file /rc/lib/rcmain: line 30: token EOF: syntax error
    init: rc exit status: rc 7:cpurc 47:can't exec
    
    criswell password: <my fs password>
    criswell% <type-any-command-and-it-never-returns>
    
my fs was in allow mode during this operation, my normal auth server
was offline. My normal cpu/auth server boots up without any of these
errors. I've checked cpurc and rcmain, and they look fine to me in
terms of rc code -- nothing link a missing '}'.


Jim