Matthew Dillon wrote: > > : > :I've been seeng lockups in 3.0 where as is in piperd, > :but the stack trace has always looked as if the problem was in soft > :updates or the syncer daemon.. > : > > It's quite possible for as to be in 'piperd' when some other unassociated > crash occurs, since it is typically waiting for input from cc1. What > is not typical, however, is if as is stuck 'piperd' and the other end of > the pipe has been closed. > > The particular piperd bug I found cannot crash the system - at worst it > will block a process forever. And you can still kill the process. > > 3.0's lockups could be very well due to a number of low-memory interlock > situations that typically occur when heavy paging is going on, if that is > how you are running 3.0. I suspect it is too late to get my getpbuf() > changes into 3.1, which might mitigate that somewhat.
the lockups are in a 2 day old SNAP of 3.x To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
