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

Camera crash on startup - investigation.

  • 112 Replies
  • 34002 Views
*

Offline reyalp

  • ******
  • 13391
Re: Camera crash on startup - investigation.
« Reply #70 on: 16 / April / 2011, 14:49:53 »
Advertisements
I'm wondering if we should just enable the startup workaround for all dryos cameras ? It should be harmless unless some ports have the wrong address for _open ?
Don't forget what the H stands for.

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: Camera crash on startup - investigation.
« Reply #71 on: 05 / August / 2011, 13:00:42 »
IXUS300 / SD4000 also tend to shutdown randomly on chdk startup. I'm gonna test CAM_STARTUP_CRASH_FILE_OPEN_FIX .

ROMLOG example:
Code: [Select]
ASSERT!! FsIoNotify.c Line 457
Occured Time  2011:08:03 22:06:20
Task ID: 1441797
Task name: SpyTask
SP: 0x0037D000
StackDump:
0x00000000
0xFF86EA84
....
....

You were right Phil. Video recording doesn't work. Same problem as bdasmith:'(
What does it mean?
« Last Edit: 05 / August / 2011, 13:42:12 by pixeldoc2000 »

Re: Camera crash on startup - investigation.
« Reply #72 on: 05 / August / 2011, 13:33:02 »
Hey Phil,

I couldn't help myself and jumped right at build 1141 and couldn't be happier now. My SX20 didn't crashed once for the past 3 days now. I am one happy camper. :D I know this is maybe not what you wanted me to do...and maybe you would have preferred that I should have tried version 969 first so you could have pinpointed the error that occurred after that but like I said I had to try the latest build with your correction and I am now 99.9999% sure that you have solved my crah problem.

In about a week I will give you feedback if this still holds true but I am very confident that you have solved the problem.

Thanks a lot and bravo for your effort. ;)

No problem, glad it's working.
There may be a problem with video recording with the 1141 version I sent you.
I'm working with bdasmith to track this down.

The problem he is having is that video stops recording and shows the warning indicator on screen that it could not write the data.

If you also get this problem let me know.

Phil.


I use your asm code you post for Ixus 1000.I record many videos on a concert or some short videos, i never get a crash.

maybe your asm fix need do with all cameras.
For me your asm fix is rock solid, and i photograph really often.currently my image counter on canon is by 4793.and since counter was at around 800 i use always chdk on boot.
« Last Edit: 05 / August / 2011, 13:35:45 by Bernd R »
Ixus 1000 HS

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: Camera crash on startup - investigation.
« Reply #73 on: 05 / August / 2011, 17:08:27 »
You were right Phil. Video recording doesn't work. Same problem as bdasmith:'(
What does it mean?

Different problem - on the SX20 if EXMEM is enabled then video doesn't work.
This one hasn't been solved yet.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)


Re: Camera crash on startup - investigation.
« Reply #74 on: 06 / September / 2011, 09:19:47 »
Hi Phil,

I only now saw your post in the thread at http://chdk.setepontos.com/index.php?topic=6045.0, after I updated my repo and things started breaking again.

Now I've enabled your workaround for my s90, and it looks great so far; I haven't been able to reproduce the problem at all.

Thanks!

    Rob

*

Offline reyalp

  • ******
  • 13391
Re: Camera crash on startup - investigation.
« Reply #75 on: 01 / March / 2014, 19:36:01 »
Resurrecting old thread for http://chdk.setepontos.com/index.php?topic=11184.60

Attached patch uses _open and _close for everything.

It works on a540, d10 and elph130. My test consisted of taking a DNG, verifying that conf setting changes were preserved, and verifying that the reboot crash no longer happens on d10.

I think this should be changed in the trunk, but I'd like to get tests on a few other cameras first.

A few thoughts:
In the past, some of the stubs distinguished between _Write which calls an FsIoNotify function (named FsIoNotify_RememberUpdate in some old disassembly), and _write which does not. The current sigfinder appears to use the _Write address for both.

Looking at the disassembly, this should be harmless if the handle isn't known to FsIoNotify, but it would probably be better to use the non-FsIoNotify version.

The other question is should we do this for VxWorks? In the past this assert has been much less of a problem. I suspect this is due to VxWorks scheduling being less preemptive, since the code seems pretty similar. I would be inclined to just do DryOS initially.
Don't forget what the H stands for.

Re: Camera crash on startup - investigation.
« Reply #76 on: 01 / March / 2014, 19:52:47 »
I think this should be changed in the trunk, but I'd like to get tests on a few other cameras first.
So do I turn off
#define CAM_STARTUP_CRASH_FILE_OPEN_FIX 1
to test this?

My ixus120_sd940 would crash pretty regularly without it (and a few hundred JPG's on the SD card).

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 13391
Re: Camera crash on startup - investigation.
« Reply #77 on: 01 / March / 2014, 20:08:09 »
I think this should be changed in the trunk, but I'd like to get tests on a few other cameras first.
So do I turn off
#define CAM_STARTUP_CRASH_FILE_OPEN_FIX 1
to test this?

My ixus120_sd940 would crash pretty regularly without it (and a few hundred JPG's on the SD card).
No need, it just ignores the defines.
Don't forget what the H stands for.


*

Offline nafraf

  • *****
  • 1308
Re: Camera crash on startup - investigation.
« Reply #78 on: 01 / March / 2014, 21:21:58 »
It works on a540, d10 and elph130. My test consisted of taking a DNG, verifying that conf setting changes were preserved, and verifying that the reboot crash no longer happens on d10.
Tests passed on A810, A1400, SX240.

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: Camera crash on startup - investigation.
« Reply #79 on: 01 / March / 2014, 21:26:30 »
Resurrecting old thread for http://chdk.setepontos.com/index.php?topic=11184.60

Attached patch uses _open and _close for everything.

It works on a540, d10 and elph130. My test consisted of taking a DNG, verifying that conf setting changes were preserved, and verifying that the reboot crash no longer happens on d10.

I think this should be changed in the trunk, but I'd like to get tests on a few other cameras first.

A few thoughts:
In the past, some of the stubs distinguished between _Write which calls an FsIoNotify function (named FsIoNotify_RememberUpdate in some old disassembly), and _write which does not. The current sigfinder appears to use the _Write address for both.

Looking at the disassembly, this should be harmless if the handle isn't known to FsIoNotify, but it would probably be better to use the non-FsIoNotify version.

The other question is should we do this for VxWorks? In the past this assert has been much less of a problem. I suspect this is due to VxWorks scheduling being less preemptive, since the code seems pretty similar. I would be inclined to just do DryOS initially.

Looks ok on my cameras (G12, G1X, SX40 & IXUS310).

The FsIoNotify call in _Close will also ignore the file handle if it is not in the list, so replacing _Close with _close is not strictly necessary.
Having said that, mixing function versions might lead to confusion in the future so perhaps it's better to replace all of them (_Open, _Close, _Read and _Write).

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

 

Related Topics