Camera crash on startup - investigation. - page 12 - General Discussion and Assistance - CHDK Forum

Camera crash on startup - investigation.

  • 112 Replies
  • 27581 Views
*

Offline reyalp

  • ******
  • 12737
Re: Camera crash on startup - investigation.
« Reply #110 on: 29 / March / 2014, 20:11:20 »
Advertisements
Using trunk 3394, I encountered the FsIoNotify assert while attempting to browse the directory tree in chdkptp GUI on D10

ASSERT!! FsIoNotify.c Line 451
Occured Time  2014:03:29 16:05:07
Task ID: 12714009
Task name: PhySw
SP: 0x00309934

Haven't looked in detail but I would guess it involves the directory listing functions. The file browser also uses stat, but IIRC that was safe.
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4285
Re: Camera crash on startup - investigation.
« Reply #111 on: 30 / March / 2014, 13:35:01 »
Using trunk 3394, I encountered the FsIoNotify assert while attempting to browse the directory tree in chdkptp GUI on D10
Me too (r3404) on a3200 (>2000 pictures on card) and ixus115 (~100-200 files). It actually makes the chdkptp GUI almost unusable for browsing and uploading.
Quote
Haven't looked in detail but I would guess it involves the directory listing functions.
a3200 100d:
Code: [Select]
ASSERT!! FsIoNotify.c Line 457
Occured Time  2014:03:30 16:29:18
Task ID: 14155806
Task name: PhySw
SP: 0x0030AB90
StackDump:
0x00000000
0xFF86C950
0x000001C9
0x00000000
0x00000003
0x00000000
0x03CF1B48
0x00000124
0x00000000
0x19980218
0x19980218
0xFF86CA70
0x00000003
0x03CF1B48
0x00000000
0x00000001
0x00000124
0xFF836C60
0x001979B0
0x00000003
0x00000000
0x03CF1B48
0x00000000
0x19980218
0x19980218
0xFFA90BC0
0x00000000
0x03CE1980
0x03CF1B48
0x00000002
0x03CE15B8
0x19980218
0x19980218
0x03CB8EE4
0x03CF1B48
0x03CEBAB8
0x03CDBCD5
0x03CEBAB8
0x00000000
0x03CEBAB8
0x03CE15E8
0x00000002
0x03CE15B8
0x03CD158F
0x00000040
0x00000002
0x03CEBAB8
0x03CE15E8
0x00000002
0x03CE15B8
0x03CD63CB
0x03CEBAB8
0x03CF25D8
0x03CF25D4
0x03CF1CA0
0x00060306
0x03CE1278
0x00000006
0x00000030
0x00000001
0x03CCA128
0x00000005
0x03CCA128
0x00000005
0x03CEBAB8
0x03CE0FC4
0x00000000
0x19980218
0x03CD15F7
0x03CEBAB8
0x03CD1061
0x03CEBAB8
0x03CD15A7
0x03CEBDB8
0x00000000
0x03CEBAB8
0x03CE0FC4
0x00000000
0x19980218
0x19980218
0x19980218
0x19980218
0x19980218
0x03CBE008
0x0030ACAC
0x03CD1053
0x00000000
0x00029780
0x03CF0988
0x03CC8F70
0x03CC752C
0x00000040
0x00000000
0x03CA8B71
0x03CF0988
0x03CC84AC
0x03CE0FC4
0x00000000
0x00000000
0x03CD16A3
0x03CE1138
0x03CE0FC4
0x03CCE945
0x03CC84AC
0x00000001
0xA32F1C9E
0x03CB5373
0x03CB4D09
0x03CD17A1
0x00000000
0x0030AD6C
0x03CF0988
0x00000000
0x00000040
0x03CE1158
0x03CE1158
0x03CEBAB8
0x03CD68AF
0x03CD0213
0xFFFFFFFF
0x03CE2284
0x03CD68AF
0x0030AD94
0x03CEBAB8
0x03CE1158
0x000001D0
0x0030ADA4
0xFFB5D4D4
Code: [Select]
03cb8ec4 <opendir>:
 3cb8ec4: e92d4030 push {r4, r5, lr}
 3cb8ec8: e1a05000 mov r5, r0
 3cb8ecc: e3a00068 mov r0, #104 ; 0x68
 3cb8ed0: eb000661 bl 3cba85c <__malloc_from_arm>
 3cb8ed4: e2504000 subs r4, r0, #0 ; 0x0
 3cb8ed8: 0a00000a beq 3cb8f08 <opendir+0x44>
 3cb8edc: e1a00005 mov r0, r5
 3cb8ee0: ebffb36e bl 3ca5ca0 <_OpenFastDir> ; ***********************
 3cb8ee4: e1a05000 mov r5, r0
 3cb8ee8: e5840000 str r0, [r4]
 3cb8eec: e3a03000 mov r3, #0 ; 0x0
 3cb8ef0: e5c43004 strb r3, [r4, #4]
 3cb8ef4: e1500003 cmp r0, r3
 3cb8ef8: 1a000002 bne 3cb8f08 <opendir+0x44>
 3cb8efc: e1a00004 mov r0, r4
 3cb8f00: eb000658 bl 3cba868 <__free_from_arm>
 3cb8f04: e1a04005 mov r4, r5
 3cb8f08: e1a00004 mov r0, r4
 3cb8f0c: e8bd4030 pop {r4, r5, lr}
 3cb8f10: e12fff1e bx lr

*

Offline reyalp

  • ******
  • 12737
Re: Camera crash on startup - investigation.
« Reply #112 on: 05 / April / 2014, 16:56:37 »
Yup, verified in D10 disassembly that OpenFastDir and closedir use the Open and Close respectively.

trunk changeset 3409 protects them with fileio_semaphore
Don't forget what the H stands for.

 

Related Topics