Date: Wed, 10 Mar 2010 10:31:33 -0800 From: Julian Elischer <julian@elischer.org> To: Adrenalin <adrenalinup@gmail.com> Cc: Doug Rabson <dfr@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca>, current@freebsd.org, freebsd-current@freebsd.org, pav@freebsd.org, Kip Macy <kmacy@freebsd.org> Subject: Re: hang in rpccon from interrupting NFS operations (Re: pointyhat panic) Message-ID: <4B97E585.20106@elischer.org> In-Reply-To: <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com> References: <1242075474.72992.118.camel@hood.oook.cz> <3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com> <20090616073353.GZ33280@droso.net> <200906160812.04284.jhb@freebsd.org> <4A3E234F.6050403@FreeBSD.org> <Pine.GSO.4.63.0906212119310.2430@muncher.cs.uoguelph.ca> <f027bef41003091519h4e2b0827i28b95cc55701076c@mail.gmail.com> <Pine.GSO.4.63.1003092141560.12283@muncher.cs.uoguelph.ca> <f027bef41003100338m57f205f6k1ed93acf80e32a6a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <rmacklem@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-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B97E585.20106>