090118 16:00:25 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
090118 16:00:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
090118 16:00:29 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
InnoDB: Log scan progressed past the checkpoint lsn 0 3207474084
090118 16:00:30  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 0 3207484055
090118 16:00:30  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 090118 16:00:31 - 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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 345917 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 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 0x20000
/usr/sbin/mysqld(my_print_stacktrace+0x22) [0x85043d2]
/usr/sbin/mysqld(handle_segfault+0x3d9) [0x821f239]
[0xffffe420]
/usr/sbin/mysqld(page_cur_parse_insert_rec+0x53d) [0x8434d7d]
/usr/sbin/mysqld [0x842058d]
/usr/sbin/mysqld(recv_recover_page+0x4be) [0x84223ae]
/usr/sbin/mysqld(buf_page_io_complete+0x581) [0x83dd581]
/usr/sbin/mysqld(fil_aio_wait+0x10b) [0x83f69bb]
/usr/sbin/mysqld [0x84647a8]
/lib/tls/i686/cmov/libpthread.so.0 [0xb7f7f4fb]
/lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7d71e5e]
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.
090118 16:00:31 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended