JVM Crash on armv7 [resend ]

[Andrew Hughes]

----- Original Message -----
> Hi
> 
> On 02/05/14 05:49 AM, Daniel McGreal wrote:
> > Hi Severin,
> > Thanks for your reply. I don’t know about the Shark variant I’m
> > afraid, as this is an off-the-shelf device over which we don’t have
> > much control. Is there a way for me to find out for sure?
> > I did forget the logs, but then I sent them in a second message
> > immediately afterwards so not sure where they went, either way they’re
> > downloadable at http://djmfiles.s3.amazonaws.com/OpenJDK-Singal11.zip .
> >
> > In trying to reproduce this crash with simpler code, I have created
> > the following code, which provokes a crash too, but this time a Signal
> > 4. Reproduction code and logs are at
> > http://djmfiles.s3.amazonaws.com/OpenJDK-Signal4-Logs.zip and
> > http://djmfiles.s3.amazonaws.com/OpenJDK-Signal4.zip.
> >
> > Very best, Dan.
> >
> >
> > On 2 May 2014, at 10:32, Severin Gehwolf <sgehwolf at redhat.com
> > <mailto:sgehwolf at redhat.com>> wrote:
> >
> >> Hi Dan,
> >>
> >> On Thu, 2014-05-01 at 10:55 +0100, Daniel McGreal wrote:
> >>> Hi,
> >>> We write Java software thats run in embedded devices. On one such
> >>> device, our application reliably crashes after several hours of
> >>> operation. The typical activity of the application is forwarding
> >>> responses from the device (over a perpetual TCP connection) into an
> >>> AMQP exchange (again, perpetual TCP connection) and does not vary
> >>> greatly over time.
> >>>
> >>> Here are some details of the crash and its environment:
> >>>
> >>> #
> >>> # A fatal error has been detected by the Java Runtime Environment:
> >>> #
> >>> #  Internal Error (os_linux_zero.cpp:270), pid=24829, tid=1354962032
> >>> #  fatal error: caught unhandled signal 11
> >>> #
> >>> # JRE version: 6.0_24-b24
> >>> # Java VM: OpenJDK Zero VM (20.0-b12 mixed mode linux-arm )
> 
> This is an older version of the ARM32 asm jit jvm.
> If possible you should try a newer version as there have
> been bug fixes since 24.
> I'll take a look at the logs and the test.
> 

Indeed. If possible, you should try with the latest 1.13.3 release [0] or
point whoever maintains the device at that version. There will be no further
updates to the 1.12.x series.

[0] http://blog.fuseyism.com/index.php/2014/04/15/security-icedtea-1-13-3-for-openjdk-6-released/

> >>
> >> This seems to indicate that you are using the shark variant of zero. Can
> >> you confirm?
> >>
> >>> # Derivative: IcedTea6 1.12pre
> >>> # Distribution: Built for
> >>> # If you would like to submit a bug report, please include
> >>> # instructions how to reproduce the bug and visit:
> >>> # http://icedtea.classpath.org/bugzilla
> >>> #
> >>>
> >>> System details are:
> >>> OS:Linux
> >>> uname:Linux 2.6.32.8.ti-omap3-am3517-evm #55 PREEMPT Mon Mar 3
> >>> 17:00:29 IST 2014 armv7l
> >>> libc:glibc 2.11.1 NPTL 2.11.1
> >>> rlimit: STACK 8192k, CORE 2048k, NPROC 1996, NOFILE 1024, AS infinity
> >>> load average:0.00 0.00 0.00
> >>>
> >>> Three full crash reports are attached reports are included. Any help
> >>> with this issue would be greatly appreciated.
> >>
> >> It appears the mailing list software scrubbed your attachments or you
> >> forgot to attach them. Could you perhaps upload the logs somewhere?
> >>
> >> Cheers,
> >> Severin
> >
> Chris
> 
> 

-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07