Mysql borken and ssh

i upgraded this morning and mysql keeps crashing this is the output

May 8 18:56:42 broken mysqld[2996]: mysqld got signal 11;

May 8 18:56:42 broken mysqld[2996]: This could be because you hit a bug. It is also possible that this binary

May 8 18:56:42 broken mysqld[2996]: or one of the libraries it was linked against is corrupt, improperly built,

May 8 18:56:42 broken mysqld[2996]: or misconfigured. This error can also be caused by malfunctioning hardware.

May 8 18:56:42 broken mysqld[2996]: We will try our best to scrape up some info that will hopefully help diagnose

May 8 18:56:42 broken mysqld[2996]: the problem, but since we have already crashed, something is definitely wrong

May 8 18:56:42 broken mysqld[2996]: and this may fail.

May 8 18:56:42 broken mysqld[2996]:

May 8 18:56:42 broken mysqld[2996]: keybuffersize=32768

May 8 18:56:42 broken mysqld[2996]: readbuffersize=131072

May 8 18:56:42 broken mysqld[2996]: maxusedconnections=0

May 8 18:56:42 broken mysqld[2996]: max_connections=100

May 8 18:56:42 broken mysqld[2996]: threads_connected=0

May 8 18:56:42 broken mysqld[2996]: It is possible that mysqld could use up to

May 8 18:56:42 broken mysqld[2996]: keybuffersize + (readbuffersize + sortbuffersize)*max_connections = 19231 K

May 8 18:56:42 broken mysqld[2996]: bytes of memory

May 8 18:56:42 broken mysqld[2996]: Hope that's ok; if not, decrease some variables in the equation.

May 8 18:56:42 broken mysqld[2996]:

May 8 18:56:42 broken mysqld[2996]: thd=(nil)

May 8 18:56:42 broken mysqld[2996]: Attempting backtrace. You can use the following information to find out

May 8 18:56:42 broken mysqld[2996]: where mysqld died. If you see no messages after this, something went

May 8 18:56:42 broken mysqld[2996]: terribly wrong…

May 8 18:56:42 broken mysqld[2996]: Cannot determine thread, fp=0x412137d4, backtrace may not be correct.

May 8 18:56:42 broken mysqld[2996]: Stack range sanity check OK, backtrace follows:

May 8 18:56:42 broken mysqld[2996]: 0x810e24b

May 8 18:56:42 broken mysqld[2996]: 0x4003aaf8

May 8 18:56:42 broken mysqld[2996]: (nil)

May 8 18:56:42 broken mysqld[2996]: New value of fp=(nil) failed sanity check, terminating stack trace!

May 8 18:56:42 broken mysqld[2996]: Please read http://dev.mysql.com/doc/mysql/en/Using … trace.html">http://dev.mysql.com/doc/mysql/en/Usingstacktrace.html and follow instructions on how to resolve the stack trace. Resolved

May 8 18:56:42 broken mysqld[2996]: stack trace is much more helpful in diagnosing the problem, so please do

May 8 18:56:42 broken mysqld[2996]: resolve it

May 8 18:56:42 broken mysqld[2996]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains

May 8 18:56:42 broken mysqld[2996]: information that should help you find out what is causing the crash.

May 8 18:56:42 broken mysqld_safe[2999]: ended

May 8 18:56:49 broken /etc/init.d/mysql[3062]: 0 processes alive and '/usr/bin/mysqladmin –defaults-file=/etc/mysql/debian.cnf ping' resulted in

May 8 18:56:49 broken /etc/init.d/mysql[3062]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed

May 8 18:56:49 broken /etc/init.d/mysql[3062]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'

May 8 18:56:49 broken /etc/init.d/mysql[3062]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

May 8 18:56:49 broken /etc/init.d/mysql[3062]:

broken:/var/cache/apt/archives#

and it just wont start now, ive tried downgrading version and still having the issue.. any ideas?

and all of a sudden i cant ssh in, i can only access stuff via lish..

any ideas?

cheers

Nathan