Ihave not seen such high times for clRead Buffer.
It might happen if we queue up lot of commands in a command queue. They are then launched together as a batch to save on kernel launch overhead. In this case all the commands report similar start & end times which might be resulting in such high times.
Do you see such numbers for a single command?