OpenJDK compile hangs on PPC64
Severin Gehwolf
sgehwolf at redhat.com
Fri Oct 24 09:38:24 UTC 2014
Hi Volker,
On Fri, 2014-10-24 at 11:14 +0200, Volker Simonis wrote:
> Hi Severin,
>
> as a quick workaround, you could download the IBM J9 from
> http://www.ibm.com/developerworks/java/jdk/beta/ to build a new
> version of OpenJDK 8 from scratch. That shouldn't have any problems.
Oh, that's OK. I'd rather debug the issue :)
> If that still hangs, could you please provide some Java stack traces
> (i.e. by using jstack or by sending the Java process a SIGQUIT
> signal).
Sure, once I see it happening again I'll try that.
Cheers,
Severin
> Regards,
> Volker
>
>
> On Thu, Oct 23, 2014 at 3:45 PM, Severin Gehwolf <sgehwolf at redhat.com> wrote:
> > Hi,
> >
> > I've compiled the OpenJDK Zero variant on PPC 64 (BE) a couple of times.
> > Out of a total of say 6 compiles it "hang" twice. I think it got stuck
> > somewhere compiling JDK classes.
> >
> > The boot JDK which I've used for building is OpenJDK 8 with the PPC64
> > JIT. The host OS is RHEL-7. I see the following showing up in dmesg
> > multiple times:
> >
> > [188362.213095] CPU: 16 PID: 10678 Comm: java Not tainted 3.10.0-123.el7.ppc64 #1
> > [188362.213100] Call Trace:
> > [188362.213105] [c00000006297ae40] [c0000000000166e8] .show_stack+0x78/0x320 (unreliable)
> > [188362.213113] [c00000006297af00] [c0000000008c6618] .dump_stack+0x28/0x3c
> > [188362.213119] [c00000006297af70] [c0000000001aa308] .rcu_check_callbacks+0x488/0x990
> > [188362.213126] [c00000006297b0b0] [c0000000000c9334] .update_process_times+0x54/0xa0
> > [188362.213132] [c00000006297b140] [c000000000144920] .tick_sched_timer+0x80/0x150
> > [188362.213138] [c00000006297b1e0] [c0000000000f177c] .__run_hrtimer+0xac/0x370
> > [188362.213144] [c00000006297b280] [c0000000000f28b8] .hrtimer_interrupt+0x138/0x320
> > [188362.213150] [c00000006297b390] [c00000000001f130] .timer_interrupt+0x120/0x2f0
> > [188362.213156] [c00000006297b440] [c000000000002614] decrementer_common+0x114/0x180
> > [188362.213162] --- Exception: 901 at .arch_local_irq_restore+0xf0/0x150
> > [188362.213162] LR = .arch_local_irq_restore+0xf0/0x150
> > [188362.213169] [c00000006297b730] [c0000000001488a0] .get_futex_key+0x310/0x3d0 (unreliable)
> > [188362.213176] [c00000006297b7a0] [c000000000051e14] .get_user_pages_fast+0x2a4/0x440
> > [188362.213181] [c00000006297b8a0] [c0000000001486e4] .get_futex_key+0x154/0x3d0
> > [188362.213187] [c00000006297b950] [c000000000149460] .futex_wake+0x50/0x1c0
> > [188362.213192] [c00000006297ba10] [c00000000014ac84] .do_futex+0x234/0xec0
> > [188362.213197] [c00000006297bb50] [c00000000014ba2c] .SyS_futex+0x11c/0x1d0
> > [188362.213202] [c00000006297bc20] [c0000000000a8dc0] .mm_release+0x130/0x190
> > [188362.213208] [c00000006297bca0] [c0000000000b7000] .do_exit+0x190/0xb60
> > [188362.213213] [c00000006297bda0] [c0000000000b7b58] .SyS_exit_group+0x48/0xf0
> > [188362.213219] [c00000006297be30] [c000000000009e7c] syscall_exit+0x0/0x7c
> >
> > PID 10678 was the java (javac) process that got stuck.
> >
> > Does this ring a bell for anyone here?
> >
> > Thanks,
> > Severin
> >
More information about the ppc-aix-port-dev
mailing list