2013-04-18 12:37:45 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-04-18 12:37:45 0 [Warning] Changed limits: max_open_files: 1024  max_connections: 151  table_cache: 431
2013-04-18 12:37:45 5826 [Note] Plugin 'FEDERATED' is disabled.
/ssd/mysql-5.6.11/BUILD/sql/mysqld: Table 'mysql.plugin' doesn't exist
2013-04-18 12:37:45 5826 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2013-04-18 12:37:45 7fdde4e69720 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2013-04-18 12:37:45 7fdde4e69720 InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
2013-04-18 12:37:45 5826 [Note] InnoDB: The InnoDB memory heap is disabled
2013-04-18 12:37:45 5826 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-04-18 12:37:45 5826 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-04-18 12:37:45 5826 [Note] InnoDB: Using Linux native AIO
2013-04-18 12:37:45 5826 [Note] InnoDB: Using CPU crc32 instructions
2013-04-18 12:37:45 5826 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-04-18 12:37:45 5826 [Note] InnoDB: Completed initialization of buffer pool
2013-04-18 12:37:45 5826 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2013-04-18 12:37:45 5826 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2013-04-18 12:37:45 5826 [Note] InnoDB: Database physically writes the file full: wait...
2013-04-18 12:37:45 7fdde4e69720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2013-04-18 12:37:45 7fdde4e69720  InnoDB: File name /tmp/vardir2/master-data/ib_logfile101
2013-04-18 12:37:45 7fdde4e69720  InnoDB: File operation call: 'create' returned OS error 71.
2013-04-18 12:37:45 7fdde4e69720  InnoDB: Cannot continue operation.
2013-04-18 12:37:45 7fdde4e69720  InnoDB: Assertion failure in thread 140591004817184 in file os0file.cc line 662
InnoDB: Failing assertion: 0
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
19:37:45 UTC - 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 = 68252 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 = 0 thread_stack 0x40000
/ssd/mysql-5.6.11/BUILD/sql/mysqld(my_print_stacktrace+0x35)[0xa8a85d]
/ssd/mysql-5.6.11/BUILD/sql/mysqld(handle_fatal_signal+0x404)[0x722c58]
/lib64/libpthread.so.0(+0xf500)[0x7fdde4a4e500]
/lib64/libc.so.6(gsignal+0x35)[0x7fdde36fa8a5]
/lib64/libc.so.6(abort+0x175)[0x7fdde36fc085]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xb7cee2]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xb7cf17]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xb7dccb]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xc469f7]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xc47f35]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xc48209]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xc4ab39]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0xb024c1]
/ssd/mysql-5.6.11/BUILD/sql/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0xce)[0x63288c]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0x7dd6b1]
/ssd/mysql-5.6.11/BUILD/sql/mysqld(_Z11plugin_initPiPPci+0x74e)[0x7de101]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0x61ed63]
/ssd/mysql-5.6.11/BUILD/sql/mysqld(_Z11mysqld_mainiPPc+0x50f)[0x61fbec]
/ssd/mysql-5.6.11/BUILD/sql/mysqld(main+0x20)[0x615474]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fdde36e6cdd]
/ssd/mysql-5.6.11/BUILD/sql/mysqld[0x615399]
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.
Writing a core file