> > Seems to be running - does top show nvsetvol eating up CPU time?
>
> top - 17:04:38 up 4 min, 2 users, load average: 1.04, 0.51, 0.20
> Tasks: 40 total, 2 running, 38 sleeping, 0 stopped, 0 zombie
> Cpu(s): 14.3% user, 48.0% system, 0.0% nice, 37.7% idle
> Mem: 100744k total, 54624k used, 46120k free, 1944k buffers
> Swap: 142028k total, 0k used, 142028k free, 38116k cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 634 root 19 0 292 292 236 R 91.2 0.3 1:52.21 nvsetvol
I see - in fact, I was able to reproduce this on a G3 oldworld here. It
seems the nvram format is broken and results in a size of 0 bytes for the
nvram buffer, which is used as an increment for reading the next buffer.
I'll compare the nvsetvol way of reading the nvram to the nvsetenv way and
cook up a more robust way for finding the pram...
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
