I searched but can't seem to find any information on this issue. I have GhostBSD installed (24.10.1) which is based on FreeBSD 14.1-STABLE on a system with the AMD Ryzen 5 PRO 2400GE CPU. If I install Java (openjdk version 8 or 17), some operations on some projects cause my computer to hard lock up (mouse also freezes, I have to hold the power button for 5 seconds to shut down). This is very repeatable, for example, if I generate a project from https://start.vertx.io/ and then run "./mvnw exec:run", it starts downloading jar files and then hard locks up. On a different project, if I invoke the coffeescript compiler, it will hard lock up. However other projects do compile and run, so I am not sure exactly where the problem is. If I switch to linux and run the same project and operation, it works fine.
I should also mention that this CPU had an issue with both Linux and FreeBSD that was causing random hard lockups until I set the "idle=nomwait" on Linux and "machdep.idle_mwait=0" on FreeBSD. In both cases this fixed the issue completely, but initially I thought the java lockup in FreeBSD was related to this, but this only seems to affect Java in certain circumstances.
Things I have tried:
- copy project to different hard drive and try there
- run the mvnw command in a thin jail
- try different java version
- try more "cpu fixes" for the AMD CPU, e.g. "machdep.idle=hlt", "cpucontrol -m '0xc0011029|=0x2000' /dev/cpuctlXXX"
I was still getting the hard lockups, making debugging really difficult since the dmesg is reset when I reboot. Anyone else experience something similar? Any ideas on what I can try?
I should also mention that this CPU had an issue with both Linux and FreeBSD that was causing random hard lockups until I set the "idle=nomwait" on Linux and "machdep.idle_mwait=0" on FreeBSD. In both cases this fixed the issue completely, but initially I thought the java lockup in FreeBSD was related to this, but this only seems to affect Java in certain circumstances.
Things I have tried:
- copy project to different hard drive and try there
- run the mvnw command in a thin jail
- try different java version
- try more "cpu fixes" for the AMD CPU, e.g. "machdep.idle=hlt", "cpucontrol -m '0xc0011029|=0x2000' /dev/cpuctlXXX"
I was still getting the hard lockups, making debugging really difficult since the dmesg is reset when I reboot. Anyone else experience something similar? Any ideas on what I can try?