RE: Evergreen: RuntimeError: Java failed with #<Process::Status: pid 10014 SIGIOT (signal 6)>

Martin Dorey

unread,

Apr 24, 2014, 2:01:27 PM4/24/14

to Mark Kaminsky, evergre...@googlegroups.com

With that Outlook-style error message, Google really is trying to become Microsoft. I think the right reason was:

Ø * You may need to join the group before receiving permission to post.

I've changed the +group so that anyone can post. Perhaps that will result in a torrent of spam and have to be changed again. I found nothing particularly compelling in /tmp/edit.log.9961

martind@balance:~$ cat /tmp/edit.log.9961

2014-04-22T14:40:07.485-0700 Evergreen: Java 1.6.0_26 (VM 20.1-b02, runtime 1.6.0_26-b03)

…

2014-04-24T09:59:56.512-0700 Evergreen: Opening "/home/mkaminsky/work/bat/2/mgmt/atlas_client/src/com/bluearc/baservice/snapshotmgmntprovider/CreateSnapshotResponse.java"

2014-04-24T09:59:57.634-0700 Evergreen: Opening "/home/mkaminsky/work/bat/2/mgmt/atlas_client/src/com/bluearc/baservice/SnapshotMgmntProviderPortType.java"

martind@balance:~$

It's preserved in /home/martind/.terminator/logs/2014-04-24T105902.431-0700-%2Fbin%2Fbash.txt in the unlikely event that it does turn out to be interesting.

From: Mark Kaminsky
Sent: Thursday, April 24, 2014 10:54
To: Martin Dorey
Subject: RE: Evergreen: RuntimeError: Java failed with #<Process::Status: pid 10014 SIGIOT (signal 6)>

Google Groups wrote:

Hello mark.k...@hds.com,

We're writing to let you know that the group you tried to contact (evergreen-users) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post:

* You might have spelled or formatted the group name incorrectly.

* The owner of the group may have removed this group.

* You may need to join the group before receiving permission to post.

* This group may not be open to posting.

If you have questions related to this or any other Google Group, visit the Help Center at http://groups.google.com/support/.

Thanks,

Google Groups

and then quoted the beginning of the message (but with some stuff which is normally hidden, so here it is):

X-Received: by 10.42.235.206 with SMTP id kh14mr1506690icb.30.1398359854873;

Thu, 24 Apr 2014 10:17:34 -0700 (PDT)

Return-Path: <mark.k...@hds.com>

Received: from usindpps04.hds.com (usindpps04.hds.com. [207.126.252.17])

by gmr-mx.google.com with ESMTPS id h6si775860iga.0.2014.04.24.10.17.34

for <evergre...@googlegroups.com>

(version=TLSv1 cipher=RC4-SHA bits=128/128);

Thu, 24 Apr 2014 10:17:34 -0700 (PDT)

Received-SPF: pass (google.com: domain of mark.k...@hds.com designates 207.126.252.17 as permitted sender) client-ip=207.126.252.17;

Authentication-Results: gmr-mx.google.com;

spf=pass (google.com: domain of mark.k...@hds.com designates 207.126.252.17 as permitted sender) smtp.mail=mark.k...@hds.com;

dkim=pass header.i=@hds.com

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hds.com; h=from : to : subject :

date : message-id : content-type : mime-version; s=mail1;

bh=x9w+tuA4prXRMfIgX2tc638Ssnj9WHNdjbE+c1H84vI=;

b=QhvnZv0ASiFCJKXb9xumQCHZ7q8Qx2eFFMySwFMCQzzmf9pXPBfKFvXBEUOEyCWpOeOZ

zDClNB1t9E9hnajHuK1Ptvr44nK2zvn5qJtZoxt+MnjKzCKoUxwaxTTwtjbhTXE57DBs

z+oP/nFSuwDsKh41/na0o7x6R9ElKpLL3U2WuZ3dHvj1fFS07eIiud1QidWbDpHBeCGX

+MaWv7BHWUTxAXkhMwmWkqFmsHymPLa1iuiDQkLQh49OR1Qb9NVKBB7RxKvWoFa/7iPU

7vlcReoF3LuT/yVRFpjxOtziShlJvPbnt/qaoB3gCDQYFRBZaW+SjA0JgXbQ+bbN2zLE XQ==

Received: from usindmail02.hds.com (usindmail02 [207.126.252.21])

by usindpps04.hds.com (8.14.5/8.14.5) with ESMTP id s3OHGvgi007248

for <evergre...@googlegroups.com>; Thu, 24 Apr 2014 13:16:57 -0400

Received: from USINDEHT101.corp.hds.com (usindnetf5d-vlan47float.corp.hds.com [10.74.73.11])

by usindmail02.hds.com (8.14.1/8.14.1) with ESMTP id s3OHGvrp011492

for <evergre...@googlegroups.com>; Thu, 24 Apr 2014 13:16:57 -0400 (EDT)

Received: from USINDEM101.corp.hds.com ([fe80::84ed:ede8:5f0b:20ac]) by

USINDEHT101.corp.hds.com ([fe80::59e1:7859:afa6:e63d%12]) with mapi id

14.03.0123.003; Thu, 24 Apr 2014 13:17:32 -0400

From: Mark Kaminsky <mark.k...@hds.com>

To: "evergre...@googlegroups.com" <evergre...@googlegroups.com>

Subject: Evergreen: RuntimeError: Java failed with #<Process::Status: pid

10014 SIGIOT (signal 6)>

Thread-Topic: Evergreen: RuntimeError: Java failed with #<Process::Status:

pid 10014 SIGIOT (signal 6)>

Thread-Index: Ac9f4ETJ/eWA2Rx1QnS9N/KX/Uj3kg==

Date: Thu, 24 Apr 2014 17:17:32 +0000

Message-ID: <63FEF7EB23F0E74DA3ED...@USINDEM101.corp.hds.com>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-originating-ip: [10.74.73.11]

Content-Type: multipart/alternative;

boundary="_000_63FEF7EB23F0E74DA3ED7E669A37765860C8C0FDUSINDEM101corph_"

MIME-Version: 1.0

X-Proofpoint-SPF-Result: pass

X-Proofpoint-SPF-Record: v=spf1 mx ip4:207.126.244.0/26 ip4:207.126.252.0/25 include:mktomail.com

include:cloud.hds.com ~all

X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000

definitions=2014-04-24_05:2014-04-24,2014-04-24,1970-01-01 signatures=0

X-Proofpoint-Spam-Details: rule=notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0

phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx

scancount=1 engine=7.0.1-1402240000 definitions=main-1404240278

From: Martin Dorey
Sent: Thursday, 24 April, 2014 10:48
To: Mark Kaminsky
Subject: RE: Evergreen: RuntimeError: Java failed with #<Process::Status: pid 10014 SIGIOT (signal 6)>

Ø Google Groups bounced it.

Saying what?

From: Mark Kaminsky
Sent: Thursday, April 24, 2014 10:21
To: Martin Dorey
Subject: FW: Evergreen: RuntimeError: Java failed with #<Process::Status: pid 10014 SIGIOT (signal 6)>

I sent the message as below, and Google Groups bounced it.

Mark

From: Mark Kaminsky
Sent: Thursday, 24 April, 2014 10:18
To: 'evergre...@googlegroups.com'
Subject: Evergreen: RuntimeError: Java failed with #<Process::Status: pid 10014 SIGIOT (signal 6)>

I had a number of files open in each of a number of tabs. I selected a file (I think I double-clicked on the title to expand it), and found that I was not looking at the latest version. So I right-clicked, and selected "Revert to saved", and it immediately crashed, giving me a window with the following data.

Note that I am running Debian Wheezy, having recently upgraded from Squeeze.

Mark

=======================================================================================================

Uncaught exception

An error occurred in Evergreen:

Exception RuntimeError: Java failed with #<Process::Status: pid 10014 SIGIOT (signal 6)>

Please send us the contents of the application log, from /tmp/edit.log.9961.

An idea of what you were doing when Java exited might be useful.

Command line was:

at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/invoke-java.rb:518:in `launch'

at /usr/bin/evergreen:105:in `launch0'

at /usr/bin/evergreen:20:in `block in launch'

at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:146:in `call'

at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:146:in `initialize'

at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:158:in `new'

at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:158:in `report_exceptions'

at /usr/bin/evergreen:20:in `launch'

at /usr/bin/evergreen:113:in `<main>'

Package 27.26.6938

Revision 6938 (6938)

Built 2014-04-22T09:20:55-07:00

Please mail this error message to evergre...@googlegroups.com.

Mark Kaminsky

unread,

Apr 24, 2014, 2:12:14 PM4/24/14

to Martin Dorey, evergre...@googlegroups.com

It is unlikely that edit.log.9961 will be of any use, as it ends long before the point where the problem happened: I was actually looking at users.txt when it crashed.

Mark

Martin Dorey

unread,

Apr 24, 2014, 2:26:27 PM4/24/14

to Mark Kaminsky, evergre...@googlegroups.com

This looks like roughly the right time:

-rw-rw-r-- 1 mkaminsky software 80793 Apr 24 10:10 /home/mkaminsky/hs_err_pid10014.log

#

# A fatal error has been detected by the Java Runtime Environment:

#

# SIGSEGV (0xb) at pc=0x00007f6fd67cff64, pid=10014, tid=140118295127808

#

# JRE version: 6.0_26-b03

# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# C [libnvidia-glcore.so.304.88+0x12def64] _nv012glcore+0x3b94

#

# If you would like to submit a bug report, please visit:

# http://java.sun.com/webapps/bugreport/crash.jsp

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

#

…

Register to memory mapping:

RAX=0x0000000000000000 is an unknown value

RBX=0x0000000000000000 is an unknown value

RCX=0x00007f6fb9319f90 is an unknown value

RDX=0x0000000000000000 is an unknown value

RSP=0x00007f6fd534f780 is pointing into the stack for thread: 0x0000000040a00000

RBP=0x0000000000000000 is an unknown value

RSI=0x0000000000000000 is an unknown value

RDI=0x00007f6fb9319f90 is an unknown value

R8 =0x00007f6fd7de5860: <offset 0x307860> in /usr/lib/x86_64-linux-gnu/libGL.so.1 at 0x00007f6fd7ade000

R9 =0x000000000000273b is an unknown value

R10=0x0000000000000004 is an unknown value

R11=0x0000000000000000 is an unknown value

R12=0x00007f6fd4f69010 is an unknown value

R13=0x00007f6fd78d9be0: _nv015glcore+0 in /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.304.88 at 0x00007f6fd54f1000

R14=0x00007f6fd78c2040: _nv017glcore+0 in /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.304.88 at 0x00007f6fd54f1000

R15=0x00007f6fd7880e80: _nv020glcore+0 in /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.304.88 at 0x00007f6fd54f1000

Stack: [0x00007f6fd5252000,0x00007f6fd5353000], sp=0x00007f6fd534f780, free space=1013k

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)

C [libnvidia-glcore.so.304.88+0x12def64] _nv012glcore+0x3b94

[error occurred during error reporting (printing native stack), id 0xb]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)

J sun.java2d.opengl.OGLRenderQueue.flushBuffer(JI)V

J sun.java2d.opengl.OGLRenderQueue.flushBuffer()V

J sun.java2d.opengl.OGLRenderQueue$QueueFlusher.run()V

v ~StubRoutines::call_stub

martind@balance:~$ dpkg -S /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.304.88

libgl1-nvidia-glx:amd64: /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.304.88

martind@balance:~$ dpkg --status libgl1-nvidia-glx

…

Version: 304.88-1+deb7u1

I contrived to get:

Version: 331.49-1

… installed on swiftboat, from wheezy-backports, in the vain hope that it might sort out either of the two problems with Terminator on Wheezy: the "grains of sand" problem with drag-scrolling right, that seems convincingly diagnosed as an xserver-xorg-core bug and/or the "ghost text" problem on the right hand monitor. The lack of any other bug reports on the interwebs for the ghost text problem, though you, bcc:Neil, bcc:Alan and I all see it, conspires with the above crash to make me think no-one is using sun.java.opengl=true. Now admittedly, we're using a version of Java from before the Oracle acquisition, though that's only because every newer version we've tried has crashed in some circumstance that we care about. I'm thinking it's time to turn sun.java2d.opengl back off and live with the "grains of sand" problem. Any objection, Neil?

Neil Berrington

unread,

Apr 24, 2014, 3:02:24 PM4/24/14

to Martin Dorey, Mark Kaminsky, evergre...@googlegroups.com

Ø sun.java2d.opengl back off and live with the "grains of sand" problem. Any objection, Neil?

I find the grain of sands issue very annoying – the logs I have to review require frequent horizontal scrolling.

Could you make it an option that only I set? J

--

Neil.

Martin Dorey

unread,

Apr 24, 2014, 3:36:25 PM4/24/14

to evergre...@googlegroups.com, Martin Dorey, Mark Kaminsky

This ought to do the trick:

export _JAVA_OPTIONS='-Dsun.java2d.opengl=true'

Sounds like a go...

From: Neil Berrington <neil.be...@hds.com>

Sender: evergre...@googlegroups.com

Date: Thu, 24 Apr 2014 19:02:24 +0000

To: Martin Dorey<Martin...@hds.com>; Mark Kaminsky<mark.k...@hds.com>

ReplyTo: evergre...@googlegroups.com

Cc: evergre...@googlegroups.com<evergre...@googlegroups.com>

--
You received this message because you are subscribed to the Google Groups "evergreen-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to evergreen-use...@googlegroups.com.
To post to this group, send email to evergre...@googlegroups.com.
Visit this group at http://groups.google.com/group/evergreen-users.
For more options, visit https://groups.google.com/d/optout.

Elliott Hughes

unread,

Apr 25, 2014, 10:31:32 PM4/25/14

to evergre...@googlegroups.com, Martin Dorey, Mark Kaminsky

would everyone be better off if we just removed that line? i've had to
remove it locally to prevent weirdness on my work laptop's Haswell
integrated graphics (HD4400?). do we still have any cases where the
VM's built-in white/blacklisting chooses wrong?

--
Elliott Hughes - http://www.jessies.org/~enh/

Martin Dorey

unread,

Apr 25, 2014, 11:31:34 PM4/25/14

to evergre...@googlegroups.com, Martin Dorey, Mark Kaminsky

> would everyone be better off if we just removed that line?

No, per Neil below, but I did it anyway yesterday.

> do we still have any cases where the
VM's built-in white/blacklisting chooses wrong?

Eh? The Oracle docs say it's always off by default.

Reply all

Reply to author

Forward