InnoDB crashed will performed full table scans

[Glenn Matthys]

Hello,

This morning during the backups, using the command:
nice -n10 mysqldump -u root -p"xxx" --all-databases


(datadir is set to /home/mysql) The MySQL server crashed with the following message in /home/mysql/mysql1.err:

InnoDB: Warning: a long semaphore wait:
--Thread 2960063376 has waited at ./../include/log0log.ic line 315 for 740.00 seconds the semaphore:
Mutex at 0xb79c20b4 created file log0log.c line 744, lock var 0
waiters flag 0
wait has ended
InnoDB: Warning: a long semaphore wait:
--Thread 2966961040 has waited at ./../include/log0log.ic line 315 for 740.00 seconds the semaphore:
Mutex at 0xb79c20b4 created file log0log.c line 744, lock var 1
waiters flag 0
InnoDB: Warning: a long semaphore wait:

After this the database server didn't accept new connections with the message " Too many connections" or " Can't connect to MySQL server on 'mysql1'".

It's a small database server, it only has 128M of data.

Anyone know what might have caused this? Because of this I had to repair a bunch of tables (including both MyISAM and InnoDB ones) and even had to restore 1 table from backup.

mysql Ver 14.12 Distrib 5.0.41, for pc-linux-gnu (i686) using readline 5.2