Comment 22 for bug 720055

i had a similar oops when bringing up another on-chip core (the SGX). It turned out that the core's power and clock needed to be turned up before executing code that poked at its registers; the "imprecise data abort" reflected an aborted fetch from a memory location mapped to a powered-down on-chip core. Your oops may be related to the issue addressed by http://gitorious.org/linux-omap-dss2/linux/commit/096b38e85e9512b6eddd08d33f0adcb5b45573fe .