On Fri, Feb 08, 2008 at 02:40:41PM +, Primeroz lists wrote:
#7 0x802af5e3 in _sx_xlock (sx=0x802b02bd, file=0x4
Address 0x4 out of bounds, line=-2140937936)
at /usr/src/sys/kern/kern_sx.c:192
192 }
Well, the file and line are nonsense.
#17 0x802b845e in
Server keeps crashing, I maged to have a new coredump that should be
reliable this time.
Here is the debugging of the kernel ... i'm not really an expert in this
topic so if you need any more information just let me know and i will do my
best to provide it.
[GDB will not be able to debug
Yes i agree with everything. Definetly mysql need to be tuned for InnoDB and
in general .
As stated in the previous post my a collegue of mine i had to install a new
kernel to have a consistent crash coredump.
Anyway still in my mind is that even if not tuned mysql should not cause my
kernel to
- Primeroz lists [EMAIL PROTECTED] wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or
2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
set-variable=
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
set-variable= key_buffer=768M
set-variable= table_cache=800
On Mon, Feb 04, 2008 at 12:50:32PM +, Primeroz lists wrote:
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
{snip}
There's
Just wanted to point out that anyway our crash is a Kernel panic crash and
not a Mysqld crash.
Platform is AMD64 so , i'm don't think it can be a problem of process size :
$ sudo -u mysql limits
Resource limits (current):
cputime infinity secs
filesize infinity kB
There's additional information needed to help with this:
1) Contents of /boot/loader.conf
empty
2) What scheduler you're using in your kernel configuration
We using the 4bsd Scheduler (ULE is commented out in kernel conf)
3) Your kernel configuration in its entirity, if possible
On Mon, Feb 04, 2008 at 12:50:32PM +, Primeroz lists wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
On Mon, Feb 04, 2008 at 02:50:09PM +, Primeroz lists wrote:
Just wanted to point out that anyway our crash is a Kernel panic crash and
not a Mysqld crash.
But the process that's inducing the panic *every time* is mysqld; this
you've already confirmed. To me this means that mysqld is
On Mon, Feb 04, 2008 at 04:35:13PM +, Primeroz lists wrote:
The vm_map.c does not contain a call to the vm_map_unlock() at the
line 3074.
Mine does ... is Revision *1.366.2.3 *on Freebsd CVS for vm_map.c , CVS TAG
RELENG_6_2
Not according to either the kgdb output you included or
We use mysql-server-5.0.45 (fairly old, since newest is 5.0.51a); yours
is a bit older. I'll have to look at the ChangeLog between 5.0.41 and
5.0.51a to see if there's any relevant changes which might give hints to
what's causing it.
I don't see any changes relevant between 5.0.41 and
The vm_map.c does not contain a call to the vm_map_unlock() at the
line 3074.
Mine does ... is Revision *1.366.2.3 *on Freebsd CVS for vm_map.c , CVS TAG
RELENG_6_2
Please, rebuild you kernel from scratch. In case this does not help,
I ask you to show the backtrace from the ddb. Also, to
On Mon, Feb 04, 2008 at 07:04:19AM -0800, Jeremy Chadwick wrote:
But the process that's inducing the panic *every time* is mysqld; this
you've already confirmed. To me this means that mysqld is responsible
for tickling some sort of condition that causes a panic; it could be the
fault of mysqld or
On Mon, Feb 04, 2008 at 02:19:05PM +, Primeroz lists wrote:
We using the 4bsd Scheduler (ULE is commented out in kernel conf)
That's good, as it confirms you're not hitting ULE bugs.
3) Your kernel configuration in its entirity, if possible :-)
attached
I don't see anything in your
Primeroz lists wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
SNIP
$ sudo kgdb /usr/obj/usr/src/sys/PE2950/kernel.debug vmcore.2
SNIP
This back trace will be useless, I
16 matches
Mail list logo
