The eNodeB may sometimes wrongly generate PHICH because somewhere
'phich_active' is not reset to 0, due to an unidentified reason. When
adding this hack the problem seems to disappear completely.
This is not the end of the story. The real underlying problem has to be
understood and fixed correctly.