111028 08:41:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111028  8:41:22 InnoDB: The InnoDB memory heap is disabled
111028  8:41:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111028  8:41:22 InnoDB: Compressed tables use zlib 1.2.5
111028  8:41:22 InnoDB: Using Linux native AIO
111028  8:41:22 InnoDB: Initializing buffer pool, size = 128.0M
111028  8:41:22 InnoDB: Completed initialization of buffer pool
111028  8:41:22 InnoDB: highest supported file format is Barracuda.
111028  8:41:22  InnoDB: Waiting for the background threads to start
111028  8:41:23 InnoDB: 1.1.8 started; log sequence number 1595685
111028  8:41:24 [Note] Event Scheduler: Loaded 0 events
111028  8:41:24 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.14-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution
111028  8:46:30  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 0:9216, should be 0:326!
111028  8:46:30  InnoDB: Assertion failure in thread 1078197152 in file 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.
111028  8:46:30 - 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=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133434 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x11831208
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 = 0x4043f408 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x46)[0x10d05855]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x118a2f00): INSERT INTO `Test` (Message) SELECT Message FROM Test ORDER BY TestId LIMIT 100000
Connection ID (thread ID): 1
Status: 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.
111028 08:46:30 mysqld_safe Number of processes running now: 0
111028 08:46:30 mysqld_safe mysqld restarted
111028  8:46:31 InnoDB: The InnoDB memory heap is disabled
111028  8:46:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111028  8:46:31 InnoDB: Compressed tables use zlib 1.2.5
111028  8:46:31 InnoDB: Using Linux native AIO
111028  8:46:31 InnoDB: Initializing buffer pool, size = 128.0M
111028  8:46:31 InnoDB: Completed initialization of buffer pool
111028  8:46:31 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 391940727
111028  8:46:31  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 397183488
InnoDB: Doing recovery: scanned up to log sequence number 399464549
111028  8:46:31  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
InnoDB: Last MySQL binlog file position 0 59140664, file name ./mysql-bin.000005
111028  8:46:32  InnoDB: Waiting for the background threads to start
111028  8:46:33 InnoDB: 1.1.8 started; log sequence number 399464549
111028  8:46:33 [Note] Recovering after a crash using mysql-bin
111028  8:46:33 [Note] Starting crash recovery...
111028  8:46:33 [Note] Crash recovery finished.
111028  8:46:34 [Note] Event Scheduler: Loaded 0 events
111028  8:46:34 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.14-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution