Juli Mallett wrote: > * De: "M. Warner Losh" <[EMAIL PROTECTED]> [ Data: 2002-09-30 ] > [ Subjecte: Re: World broken at libkvm ] > > In message: <[EMAIL PROTECTED]> > > walt <[EMAIL PROTECTED]> writes: > > : cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c > > : /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o > > : /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': > > : /usr/src/lib/libkvm/kvm_proc.c:201: structure has no member named `p_sigl ist' > > > > This has been fixed. But there's other breakages in the kernel that > > are being worked on. > > And now fixed. All we have to look out for now is someone doing something > that exposes some sort of functional difference, but I don't anticipate it.
Have you dealt with the 'could sleep' stuff with witness turned on? These are *guaranteed* panics if the system is low on memory at that given instant. (Witness doesn't cause the problems, it reports fundamental problems that are already there. The system will panic regardless of whether witness is there or not.) I suggest you turn WITNESS on, and stress the system. If you get *new* 'could sleep' stuff or other lock order problems, then there are still significant regressions to be fixed. The last thing we need during the 'please stabilize 5.0' drive is newly added problems. If other folks are seeing new ones, please report them here (not to me, I already get too much email :-]). Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message