Bug in ndb_mgm ? (no replies)

Ok, this is rather funny ...

ndb_mgm> all report memory
Node 2: Data usage is 223679%(-3208 32K pages of total 19200)

Ndb node is still in the starting phase.

2012-11-18 16:02:40 [ndbd] WARNING -- Watchdog: Warning overslept 263 ms, expected 100 ms.
2012-11-18 16:02:40 [ndbd] INFO -- timerHandlingLab now: 133124833 sent: 133124612 diff: 221
2012-11-18 16:02:41 [ndbd] INFO -- Watchdog: User time: 234 System time: 78386
2012-11-18 16:02:41 [ndbd] WARNING -- Watchdog: Warning overslept 226 ms, expected 100 ms.
2012-11-18 16:02:43 [ndbd] INFO -- Watchdog: User time: 234 System time: 78578
2012-11-18 16:02:43 [ndbd] WARNING -- Watchdog: Warning overslept 450 ms, expected 100 ms.
2012-11-18 16:02:43 [ndbd] INFO -- timerHandlingLab now: 133127097 sent: 133126695 diff: 402
2012-11-18 16:03:13 [ndbd] WARNING -- Ndb kernel thread 0 is stuck in: Polling for Receive elapsed=169
2012-11-18 16:03:13 [ndbd] INFO -- Watchdog: User time: 241 System time: 81665
2012-11-18 16:03:13 [ndbd] INFO -- timerHandlingLab now: 133157974 sent: 133157720 diff: 254

How should I proceed now?

EDIT: Mysql cluster 7.2.8 debian 6.0 64bit

EDIT2:

2012-11-18 16:26:08 [ndbd] WARNING -- Ndb kernel thread 0 is stuck in: Allocating memory elapsed=12009
2012-11-18 16:26:08 [ndbd] INFO -- Watchdog: User time: 26 System time: 2429
2012-11-18 16:26:14 [ndbd] WARNING -- Ndb kernel thread 0 is stuck in: Allocating memory elapsed=18020
2012-11-18 16:26:14 [ndbd] INFO -- Watchdog: User time: 27 System time: 3029

1,3GB free, datamemory 600M, indexmemory 100M