-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] OAK-D-POE intermittent failure - INTERNAL_ERROR_CORE #1103
Comments
Thanks for the bug report @laurence-diack-pk ! Just to clarify, the disconnects happen whilst you're running the app right? |
@SzabolcsGergely could you take a look at a crashdumps when you have a moment? |
Crash occurred during a XLink read, in XLinkPlatformRead, reason unknown. |
Yeah so it seems it can happen on pipeline load or also mid-run. It doesn't seem to be a very predictable failure and I'm having a hard time reproducing it consistently - for example I am looking at an instance right now where one of two cameras has disappeared, but I had to restart the host several times to get it into this state. Also it may well be that the crashdumps are not a 1:1 correlation with this failure, as I have observed cases where it does this and no crashdump is retrieved. Sorry for the vagueness, it's just sorta a black box from my end - if I can't communicate with the camera over network, it's hard to tell exactly what's going on. I was wondering if there's any additional logging I can pull of the device itself, or perhaps some way in which I could use the M8 connector to debug over uart or usb so I can get some insight into the state of the camera when it disappears like that. |
I trimmed down the pipeline slightly by conditionally removing nodes that weren't necessary (imageManip and the mono encoders/outs) and that seemed to help stability greatly, though I have still had a few intermittent failures. See: crashDump_0_18443010C15E9F0F00_9ed7c9ae4c232ff93a3500a585a6b1c00650e22c.json |
Problem Description
OAK-D-POE cameras intermittently disappear from the network and become unreachable via ping while running. The issue occurs unpredictably:
System Details
Observed Behavior
Crash Dumps
Two crash dumps have been collected, showing the following errors:
INTERNAL_ERROR_CORE
RTEMS_FATAL_SOURCE_EXCEPTION
Crash dump files:
crashDump_1_1844301031A3DC0E00_c7127782f2da45aac89d5b5b816d04cc45ae40be.json
crashDump_0_18443010C15E9F0F00_c7127782f2da45aac89d5b5b816d04cc45ae40be.json
Pipeline
The main app is C++ so I can't get a pipeline grab, but here's the basic setup:
Any insights would be greatly appreciated, thanks
The text was updated successfully, but these errors were encountered: