• Status Closed
  • Percent Complete
  • Task Type Bugs
  • Category Operating System/Drivers
  • Assigned To
  • Operating System Iriver H100 series
  • Severity High
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by pabouk - 2010-02-08
Last edited by jdgordon - 2010-02-10

FS#10983 - panic: I04:IllInstr

With the latest builds I observe panic immediately after starting Rockbox kernel from the bootloader. The bootloader writes approximately:

… checksum … result 0

then the screen clears and Rockbox immediately writes (two different results for two builds tested):
— build r24571-000208
at 31057FE8
— — build r24568-100208
at 31057FE4
— Then it normally reacts to pressing PLAY by rebooting.

The latest known working build is the daily build r24556-100207. The problem happens on iriver H120.

PS: Notice the wrong year in the build number: build r24571-000208

Closed by  jdgordon
2010-02-10 04:21
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

mea culpa. fixed in r24578.

Initially I forgot to clear the configuration. A while ago I tried that (I completely erased .rockbox directory and .scrobbler-timeless.log and the result is the same.

It did not come to my mind to erase the config. as the message appears immediately after bootloader finishes its job.

With linuxstb we realized that the problem was introduced by r24568

This may not be the same reason it crashes on target, but r24568 of the h140 sim also crashes on startup:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff3c46910 (LWP 21527)]
0×0000000000434394 in sb_get_backdrop (screen=2) at /home/dave/rockbox/rockbox/apps/gui/statusbar-skinned.c:81
81 return sb_skin[screen].data→backdrop;

how the hell can screen==2?! ok, I’ll look into this.


Available keyboard shortcuts


Task Details

Task Editing