Comment 1 for bug 435007

This currently seems to be the result of poor trace placement on the board. This problem has not been exhibited on professional boards, more research must be executed before this can be considered a bug in firmware.