Date: Tue, 2 Nov 2004 23:56:06 -0500 From: Jason Harmening <gte990t@mail.gatech.edu> To: freebsd-threads@freebsd.org Subject: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state Message-ID: <200411022356.06257.gte990t@mail.gatech.edu>
next in thread | raw e-mail | index | archive | help
The following message has already been posted to the freebsd-current mailing list. Please note that the unkillable process problem originally reported in 5.3-RC1 is NOT isolated to gdb/kde, and seems to occur with OpenOffice under heavy loads, especially with java running at the same time. Furthermore, 5.3-RC2 does not fix the problem. Several other people have chimed in saying they have the same problem, and I think it would be a BAD idea to release 5.3 without fixing this. I don't have the kernel expertise to directly delve into the problem, but I do have a reasonable amount of systems-level development/troubleshooting experience, so I would be more than willing to help with debugging/diagnosis if someone could point me in the right direction. Thanks, Jason Harmening ---------- Forwarded Message ---------- Subject: Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state Date: Tuesday 02 November 2004 11:45 From: Jason Harmening <gte990t@mail.gatech.edu> To: Alex Dupre <sysadmin@alexdupre.com> Cc: freebsd-current@freebsd.org On Tuesday 02 November 2004 09:00, you wrote: > Jason Harmening wrote: > > I just upgraded to 5.3-RC2, and I'm still running into the problem where > > processes will hang in an unkillable state. In particular, this happens > > for me with OpenOffice under a heavy load. 'ps' reports the state as > > 'TL' and 'top' reports the state as STOP. Neither kill -CONT nor kill > > -KILL will work. > > Same here. With OpenOffice and Java under high load. Yes--I forgot to mention it, but my OpenOffice problems have all seemed to happen at the same time I have some instance of the JVM (native 1.4.2) running. OpenOffice will start up, reach almost the end of its splash screen, and then simply hang in an unkillable state. This has a very sinister side effect in that, when the system does its daily security run (I'm also assuming it tries to clean up useless processes), and there's such an "unkillable" process, the entire system will hang. It's not an abrupt freeze, but it's a gradual "bogging down" that ultimately requires a hard reset. The same thing happens during a shutdown/reboot with an unkillable process, but luckily the system manages to sync the disk before hanging. -------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411022356.06257.gte990t>