a...@freebsd.org, freebsd-j...@freebsd.org
Subject: Re: latest openjdk7 triggers kernel panic
Message-ID:
CAGE5yCrRfunbFhGrKgZHAXvOmPb6tUR2d_TEuju=snkokhd...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Dec 26, 2013 at 7:39 AM, Antoine Brodin anto...@freebsd.org wrote
I am running FreeBSD based on the head from a few weeks ago, amd64.
It seems that after a recent upgrade of openjdk7 I consistently get a kernel
panic when a java process starts:
panic: Bad entry start/end for new stack entry
KDB: stack backtrace:
db_trace_self_wrapper() at 0x803adc9b =
On Thu, Dec 26, 2013 at 02:04:17PM +0200, Andriy Gapon wrote:
I am running FreeBSD based on the head from a few weeks ago, amd64.
It seems that after a recent upgrade of openjdk7 I consistently get a kernel
panic when a java process starts:
panic: Bad entry start/end for new stack entry
on 26/12/2013 16:05 Konstantin Belousov said the following:
I provided the following patch yesterday to Peter, after the similar mail.
diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c
index e3842a3..51b60de 100644
--- a/sys/vm/vm_map.c
+++ b/sys/vm/vm_map.c
@@ -1207,6 +1207,7 @@ charged:
On Thu, Dec 26, 2013 at 1:04 PM, Andriy Gapon a...@freebsd.org wrote:
I am running FreeBSD based on the head from a few weeks ago, amd64.
It seems that after a recent upgrade of openjdk7 I consistently get a kernel
panic when a java process starts:
panic: Bad entry start/end for new stack
On Thu, 26 Dec 2013 14:04:17 +0200
Andriy Gapon a...@freebsd.org wrote:
I am running FreeBSD based on the head from a few weeks ago, amd64.
It seems that after a recent upgrade of openjdk7 I consistently get a
kernel panic when a java process starts:
panic: Bad entry start/end for new
On Thu, Dec 26, 2013 at 7:39 AM, Antoine Brodin anto...@freebsd.org wrote:
On Thu, Dec 26, 2013 at 1:04 PM, Andriy Gapon a...@freebsd.org wrote:
...
Hello,
FWIW, I had a similar panic today on 9.2-RELEASE with a GENERIC kernel:
panic: Bad entry start/end for new stack entry
cpuid = 1
KDB:
On Thu, Dec 26, 2013 at 7:33 PM, Peter Wemm pe...@wemm.org wrote:
On Thu, Dec 26, 2013 at 7:39 AM, Antoine Brodin anto...@freebsd.org wrote:
On Thu, Dec 26, 2013 at 1:04 PM, Andriy Gapon a...@freebsd.org wrote:
...
Hello,
FWIW, I had a similar panic today on 9.2-RELEASE with a GENERIC
On Thu, Dec 26, 2013 at 07:51:45PM +0100, Antoine Brodin wrote:
On Thu, Dec 26, 2013 at 7:33 PM, Peter Wemm pe...@wemm.org wrote:
On Thu, Dec 26, 2013 at 7:39 AM, Antoine Brodin anto...@freebsd.org wrote:
On Thu, Dec 26, 2013 at 1:04 PM, Andriy Gapon a...@freebsd.org wrote:
...
Hello,
On Thu, Dec 26, 2013 at 12:01 PM, Konstantin Belousov
kostik...@gmail.com wrote:
On Thu, Dec 26, 2013 at 07:51:45PM +0100, Antoine Brodin wrote:
On Thu, Dec 26, 2013 at 7:33 PM, Peter Wemm pe...@wemm.org wrote:
On Thu, Dec 26, 2013 at 7:39 AM, Antoine Brodin anto...@freebsd.org
wrote:
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antonie,
Do you know which java process is running (if any) when kernel panics?
Please, look around - is there any hs_err_pid.log files in your system.
jvm do some tricky things when setting up stack guard pages and it
worth to take a look at it.
+--On 26 décembre 2013 16:05:00 +0200 Konstantin Belousov
kostik...@gmail.com wrote:
| But there were no core dump available, and I think that your note is also
| valid. I do not see why cow should be cleared from the stack direction
| bits.
I can provide what I have in /var/crash from a
12 matches
Mail list logo
