Beagleboard xM Rev C builds are broken

```
What steps will reproduce the problem?
1. Obtain Beagleboard-xM Rev C
2. Download prebuilt images for Rowboat Android 2.3.4 for BeagleBoard xM
3. Install prebuilt image onto a SD 2/4/8GB Micro SD card using default script
4. Boot board, wait for it to fail...it will eventually

What is the expected output? What do you see instead?
Android 2.3.4 boots

What version of the product are you using? On what operating system?
I am using a BeagleBoard-xM Rev C with prebuilt Beagleboard-xM images. I have
also tried to build from source with the same results (even using the latest by
doing a repo sync)

Please provide any additional information below.
Board boots from flash just fine, it starts booing android, launches adb and
then outputs 2 messages

request_suspend_state (x->x) (they are different at times, some are 0->0 and I
have seen 0->3 and 3->0)

and

init: untracked pid x exited

Eventually after some time (variable it seems) the system does a kernel oops
and a variety of error messages have been seen, depending on if it was the
first boot or not. Some have been trying to dealocate a NULL pointer others
have been in the ti power saving code. I do not have a different board to test
this on (rev A or B) so I do not know if this is isolated to rev C or not. I
am not getting consistent crashes so providing a boot log is pretty useless as
each time I get different results.

```

Original issue reported on code.google.com by `OpenWa...@gmail.com` on 22 Aug 2011 at 9:20

Start by reproducing the failure on a BeagleBoard-xM Rev C with the prebuilt and source-built Rowboat Android 2.3.4 images, capturing boot and kernel output despite the reported variability. Investigate the reported kernel oops, NULL-pointer errors, and TI power-saving messages; done means Android boots reliably without those failures.

Written by the indexing model from the issue text.