Re: Current port status

matthew green wrote:

> i've had a new crash.  i saw it with a 5.99.65 kernel and a
> very -current kernel, when trying to read a new kernel over NFS
> from the build machine:

What do you mean by "read"? Are you just copying the kernel from NFS with
cp(1), or is the kernel booted from NFS?


> panic: kernel diagnostic assertion "cur->pcg_avail == cur->pcg_size"
> failed: file "/usr/src/sys/kern/subr_pool.c", line 2573 Stopped in pid
>  0.45 (system) at netbsd:cpu_Debugger+0x10:       lwz     r0, 0x14(r1)
> [...]
> not much idea about it yet.  the assert means that because
> we've taken the slow path, the cache should be full.  100%
> repeatable for me.

I couldn't reproduce that during the last days. Neither by running
standalone from NFS nor by copying a kernel or other large files from NFS.


Which network interface did you use? vr(4) or mvgbe(4)?

With the recent 6_beta I realized that vr(4) has become nearly unusable and
frequently gets stuck with "vr0: device timeout". This has been observed
since 5.99.59, but not before 5.99.42.

I have neither the time to look into all that nor am I experienced enough to
fix all the open issues, so I fear that there will be no ofppc release for
6.0.

-- 
Frank Wille