On Fri, 27 Dec 2013, Peter Wemm wrote:
Date: Thu, 26 Dec 2013 10:33:01 -0800
From: Peter Wemm <pe...@wemm.org>
To: Antoine Brodin <anto...@freebsd.org>
Cc: Alan Cox <a...@freebsd.org>, Marcel Moolenaar <mar...@freebsd.org>,
FreeBSD Current <freebsd-current@freebsd.org>, Andriy Gapon
<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:
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: stack backtrace:
#0 0xffffffff80947986 at kdb_backtrace+0x66
#1 0xffffffff8090d9ae at panic+0x1ce
#2 0xffffffff80b81314 at vm_map_stack+0x274
#3 0xffffffff80b83584 at vm_mmap+0x674
#4 0xffffffff80b83d2f at sys_mmap+0x1cf
#5 0xffffffff80cf187a at amd64_syscall+0x5ea
#6 0xffffffff80cdbff7 at Xfast_syscall+0xf7
It looks like the box was compiling java related ports (java/jaxen and
devel/antlr) when it panic'ed.
This is troubling. I'm wondering what's changed and why we haven't
seen this before.
Just so I'm clear, you're building 9.2 ports on a 9.2-REL kernel,
right? and not something like building 9.2-REL ports inside a jail on
a 10.x or 11.x host? 10.x / 11.x are not involved and you're seeing
this?
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
Another data point - I'm running 9.2, svn to 9-stable, and my ports
tree is kept current with portsnap.
On Wednesday (25 Dec) I built the "devel/arduino" port, which pulls in
openjdk-6.2. I was using a /usr/src & /usr/ports updated 13 December.
The kernel was r259382:. Everything worked great.
Thursday, I did
svn update /usr/src
portsnap fetch update
(the svn is against 9-stable), rebuilt world+kernel, and ran
'portupgrade -a'. That gave a r259923 kernel.
Arduino now reliably takes the box down, no dump, just a freeze /
reboot. Rebooting on the older kernel doesn't fix anything.
regards,
Ross ve6pdq
--
Ross Alexander, (780) 675-6823 / (780) 689-0749, r...@athabascau.ca
"Always do right. This will gratify some people,
and astound the rest." -- Samuel Clemens
--
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
