Hello,
i have got the exactly same problem with Kernel 2.6.31.4-grsec and MySQL 5.0.51b and 5.1.39. MySQL is compiled from source on an gentoo.
The problem does not appear on 2.6.30.7-grsec ( grsecurity-2.1.14-2.6.30.7-200909151852 )
but on 2.6.31.4-grsec ( grsecurity-2.1.14-2.6.31.4-200910202041 ) and 2.6.31.5-grsec ( grsecurity-2.1.14-2.6.31.5-200910232000 )
Could it be, that the 'bad page state' error fix was removed ?
Greetings,
Daniel
The failure itself:
MySQL 5.1.39-log:
091109 18:41:30 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=1384120320
read_buffer_size=2097152
max_used_connections=7
max_threads=150
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2274233 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x46504488
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x46b213b8 thread_stack 0x30000
/usr/sbin/mysqld-5(my_print_stacktrace+0x21)[0x85def51]
/usr/sbin/mysqld-5(handle_segfault+0x381)[0x825e8f1]
[0xb0710400]
/usr/sbin/mysqld-5(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1c5)[0x81d40b5]
/usr/sbin/mysqld-5(_ZN12Item_func_if10fix_fieldsEP3THDPP4Item+0x38)[0x81e59b8]
/usr/sbin/mysqld-5(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x11f)[0x82a73af]
/usr/sbin/mysqld-5(_ZN4JOIN7prepareEPPP4ItemP10TABLE_LISTjS1_jP8st_orderS7_S1_S7_P13st_select_lexP18st_select_lex_unit+0x202)[0x82ca142]
/usr/sbin/mysqld-5(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x729)[0x82d8949]
/usr/sbin/mysqld-5(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x15e)[0x82ddd7e]
/usr/sbin/mysqld-5[0x826c5e0]
/usr/sbin/mysqld-5(_Z21mysql_execute_commandP3THD+0x4157)[0x8273177]
/usr/sbin/mysqld-5(_Z11mysql_parseP3THDPKcjPS2_+0x340)[0x82769f0]
/usr/sbin/mysqld-5(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1218)[0x8277c18]
/usr/sbin/mysqld-5(_Z10do_commandP3THD+0xe0)[0x82784a0]
/usr/sbin/mysqld-5(handle_one_connection+0x253)[0x8268db3]
/lib/libpthread.so.0[0xb06f816f]
/lib/libc.so.6(clone+0x5e)[0xb05f7c0e]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x90e2ce8 = SELECT count(*) AS count, if (pa.text<>'',pa.text,pa.number) AS name, pa.name AS title FROM product AS p LEFT JOIN product_attribute AS pa ON ( pa.product_number = p.product_number AND pa.language = p.language ) LEFT JOIN product_attribute AS paTeleskope_Allgemein_Serie ON ( paTeleskope_Allgemein_Serie.product_number = p.product_number AND paTeleskope_Allgemein_Serie.language = p.language ) LEFT JOIN product_attribute AS paTeleskope_Anwendungsgebiete ON ( paTeleskope_Anwendungsgebiete.product_number = p.product_number AND paTeleskope_Anwendungsgebiete.language = p.language ) LEFT JOIN product_attribute AS paTeleskope_Optik_Bauart ON ( paTeleskope_Optik_Bauart.product_number = p.product_number AND paTeleskope_Optik_Bauart.language = p.language ) LEFT JOIN product_attribute AS paTeleskope_Optik_Brennweite ON ( paTeleskope_Optik_Brennweite.product_number = p.product_number AND paTeleskope_Optik_Brennweite.language = p.language ) WHERE p.shop = '100' AND p.language = 'fr' AND p.active_in_filter = 1 AND p.is_deliv
thd->thread_id=34772
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
MySQL 5.0.51b-log:
091109 14:19:11 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=1384120320
read_buffer_size=2093056
max_used_connections=8
max_connections=150
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2272678 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x50c08b40
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x50d6e0b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818c77c
0xb7842e55
0x826aeea
0x81e6517
0x81da37f
0x81dd722
0x81d886b
0x81a1adb
0x81a9440
0x81a0250
0x819fc9e
0x819f0f2
0xb783d13d
0xb76abe7a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using ... trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8d51a60 = SELECT p.* FROM product AS p LEFT JOIN product_attribute AS paTeleskope_Optik_Bauart ON ( paTeleskope_Optik_Bauart.product_number = p.product_number AND paTeleskope_Optik_Bauart.language = p.language ) WHERE p.shop = '100' AND p.language = 'de' AND p.active_in_filter = 1 AND p.is_deliverable = 1 AND p.is_master = 0 AND p.class_of_goods_id LIKE '10%' AND ( paTeleskope_Optik_Bauart.refcode = 'Teleskope.Optik.Bauart' AND ( paTeleskope_Optik_Bauart.number IN ( 'Schmidt-Cassegrain' ) OR paTeleskope_Optik_Bauart.text IN ( 'Schmidt-Cassegrain' ) ) ) ORDER BY p.preferred DESC, p.sales DESC LIMIT 9 OFFSET 0
thd->thread_id=46977
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.