[prev in list] [next in list] [prev in thread] [next in thread]
List: openjdk-zero-dev
Subject: Re: JVM Crash on armv7
From: Daniel McGreal <daniel () redbite ! com>
Date: 2014-05-02 9:49:28
Message-ID: 3B75A3BA-886A-4605-809D-01C3C5348E99 () redbite ! com
[Download RAW message or body]
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@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 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
[Attachment #3 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html \
charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: \
space; -webkit-line-break: after-white-space;">Hi Severin,<div>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?</div><div>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 <a href="http://djmfiles.s3.amazonaws.com/OpenJDK-Singal11.zip">http://djmfiles.s3.amazonaws.com/OpenJDK-Singal11.zip</a> \
.</div><div><br></div><div>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 <a \
href="http://djmfiles.s3.amazonaws.com/OpenJDK-Signal4-Logs.zip">http://djmfiles.s3.amazonaws.com/OpenJDK-Signal4-Logs.zip</a> \
and <a href="http://djmfiles.s3.amazonaws.com/OpenJDK-Signal4.zip">http://djmfiles.s3.amazonaws.com/OpenJDK-Signal4.zip</a>.</div><div><br></div><div>Very \
best, Dan.</div><div><br></div><div><br></div><div><div><div>On 2 May 2014, at 10:32, \
Severin Gehwolf <<a href="mailto:sgehwolf@redhat.com">sgehwolf@redhat.com</a>> \
wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div \
style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: \
normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: \
start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; \
word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi Dan,<br><br>On Thu, 2014-05-01 \
at 10:55 +0100, Daniel McGreal wrote:<br><blockquote type="cite">Hi,<br>We write Java \
software thats run in embedded devices. On one such<br>device, our application \
reliably crashes after several hours of<br>operation. The typical activity of the \
application is forwarding<br>responses from the device (over a perpetual TCP \
connection) into an<br>AMQP exchange (again, perpetual TCP connection) and does not \
vary<br>greatly over time.<br><br>Here are some details of the crash and its \
environment:<br><br>#<br># A fatal error has been detected by the Java Runtime \
Environment:<br>#<br># Internal Error (os_linux_zero.cpp:270), pid=24829, \
tid=1354962032<br># fatal error: caught unhandled signal 11<br>#<br># JRE \
version: 6.0_24-b24<br># Java VM: OpenJDK Zero VM (20.0-b12 mixed mode linux-arm \
)<br></blockquote><br>This seems to indicate that you are using the shark variant of \
zero. Can<br>you confirm?<br><br><blockquote type="cite"># Derivative: IcedTea6 \
1.12pre<br># Distribution: Built for<span \
class="Apple-converted-space"> </span><br># If you would like to submit a bug \
report, please include<br># instructions how to reproduce the bug and visit:<br># \
<a href="http://icedtea.classpath.org/bugzilla">http://icedtea.classpath.org/bugzilla</a><br>#<br><br>System \
details are:<br>OS:Linux<br>uname:Linux 2.6.32.8.ti-omap3-am3517-evm #55 PREEMPT Mon \
Mar 3 17:00:29 IST 2014 armv7l<br>libc:glibc 2.11.1 NPTL 2.11.1<span \
class="Apple-converted-space"> </span><br>rlimit: STACK 8192k, CORE 2048k, NPROC \
1996, NOFILE 1024, AS infinity<br>load average:0.00 0.00 0.00<br><br>Three full crash \
reports are attached reports are included. Any help<br>with this issue would be \
greatly appreciated.<br></blockquote><br>It appears the mailing list software \
scrubbed your attachments or you<br>forgot to attach them. Could you perhaps upload \
the logs somewhere?<br><br>Cheers,<br>Severin</div></blockquote></div><br></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic