queue: fix kernel panic during multiple streams recovery #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A kernel panic is observed in the next stream when the previous multiple concurrent streams are both unexpectedly terminated at the same time.
Example gst commands used:
gst-launch-1.0 icamerasrc num-buffers=300 scene-mode=normal device-name= printfps=true io-mode=4 ! 'video/x-raw(memory:DMABuf),drm-format=UYVY,width=1920,height=1080' ! glimagesink icamerasrc num-buffers=300 scene-mode=normal device-name= printfps=true io-mode=4 ! 'video/x-raw(memory:DMABuf),drm-format=UYVY,width=1920,height=1080' ! glimagesink
Steps to reproduce:
Observe these in dmesg after executing step 2.
[ 261.859124] intel_ipu7_isys.isys intel_ipu7.isys.40: no buffer available, DRIVER BUG?
[ 262.660364] intel_ipu7_isys.isys intel_ipu7.isys.40: Runtime PM usage count underflow!
Tests conducted after fix: