Canon 100D / SL1

[a1ex]

The error was from Canon in their LiveView (aka Evf) task:

Code: [Select]

      DebugMsg(171, 6, "Job are all in use.");
      assert("FALSE", "./LvCommon/LvJob.c", 156);

Was the camera in photo or movie mode? (todo: I should add this information in the logs)

Your ML/SETTINGS directory could be also helpful (to know what modules and settings are activated). It's best to make a copy of it while you can still reproduce the bug.

If the bug shows up with ML default settings, it's best to write the main Canon settings as well (such as shooting mode, FPS, video resolution...)

[OlRivrRat]

      @Alex

   Original Issue Find had User/Me Settings involved but subsequent tests were done with

"Clean" Reinstalls of each build with All Modules Off so M'L' Defaults should have been @ play.

Issue happens in both Live View & Movie but presents differently. In L'V', Cam' freezes, mirror

& shutter are heard returning to "Home" & the last L'V' Image remains on screen, Occasionally

the Screen goes Black. In Movie the Cam Freezes with Image on screen & the message that I

Posted before >

" [89] ?: stack overflow: free=0 used=-385938417 "

In Red @ the upper left of screen.

   In Stills Mode

Cam' is in Manual @ 200ISO, F5, 1/40Sec, AWB, AF FaceTrack, Single Shot, Raw+L'JPEG.

   In Movie Mode

Cam' is in Manual @ 200ISO, F5, 1/40Sec, AWB, AF FaceTrack, 1920x1080 @ 24FPS.

[IDA_ML]

OlRivrRat,

I have been testing the Sept. 27 Experimental build with my 100D for 3 days and all video functions seem to work fine.  I did not find any serious problems except for the behavior I described above.

Please check your SD card, especially make sure that the card is formatted in the camera before writing the ML package on it, also check if the card contacts are clean and the card has proper contact inside the camera.  If the camera is too slow and you get error messages without ML installed on it, this might be the problem.  Try different cards and see if Canon video recording works fine.  Other than that, your camera may have a problem.  Just check if your camera works perfectly OK with the Canon firmware before attempting to install ML.

[a1ex]

@IDA_ML: nope, 'stack overflow' is a (very serious) ML bug that might result (soft, usually recoverable) camera bricking - see e.g. this PR for low-level details. Therefore, solving it should have the highest priority.

If the filesystem would be corrupted or the card contacts would be weak, ML would refuse to boot (autoexec.bin has a checksum to prevent that).

@OlRivrRat: can you get screenshots of your Canon menus? I doubt I can reproduce it in QEMU, but others might be able to try.

A screenshot of the Debug -> Free Memory menu might also help (especially if the bug can be triggering after taking this screenshot).

[nikfreak]

Tried to replicate OlRivrRat's issue but can't replicate it. It will not freeze as OlRivrRat described. I would need a more detailed description on how to reproduce and I tried several settings like exp. override / -sim / globaldraw options / fps override. BUT:

got these errors when being in LV and adjusting shutter speed all the way down from 1/180 to BULB and then back to 32" , 20":

Code: [Select]

ASSERT: pReturnData->Engine_Address != 0xFFFFFFFF
at ./LvCommon/LvGainController.c:810, Evf:186c4
lv:1 mode:3

Evf stack: 1bf368 [1bf4b8-1be8b8]
0xUNKNOWN  @ d090:1bf4b0
0xUNKNOWN  @ 3a758:1bf488
0x0003A450 @ ff0d444c:1bf470
0xUNKNOWN  @ 3a480:1bf460
0xUNKNOWN  @ 47cb3c:1bf438
0xUNKNOWN  @ 3a508:1bf418
0x00018650 @ 1318c:1bf3a8
0x00001900 @ 186c0:1bf3a0
0x0044C468 @ 44c4ec:1bf368

Magic Lantern version : Nightly.2017Oct01.100D101
Mercurial changeset   : 3f68cd33c46d+ (crop_rec_4k) tip
Built on 2017-10-01 07:28:32 UTC by ml@ml-VirtualBox.
Free Memory  : 414K + 2534K

Code: [Select]

ASSERT: 0
at ./LvCommon/LvGainController.c:806, Evf:1869c
lv:1 mode:3

Evf stack: 1bf368 [1bf4b8-1be8b8]
0xUNKNOWN  @ d090:1bf4b0
0xUNKNOWN  @ 3a758:1bf488
0x0003A450 @ ff0d444c:1bf470
0xUNKNOWN  @ 3a480:1bf460
0xUNKNOWN  @ 47cb3c:1bf438
0xUNKNOWN  @ 3a508:1bf418
0x00018650 @ 1318c:1bf3a8
0x00001900 @ 18698:1bf3a0
0x0044C468 @ 44c4ec:1bf368

Magic Lantern version : Nightly.2017Oct01.100D101
Mercurial changeset   : 3f68cd33c46d+ (crop_rec_4k) tip
Built on 2017-10-01 07:28:32 UTC by ml@ml-VirtualBox.
Free Memory  : 414K + 2527K

Settin exp. level increments from 1/2 to 1/3 in Canon menu let's the camera freeze even before reaching BULB at 32".

[a1ex]

This one is likely MAX_ISO_BV in lens.h - maybe it's like 6D? (70D might require it as well)

Would be great if this kind of errors could be replicated in QEMU, but these require LiveView emulation...

[nikfreak]

Yes, true. It needs to be

Code: [Select]

#elif defined(CONFIG_100D)
#define MAX_ISO_BV 120
128 will work when Cfn "iso expansion" for video mode is active. But 128 would freeze switching to video mode if "iso expansion" is not set. So 120 is fine. Going to check 70D at a later time. Maybe other cameras need this too idk.

[nikfreak]

@OlRivrrat: once a new nightly (01 or 02 Oct containing MAX_ISO_BV fix) is out can you recheck the bug you encountered. Does it still happen?

[IDA_ML]

@IDA_ML: nope, 'stack overflow' is a (very serious) ML bug that might result (soft, usually recoverable) camera bricking - see e.g. this PR for low-level details. Therefore, solving it should have the highest priority.

Thank you for clarifying this to me, a1ex.  As a noob I was so happy that the Sept. 27 build works so well for me that I never thought, such a nasty bug may be lurking somewhere waiting for the right moment to brick my camera.  With regard to that I have a few questions:

1) Is it safe enough to continue testing the above 100D build or we should stop doing this until a solution is found?  If it is dangerous it might be a good idea to post a warning to the people so that nobody's camera gets bricked.

2) I have noticed that you tried to find a solution for the 5D3.  How safe  is it to continue experimenting with the latest Experimental build for that camera?

3) What exactly is "soft" bricking?  Can it be resolved just by pulling the battery out and restarting the camera or it requires more serious intervention?

Thank you.

[a1ex]

http://wiki.magiclantern.fm/faq#is_it_safe
https://bitbucket.org/hudson/magic-lantern/pull-requests/825
http://www.magiclantern.fm/forum/index.php?topic=20579.msg190486#msg190486
https://en.wikipedia.org/wiki/Brick_(electronics)#Soft_brick

"stack overflow" is bad because one task (no idea which one) is writing over the memory of some other task (again, no idea which one). Therefore, the side effects are completely unpredictable.

[IDA_ML]

Thank you, a1ex.  That explains a lot.  I'll keep experimenting - too much excited about the latest good stuff and can't help it.  If it breaks, "l'll keep both pieces".

[Danne]

I see all updates go into this branch Nikfreak:
100D_merge_fw101
Would be nice to have all updates also going straigt into crop_rec_4k to avoid merging issues when fixes starts piling up. Or is it testing first, then potential merging into crop_rec_4k? 

[IDA_ML]

Look guys, what the 100D is capable of at 11-bit bit lossless in the maximum resolution of 2520x1080 at 5x magnification:



 

This is a frame grab from a 150 frames video that I have just shot in the RAW_rec mode.  I found that, if the scene does not contain so much fine detail, I can shoot more than 250 frames in the above mode before recording stops.  The video was converted into a cDNG sequence using MLVDump and the frame grab was slightly edited in Adobe Camera RAW.

You need to click on the image to view it in full size.

[Danne]

Some bad ass details IDA_ML.
Here is a version with also lossless FRSP dng working with silent.mo:
- deleted -

branch:
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_100D_lossless_FRSP
Added changes from dfort here:
https://bitbucket.org/hudson/magic-lantern/pull-requests/858/fix-lossless-compression-on-frsp-for-eosm/diff

[DeafEyeJedi]

Indeed that's some bad ass image even @ 11-bit 2.5k from this little tiny beast @IDA_ML and thanks for sharing!

Can't wait to test out lossless FRSP dng w silent.mo -- Thanks for posting this build @Danne and to @dfort for the changes! 

[Danne]

@IDA_ML
Are there no focus pixel on output when filming lossless 2.5k?

[OlRivrRat]

                     @Alex

           Finally back. Bug is still doable. A bit diff' this morn' as LV & Cam just freeze without shutter & Mirror action &

no crash reports are on card. Have ScreenShots of Canon Menus, where would you like them? Tried to UpLoad to Yahoo

Photos but Yahoo seems to not like .PPM . If it is all the same to You, I am not going to try for the Mov Stack Overflow

again until You say it is Safe.

[OlRivrRat]

   For General Knowledge > I have been using 3 Different cards during these tests & the Bug only Bites when

running any of the 3 Sep Builds, Jul Builds work fine. Have Redownloaded Sep Builds & No Diff'.

[OlRivrRat]

           Test after Free Mem Screen Shot was kinda scary > produced stack overflow.

[nikfreak]

trying hard but I can't reproduce your error. i can take dozens of screenshots from "free memory". Even loaded a bunch of modules including lua but nope. No single crash or error message.

[nikfreak]

Ok, guess I am finding something. Please disable facetracking and report back! I switched to facetracking and the cam crashed.

[OlRivrRat]

           JPEGed all PPMs & UpLoaded to Yahoo Photos

https://photos.app.goo.gl/Toc1SUZ58qqgSVg82

[OlRivrRat]

                     @ NikF

           In Canon Menus, changed from Face Detect to FlexZone[] & got Immediate "Crash Detected" warning & Cam Kind of Froze, could still

navigate Up & Down that Menu Page but could do nothing else. Cam will no longer start with that card, card with 12Jul Build still works Fine.

Have some new Crash Logs now.

           This is latest

ASSERT: 0
at ./Memory/Memory.c:575, PropMgr:3a6f4
lv:0 mode:3

PropMgr stack: 18cee0 [18cf68-18bf68]
0xUNKNOWN  @ d090:18cf60
0x0003A670 @ 3a72c:18cf38
0x00008C14 @ 3a6f0:18cf18
0x0044C468 @ 44c4ec:18cee0

Magic Lantern version : Nightly.2017Sep30.100D101
Mercurial changeset   : d85e97b54bd2+ (100D_merge_fw101) tip
Built on 2017-09-30 12:45:05 UTC by jenkins@nightly.
Free Memory  : 584K + 2547K

[nikfreak]

Jizz.

I was initially using Flexizone []
Then switched to facetracking getting crash and read you were setting Flexizone(). I ofc tried that immediately out to replicate.
the cam crashed with some Memory.C error and seems now to be bricked (LCD stays black whatever i do). I recommend everybody not to play around with the AF settings until things get sorted! it somehow reminds me of:

https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff#comment-12338399

[nikfreak]

Ok, cam is alive again. After the crash I experienced described above the card seems to have somehow got an error (bootflag? cause unpacking ML zip to it didn't help). Now comes the great part. I now suffer the same sympthoms as canneloni and Nex. Cam will either get black LCD / or continuos LED when using one of the newer builds (always need to reformat and run ML installer each try). Using 12th July build from 1st post works w/o problems. I am taking a break now. This is going to get interesting cause 12th July build doesn't crash at all when playing around with Af settings... Don't try to reproduce you have been warned. I will try tomorrow if switching back the boot methd will work with the newer builds.