Rockbox General > Rockbox General Discussion

ipod4g instability fixed with 20070301 daily

(1/2) > >>

Shovas:
Since April, 06, I've been downloading daily builds of rockbox for my Ipod 4g 20GB. Initially I downloaded once every few days, then moved to once every few weeks. Finally, I started downloading the builds at the start of the month. I've run 21 builds beginning April 24, 06.

Now, there's a common problem with ipod4g's with instability. People who have this model and have used rockbox for a while tend to agree there was hardware instability (triggered by some code, but who knows where it was) when modulating the CPU speed. So the common fix was to jack up the CPU speed. I always ran mine up to 10 from the CPU Frequency debug menu option.

With the 2007-03-01 build, however, I tried again to run without updating the CPU Frequency. I've been running for quite some time now (a few hours) and no crashes, "data corrupt at...", errors, freezes, etc. at all. Previously, these errors would have triggered within 10 minutes or so.

It looks to me like the issue is resolved. No more jacking up the CPU _every_time_ you boot your ipod!

If I see any more problems I'll be sure to post them here.

Can anyone confirm these results?

Llorean:
There was never any reason to increase the boost by more than 1. It's an on/off thing. Setting it to 10 just means "On, 10 times" which means it'd have to be turned off 10 times before it goes off. It doesn't make it any more boosted than just 1.

Shovas:

--- Quote from: Llorean on March 04, 2007, 06:17:56 PM ---There was never any reason to increase the boost by more than 1. It's an on/off thing. Setting it to 10 just means "On, 10 times" which means it'd have to be turned off 10 times before it goes off. It doesn't make it any more boosted than just 1.

--- End quote ---

Actually, early on when I started boosting, I would boost it by one, as you say. What seemed to happen is that rockbox would modulate it down to 0 (30mhz) when it felt it didn't need 70mhz. And so you'd get the crashing. The errors disappeared when the system was at 70mhz all the time. So, that's why I've been jacking it up to at least 10. Maybe that behaviour changed at some point.

Llorean:
If it was going down to 0, there were more unboosts than there were boosts, and it should've been reported.

It only ever needed to be increased by 1. Not set to 1. Increased by 1. As long as the rest of the boost-tracking portion of the code keeps count properly.

Shovas:

--- Quote from: Llorean on March 04, 2007, 06:21:51 PM ---If it was going down to 0, there were more unboosts than there were boosts, and it should've been reported.

It only ever needed to be increased by 1. Not set to 1. Increased by 1. As long as the rest of the boost-tracking portion of the code keeps count properly.

--- End quote ---

Interesting. I do remember rechecking the cpu frequency after I initially set it to 10 to see if rockbox was changing it. I remember becoming confident it wasn't changing (the last time I would've checked was Fall 06). But I'm also confident I remember it changing the cpu freq when I set it to 1 (this would have been a lot earlier, April/May/June 06).

I wonder if more-unboosts-than-boosts was the bug. I at one point took a look at the boosting code (to see if I could make it a constant) and couldn't see any problematic cases.

Navigation

[0] Message Index

[#] Next page