Skip to content

queue: fix kernel panic during multiple streams recovery#30

Open
jluiI wants to merge 1 commit intointel:mainfrom
jluiI:fix_kernel_panic
Open

queue: fix kernel panic during multiple streams recovery#30
jluiI wants to merge 1 commit intointel:mainfrom
jluiI:fix_kernel_panic

Conversation

@jluiI
Copy link

@jluiI jluiI commented Oct 10, 2025

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:

  1. Run the gst command above.
  2. Kill gst before it completes.
  3. Rerun the gst command above.
  4. Observe kernel panic

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:

  1. Rerun the steps above.
  2. Open 2 terminals and run 1 gst command in each terminal and kill both at the same time. Use Mobaxterm multiexec feature to execute the command and kill both of them together.

A kernel panic is observed in the next stream when the previous multiple concurrent streams are both unexpectedly terminated at the same time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant