misc/187238: vm.pmap.pcid_enabled="1" causes Java to coredump in FBSD 10

Craig Rodrigues rodrigc at FreeBSD.org
Tue Mar 4 01:00:01 UTC 2014


>Number:         187238
>Category:       misc
>Synopsis:       vm.pmap.pcid_enabled="1" causes Java to coredump in FBSD 10
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 04 01:00:01 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Craig Rodrigues
>Release:        FreeBSD 10-STABLE
>Organization:
>Environment:
10.0-STABLE FreeBSD 10.0-STABLE #0 r261732: Tue Feb 11 04:35:10 UTC 201
>Description:
Hi,

As part of the Jenkins deployment in the FreeBSD cluster
the jenkins-admin team observed that when running Jenkins on FreeBSD 10,
the Java virtual machine from the openjdk6 or openjdk7 port
would coredump regularly.

See item #10 here:  https://wiki.freebsd.org/Jenkins

On the advice of Jung-uk Kim, I put the following in /boot/loader.conf:

vm.pmap.pcid_enabled="0"

and rebooted.

After that, the Java coredumping problems went away.

Can someone with VM expertise look into this problem and suggest a fix?

There are many reports of Java coredumping on FreeBSD 10, such as this
one:  http://lists.freebsd.org/pipermail/freebsd-java/2014-March/010606.html

It would be good to fix this, so that Java works "out of the box" on
FreeBSD 10.  It's not good when kernel tunables need to be set
so that Java can work. :(

Thanks.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list