This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#11433 - Nano 2G: *PANIC* stkov nand crash
Attached to Project:
Rockbox
Opened by Hunter Ragnarok (G4Oblivion) - Tuesday, 22 June 2010, 20:05 GMT+2
Last edited by Frank Gevaerts (fg) - Monday, 06 September 2010, 16:14 GMT+2
Opened by Hunter Ragnarok (G4Oblivion) - Tuesday, 22 June 2010, 20:05 GMT+2
Last edited by Frank Gevaerts (fg) - Monday, 06 September 2010, 16:14 GMT+2
|
DetailsWhen I put these settings into my nano it crashes at "browse themes" it does not crash if I try to change the theme only.
Steps: Change time format to 12 hour Playback: Repeat: one, Fade on stop/pause: No General: LCD brightness = 10, Idle poweroff = 8min., Accessory power supply = No Theme: Clicking Browse theme files make it crash with "*PANIC* stkov nand" error. Using revision: r27036 This just started happening. I update quite often and I always do a clean build to reset my settings. I don't like importing my config file. |
This task depends upon
Closed by Frank Gevaerts (fg)
Monday, 06 September 2010, 16:14 GMT+2
Reason for closing: Fixed
Additional comments about closing: The final patch was submitted as r28011
Monday, 06 September 2010, 16:14 GMT+2
Reason for closing: Fixed
Additional comments about closing: The final patch was submitted as r28011
FS#11430. Can you please check if that issue still appears?Using the same steps + start screen = files.
I was able to change my theme, font, foreground/background color.
I then went to view "files" and I got the same crash, "*PANIC* stkov nand"
I'm guessing its one of the recent updates by theseven that caused it.
I'm currently using r27090
I can turn off my nano right after applying the settings then go to view files without crashing.
I was able to turn it off then change the theme before too. Not sure what this means.
I got a clean build put my config file from my previous build and as soon as I turn it on I get the *PANIC* stkov nand.
I would like this fixed since I can't revert back because theres no archived builds for unstable ports......
I'll post a .diff of what I did. All I did was remove "call_storage_idle_notifys(false);"
I will try to test it some more, but I think its fine.
Small plus; when opening and closing a text file main stack usage went from 75% to 62%.
Little annoying that just by removing "call_storage_idle_notifys(false);" nand stack usage goes from 74% to 2%.
Is this something that could make it into current svn? or would it interfere with other targets?
Sorry, I don't know much about coding.
Yes, this is meant for svn, it just needs a bit more testing (possibly on other targets too) to make sure it doesn't break anything.