Date: Fri, 7 May 2010 09:14:45 +0300 From: Achilleas Mantzios <achill@matrix.gatewaynet.com> To: freebsd-java@freebsd.org Subject: Re: openjdk6 crashes Message-ID: <201005070914.46082.achill@matrix.gatewaynet.com> In-Reply-To: <201005070902.22700.achill@matrix.gatewaynet.com> References: <4BE11114.5030306@gmail.com> <4BE3A331.20607@gmail.com> <201005070902.22700.achill@matrix.gatewaynet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=CE=A3=CF=84=CE=B9=CF=82 Friday 07 May 2010 09:02:22 =CE=BF/=CE=B7 Achillea= s Mantzios =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > =CE=A3=CF=84=CE=B9=CF=82 Friday 07 May 2010 08:20:49 =CE=BF/=CE=B7 Peter = Palmreuther =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > > Hello, > >=20 > > On 06.05.10 12:28, mailinglists@moumantai.de wrote: > > > Here the JVM crashed because the user that tries to start it is > > > defined within a ldap database using nsswitch.conf and pam_ldap > > > to connect to. Everthing is fine using a local user. Maybe its > > > the same problem on your side. > >=20 > > I don't think this is the same issue over here. > > It's comepletely local users involed, no LDAP or any other external ser= vice > > configured for user authentication and authorization. > >=20 > > It's just about starting a tomcat from root account, with startup 'su'-= ing to > > 'www', which is localally defined too. >=20 > Hi, in your first message you said you got a "signal 6" SIGABRT, while wi= th the fastdebug build > you got a "signal 4" SIGILL, so you dont have consistent behaviour. >=20 > Are you sure your hardware is sane? > Is your memory ok? Did you run memtest86? Are your disks ok? Is your moth= erboard in a good condition? (no sounds, fans rotating fast, etc..) > Is your CPU in a good condition? Do you experience any high temperatures = on your CPU? >=20 > Note, that it is *100%* normal to have a problematic hardware, and the on= ly instance that the hardware problem is manifested=20 > to happen when running a particular program or script (even consistently). >=20 Also i'd like to add that i had read some years back that linux tries (and = maybe does a good job, but even that is not necessarily enough) to detect and mask out bad memory address. =46reeBSD on the other hand, takes for granted that your hardware is perfec= t. That's why maybe, running FreeBSD or Linux on the same hardware might yeild different behaviors regarding memory issues. =2D-=20 Achilleas Mantzios
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005070914.46082.achill>