Broken Freerunner.. CPU stall messages.. repairable?

[Maksim 'max_posedon' Melnikau]

I have same missages too, Qi can't boot my system from nand too,

BUT It successfully boots with uboot (actually not always, but boots),
there is opinion that Qi doesn't handle badblocks on nand correctly,
or smth like this.

So, try uboot.

On 9/30/09, Thomas Franck <thomas.franck at gmx.com> wrote:
> Hi..
>
> This is a re-post from the support ML.. community is way more active,
> hope to get some more hints here.. :)
>
> I can access the NOR boot menu.. and since then I have reflashed the
> kernel, the system image and the boot loader..
> I also disassembled the FR (for the first time!!) to see if I can find
> any physical damage.. didn't manage to remove the tin caps for look
> under there, though.. after re-assembling I still get the CPU stall..
>
> ------
>
> Some moron broke my freerunner by a hard impact yesterday (EDIT: that
> was last sunday.. oh, and the case is OK, in fact, everything seems
> fine, except the messages)..  :(
>
> now the bootloader (Qi) starts, and I think Kernal start booting, too..
> I get messages like:
>
> [ 0.000000] Unknown boot option 'g_ether.host_addr=00:1F:11:01:2D:C7:
> ignoring
> [ 0.000000] Unknown boot option 'g_ether.dev_addr=00:1F:11:01:2D:C7:
> ignoring
> [ 0.000000] Unknown boot option 'g_ether.host_addr=00:1F:11:01:2D:C7:
> ignoring
> [ 0.000000] Unknown boot option 'g_ether.dev_addr=00:1F:11:01:2D:C7:
> ignoring
> [21474548.655000] INFO: RCU detected CPU 0 stall (t=429490971/2000 jiffies)
> [21474578.655000] INFO: RCU detected CPU 0 stall (t=429491571/8000 jiffies)
>
> etc...
>
> when I touch the screen, I get:
> drivers/input/touchscreen/s3c2410_ts.c:stylus_action bug.
> drivers/input/touchscreen/s3c2410_ts.c: stylus_updown lost event!
> drivers/input/touchscreen/s3c2410_ts.c: stylus_updown lost event!
>
>
> is there something I can do?  I mean, beside getting a new FR :S  :(
>
> Cheers,
> --
> Thomas
>
> -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
> In addition to prototyping, Dan put together a reference card for users.
> If we couldn't figure out how to explain a feature on the reference card
> we would change the program. The original method for copying formulas
> was too complicated so we just changed the design rather than try to
> explain it.
>   - Bob Frankston, author (with Dan Bricklin) of VisiCalc
> -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
>
>