I recently changed my kernel (as noted in another message) to one that supports ACPI (for my laptop running RH9) and a couple other patches (I don't know all of them, one may have been the preemptive kernel patch). I've installed MySQL 4.0.12 from RPM's on the myslq.com site. When I start mysql using /etc/init.d/mysql start, I now get a 1024 segmentation fault:
# /etc/init.d/mysql start # Starting mysqld daemon with databases from /var/lib/mysql /usr/bin/mysqld_safe: line 320: 1024 Segmentation fault $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking >>$err_log 2>&1 030618 08:00:57 mysqld ended I've checked the mysql log /var/lib/mysql/hostname.err but all it shows is this: 030618 08:00:57 mysqld started 030618 08:00:57 mysqld ended no realy information at all. If I switch back to the stock RH9 kernel, mysql starts just fine. So what in the kernel would cause this sudden segfault on startup? I don't get it. It shouldn't happen. Please answer. I've searched the mysql and mysql-bugs archives at AIMS and no answer. I did a google search on this error and come up with hits from many different lists (PHP, LDAP, and so forth) but nothing that pertains to what I'm seeing. Can someone provide some insight? -- .''`. Carl B. Constantine : :' : [EMAIL PROTECTED] `. `' GnuPG: 135F FC30 7A02 B0EB 61DB 34E3 3AF1 DC6C 9F7A 3FF8 `- Debian GNU/Linux -- The power of freedom
pgp00000.pgp
Description: PGP signature
