Adrenalin wrote:
Rick thank you for the answer.
I'll "put my heart into the teeth" and will try to go for the stable.
This is kind of critical I guess, I think it should really go to the
release. It's the first time I got into a such a nasty bug with freebsd.
Unfortunately the release has 'left the station', however I guess we
might be able to add a pointer in the erratum document.
I'm not sure who is in charge of that doc. (re?)
On Wed, Mar 10, 2010 at 3:44 AM, Rick Macklem <rmack...@uoguelph.ca> wrote:
On Wed, 10 Mar 2010, Adrenalin wrote:
Hi, I would like to know if this bug has been fixed in the FreeBSD 8
Release
since I got it 3 times already on a busy box that use heavily NFS (with
lots
of files).
Unfortunately my processes are not compiled with debug symbols(so I cannot
get an backtrace), but I've got all the php-cgi stuck in the "rpccon"
state
just like described here, I cannot kill them and I cannot cleanly reboot,
manual restart is required.
I suspect that what you are seeing is fixed by:
http://people.freebsd.org/~rmacklem/patches/freebsd8-clntvc.patch<http://people.freebsd.org/%7Ermacklem/patches/freebsd8-clntvc.patch>
It is in head and stable/8, but did not make the FreeBSD8.0 release.
I believe that the patch is safe to add to a FreeBSD8.0 release kernel.
rick
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
