Description:
130516 1:48:56 InnoDB: The InnoDB memory heap is disabled
130516 1:48:56 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
130516 1:48:56 InnoDB: Compressed tables use zlib 1.2.3
130516 1:48:56 InnoDB: Initializing buffer pool, size = 128.0M
130516 1:48:56 InnoDB: Completed initialization of buffer pool
130516 1:48:56 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 57791884304
130516 1:48:56 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 57797127168
InnoDB: Doing recovery: scanned up to log sequence number 57799166798
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2766 row operations to undo
InnoDB: Trx id counter is 7FB0200
130516 1:48:57 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76
77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
130516 1:48:58 InnoDB: Waiting for the background threads to start
InnoDB: Starting in background the rollback of uncommitted transactions
130516 1:48:58 InnoDB: Rolling back trx with id 7F7FFA8, 2766 rows to undo
InnoDB: Progress in percents: 1 2 3 4 5130516 1:48:58 InnoDB: Assertion failure in thread 3888118672 in file
/home/nightly/src/main-trunk/src-2013-05-14/trunk/platform/pentium/embedded_rootfs/build/mysql-
5.5.11/storage/innobase/btr/btr0pcur.c line 425
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
130516 1:48:58 - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337868 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = (nil) thread_stack 0x30000
./mysqld(my_print_stacktrace+0x24)[0x82d5b68]
[0x6]
/lib/libc.so.6(abort+0x101)[0x542591]
./mysqld[0x835a9c8]
[0xefd60000]
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.
How to repeat:
Happening occassionally
