From daniel at redbite.com Thu May 1 09:55:08 2014 From: daniel at redbite.com (Daniel McGreal) Date: Thu, 1 May 2014 10:55:08 +0100 Subject: JVM Crash on armv7 Message-ID: <95E2B03B-48AD-46F5-94CB-BF1601E6436F@redbite.com> 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 ) # 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. Many thanks, Dan. From sgehwolf at redhat.com Fri May 2 09:32:00 2014 From: sgehwolf at redhat.com (Severin Gehwolf) Date: Fri, 02 May 2014 11:32:00 +0200 Subject: JVM Crash on armv7 In-Reply-To: <95E2B03B-48AD-46F5-94CB-BF1601E6436F@redbite.com> References: <95E2B03B-48AD-46F5-94CB-BF1601E6436F@redbite.com> Message-ID: <1399023120.3248.15.camel@localhost.localdomain> 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 From daniel at redbite.com Fri May 2 09:49:28 2014 From: daniel at redbite.com (Daniel McGreal) Date: Fri, 2 May 2014 10:49:28 +0100 Subject: JVM Crash on armv7 In-Reply-To: <1399023120.3248.15.camel@localhost.localdomain> References: <95E2B03B-48AD-46F5-94CB-BF1601E6436F@redbite.com> <1399023120.3248.15.camel@localhost.localdomain> Message-ID: <3B75A3BA-886A-4605-809D-01C3C5348E99@redbite.com> 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ChrisPhi at LGonQn.Org Fri May 2 12:39:43 2014 From: ChrisPhi at LGonQn.Org (Chris Phillips @ T O) Date: Fri, 02 May 2014 08:39:43 -0400 Subject: JVM Crash on armv7 [resend ] In-Reply-To: <3B75A3BA-886A-4605-809D-01C3C5348E99@redbite.com> References: <95E2B03B-48AD-46F5-94CB-BF1601E6436F@redbite.com> <1399023120.3248.15.camel@localhost.localdomain> <3B75A3BA-886A-4605-809D-01C3C5348E99@redbite.com> Message-ID: <5363920F.2050408@LGonQn.Org> 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 > 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. >> >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnu.andrew at redhat.com Fri May 16 21:00:14 2014 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Fri, 16 May 2014 17:00:14 -0400 (EDT) Subject: JVM Crash on armv7 [resend ] In-Reply-To: <5363920F.2050408@LGonQn.Org> References: <95E2B03B-48AD-46F5-94CB-BF1601E6436F@redbite.com> <1399023120.3248.15.camel@localhost.localdomain> <3B75A3BA-886A-4605-809D-01C3C5348E99@redbite.com> <5363920F.2050408@LGonQn.Org> Message-ID: <1810099942.7101149.1400274014226.JavaMail.zimbra@redhat.com> ----- 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 > > 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