Red Hat Bugzilla – Bug 179228
kernels > 2.6.15-1.1826.2.10_FC5 cause java/mono apps to freeze during GC
Last modified: 2007-11-30 17:11:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
Eclipse, RSSOwl, Azureus, chainsaw, etc all run fine on 2.6.15-1.1826.2.10_FC5 with java-1.4.2-gcj-compat, but they all freeze during startup on newer kernels.
It looks like this is happening during GC. I gathered some stack traces from an eclipse process and will I'll upload in a minute.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 123840 [details]
stack traces from gdb
*** Bug 179002 has been marked as a duplicate of this bug. ***
I am seeing this as well. It has bitten me most when trying to update.
gcj-dbtool get stuck and yum sits there waiting on it. Running "for((;;)); do
killall gcj-dbtool; sleep 1; done" allows yum to get through updating, but I'm
sure my java stuff is a mess. I think I'm also seeing this affect mono apps,
like beagle. Running beagle-search just sits there. Attaching to it with gdb
0x00002ba878af615d in sem_wait () from /lib64/libpthread.so.0
(gdb) info threads
3 Thread 1073822048 (LWP 3674) 0x00002ba878af7461 in __nanosleep_nocancel ()
2 Thread 1075988832 (LWP 3675) 0x00002ba878af46f7 in
pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
1 Thread 48002585361616 (LWP 3673) 0x00002ba878af615d in sem_wait () from
Let me know what I can do to help with debugging this problem.
(In reply to comment #3)
> I think I'm also seeing this affect mono apps,
> like beagle.
This makes sense. gcj and mono use the same GC implementation, and the problem
shows up when the collector tries to stop all threads so it can take care of
Changing arch=all, remarkably similar wedgie occures on i386 during garbage collect.
Actually I'm pretty sure this is x86_64 arch specific. Something is wrong with
signals/sigsuspend. Removing the following patches from kernel-2.6.15-1.1914_FC5
fixes it for me:
Just replicated with 2.6.15-1.1826.2.10_FC5 #1 Wed Jan 11 18:12:42 EST 2006 i686
i686 i386 GNU/Linux on i386 machine using Frysk.
(In reply to comment #6)
> Actually I'm pretty sure this is x86_64 arch specific. Something is wrong with
> signals/sigsuspend. Removing the following patches from kernel-2.6.15-1.1914_FC5
> fixes it for me:
> Patch206: linux-2.6-x86_64-tif-restore-sigmask.patch
> Patch207: linux-2.6-x86_64-generic-sigsuspend.patch
> Patch208: linux-2.6-x86_64-add-ppoll-pselect.patch
What did those pathces try to fix ? I mean could they temp. be disabled in the
next rawhide kernels ?
*** Bug 177820 has been marked as a duplicate of this bug. ***
*** Bug 179304 has been marked as a duplicate of this bug. ***
*** Bug 177592 has been marked as a duplicate of this bug. ***
*** Bug 177703 has been marked as a duplicate of this bug. ***
*** Bug 180551 has been marked as a duplicate of this bug. ***
There seems to be conflicting reports about whether this is x86_64 only or not.
Can someone confirm whether it does happen on i386 and ppc?
For explanation of these patches, see http://lwn.net/Articles/164892/
The PowerPC code path is the one I handled myself; i386 was done by dhowells and
then x86_64 by Andi Kleen.
I was just able to 'yum update' from a three-day-old rawhide to current, on
ppc64 (with 1.1909 kernel). That updated a few Java packages, including eclipse,
and will definitely have involved running gcj-dbtool. There were no problems --
should I infer from this that PPC isn't affected, or is there a better
reproducer I should be trying? A smaller test case would definitely be good.
Could this be related to bug #180567?
There's no reason to belive the frysk bug and the x86_64 java bug are in any way
connected. Let's keep them separate.
*** Bug 180926 has been marked as a duplicate of this bug. ***
(In reply to comment #14)
> There seems to be conflicting reports about whether this is x86_64 only or not.
> Can someone confirm whether it does happen on i386 and ppc?
This does not effect i386. The i386/frysk hang is a separate issue. So far I have been unable to install FC5
on a PPC machine to test there.
Yes, I think this is very likely the same as bug #180567
It's fine on PowerPC -- but tell me separately about the problems you had
installing FC5. I did a rawhide install to a PPC64 machine only a couple of days
ago, and it was mostly OK.
After applying the updates today (Feb 13 2006), Mono apps work again. Kernel
version is now 2.6.15-1.1939_FC5 x86_64.
Yeah, Dave removed the patches noted in comment 6.
I can confirm that this is fixed in 2.6.15-1.1939_FC5. I'm closing this one: the
underlying kernel problem is also being tracked in bug #180567.
*** Bug 179978 has been marked as a duplicate of this bug. ***