On Saturday, 21 August 1999 at 22:30:54 -0400, Luoqi Chen wrote:
I'm generating a core dump. Please note that as tara is my test machine, I use
"INVARIANT" "INVARIANT_SUPPORT". Should I remove them ?
It seems that from my reading of the code, the panic would not had happened
without
According to Greg Lehey:
In all likelihood, these options didn't "cause" the panic, they just
made another bug more visible. That's what they're there for.
That's what I'm thinking but compiling NFS into the kernel "fixed" my
panic. The weird part is that I'm still using INVARIANT. I don't
On Sun, Aug 22, 1999 at 10:24:33PM +0200, Ollivier Robert wrote:
That's what I'm thinking but compiling NFS into the kernel "fixed" my
panic. The weird part is that I'm still using INVARIANT. I don't see why the
condition is not met when compiling all these together and is when using the
kld.
Hello,
I just got a panic when trying to play with NFSv3. The system is a dual
PentiumPro system, running CURRENT/SMP. I use NFS as a kld.
The FS on keltia is exported as:
/z -alldirs -maproot=0 tara
And mounted on tara with
keltia:/z /spare rw,nfsv30 0
I tried making a
:Hello,
:
:I just got a panic when trying to play with NFSv3. The system is a dual
:PentiumPro system, running CURRENT/SMP. I use NFS as a kld.
The very first thing I would do is compile NFS into the kernel and not
use it as a kld. Then see if you can repeat the problem.
I'm generating a core dump. Please note that as tara is my test machine, I use
"INVARIANT" "INVARIANT_SUPPORT". Should I remove them ?
It seems that from my reading of the code, the panic would not had happened
without INVARIANT.
It is these options that caused the panic, you either
