ACK problems

Odd ack problem

I have a machine that went red for CPU

It generated an "cookie" of 371004 , and paged reciepent1. It was then ACK'd for 8 hours. CPU recovered after 2 hours, then went red again. This generated a new "cookie" of 344975, which we could no longer ACK because in the hobbitdboard it had the "old" ack data and time. This new "cookie" then escalated (because we could not ack this event)

Is there some logic I need to look at in do_alert where something recovers and can't be ack'd again?

-Sean