Particularly while rehasing, you might see this on the partyline:

1718.45  [12:18] bMotion: A level 4 diagnostic has found a duplicate utimer timer2408384 for bmotion_flood_tick ... removing
1718.45  [12:18] bMotion: A level 4 diagnostic has found a duplicate utimer timer2408383 for bmotion_interbot_resync ... removing
1718.45  [12:18] bMotion: A level 4 diagnostic has found a duplicate utimer timer2408382 for bmotion_interbot_next_elect ... removing

Don't panic! You can ignore this. It's entirely harmless. In versions >0.0.9, this message goes to a debug loglevel rather than the main partyline.

Explaination

Due to the way TCL and eggdrop work it can be a bit of a sod to reliably not have multiple instances of the same timer running. For most things, this isn't too much of a big deal and will just result in maintenance functions being called too often. Some things it'd be bad news for though - bMotion will start calling InterbotElections too frequently on the partyline, or could say randomstuff too often.

To work around this (i.e. to be a bit lazy), bMotion frequently scans the list of timers and utimers and deletes any duplicates it finds. Typically these are caused when you RehashBmotion? (or eggdrop directly).