Quote:
Originally Posted by arrrghhh
Hm. Let me see if I can recreate that. This was the exact bug I was trying to track down, and stinebd had me disable JIT because he said it basically prevents us from debugging the error.
After disabling JIT... I couldn't reproduce the error. And so FRX03 was born...
I'll see if I can reproduce this on the newest kernel/rootfs.
Just tried, abused the heck outta the volume control... No resets.
|
I have this same problem. I have no idea how to fix it either