• Status Closed
  • Percent Complete
  • Task Type Bugs
  • Category Settings
  • Assigned To No-one
  • Operating System iPod Nano 2G
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by G4Oblivion - 2010-06-22
Last edited by fg - 2010-09-06

FS#11433 - Nano 2G: *PANIC* stkov nand crash

When I put these settings into my nano it crashes at “browse themes” it does not crash if I try to change the theme only.

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.

Closed by  fg
2010-09-06 14:14
Reason for closing:  Fixed
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

The final patch was submitted as r28011

Sounds like the same issue as  FS#11430 . Can you please check if that issue still appears?

I still get this problem, although its a little different.
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

More information:
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.

This has just become a serious problem for me.
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……

Give a try to FS#11429 instead of complaining, we all want that fixed.

I’ve built the latest release (r27956) and did a temporary fix on it to stop the crash. You can download it here
I’ll post a .diff of what I did. All I did was remove “call_storage_idle_notifys(false);”

fg commented on 2010-09-05 12:50

This patch changes fat.c a bit to avoid ever allocating two sector buffers on the stack. From what I can see, that should make things work without changing nand_stack, or at least without changing it a lot.

fg commented on 2010-09-05 17:06

This patch should make sure that fat.c never allocates more than one sector buffer on the stack

Thanks Gevaerts!, I have not gotten the nand crash yet. All I tested was my normal “Import config.cfg and wait for crash”.
I will try to test it some more, but I think its fine.

I did some more testing and could not get the “*PANIC* stkov nand” crash.
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.

fg commented on 2010-09-06 11:28

Removing call_storage_idle_notifys() removes a large part of the reason why the nand thread (and stack) exists, so it’s not surprising that that reduces stack usage.

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.


Available keyboard shortcuts


Task Details

Task Editing