>>/158598/
> hardware issue

What was the hardware issue?