Skip to contentSkip to conversation

IPU6 "Transfer FIFO overflow" errors when CPU is idle

PATCH Hans de Goede 2 participants 2 messages Oct 8, 2025 – Oct 9, 2025 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Hi,

While testing raw image capture for sensor calibratino on a Dell XPS 9320 (Raptor Lake, ov01a10, LJCA, IVSC)

I noticed pretty bad flickering of the images coming from the camera with the bottom part of the image flickering from the actual image to fully white. This gets combined with errors like these in dmesg pointing at an isys/CSI2 receiver problem:

[  144.764888] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Transfer FIFO overflow
[  144.764902] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet
[  144.809886] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame short packet
[  144.809910] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet
[  144.834517] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Transfer FIFO overflow
[  144.834541] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet
[  144.876643] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame short packet
[  144.876665] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet

...

To reproduce this apply the following diff to libcamera:

src/libcamera/pipeline/simple/simple.cpp +1 -1
index c816cffc..ef336721 100644
@@ -253,7 +253,7 @@ namespace {
 static const SimplePipelineInfo supportedDevices[] = {
 	{ "dcmipp", {}, false },
 	{ "imx7-csi", { { "pxp", 1 } }, false },
-	{ "intel-ipu6", {}, true },
+	{ "intel-ipu6", {}, false },
 	{ "intel-ipu7", {}, true },
 	{ "j721e-csi2rx", {}, true },
 	{ "mtk-seninf", { { "mtk-mdp", 3 } }, false },

Build it and then run:

./redhat-linux-build/src/apps/qcam/qcam -r gles

This will disable the softwareISP and instead has qcam using a shader to debayer/demosaic the image.

The same flickering does not happen when using the softwareISP.

After trying some other things I had a hunch I and thought maybe the problem is that doing things this way leaves the CPU mostly idle.

So I ran:

md5sum /dev/zero&

from the terminal to put 1 CPU core at 100% load and then rerun qcam in raw + shader debayer mode:

./redhat-linux-build/src/apps/qcam/qcam -r gles

And the problem is gone. So I believe that the problem is that when the CPU is not significantly loaded some other resource, maybe the ring-bus, maybe the DDR4 RAM speed is clocked down causing problems for the CSI2 receiver...

Regards,

Hans

#1 lore raw

Hi Hans,

Quoted 56 lines · Hans de Goede

Hi,

While testing raw image capture for sensor calibratino on a Dell XPS 9320 (Raptor Lake, ov01a10, LJCA, IVSC)

I noticed pretty bad flickering of the images coming from the camera with the bottom part of the image flickering from the actual image to fully white. This gets combined with errors like these in dmesg pointing at an isys/CSI2 receiver problem:

[  144.764888] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Transfer FIFO overflow
[  144.764902] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet
[  144.809886] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame short packet
[  144.809910] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet
[  144.834517] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Transfer FIFO overflow
[  144.834541] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet
[  144.876643] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame short packet
[  144.876665] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-2 error: Inter-frame long packet

...

To reproduce this apply the following diff to libcamera:

src/libcamera/pipeline/simple/simple.cpp +1 -1
index c816cffc..ef336721 100644
@@ -253,7 +253,7 @@ namespace {
 static const SimplePipelineInfo supportedDevices[] = {
 	{ "dcmipp", {}, false },
 	{ "imx7-csi", { { "pxp", 1 } }, false },
-	{ "intel-ipu6", {}, true },
+	{ "intel-ipu6", {}, false },
 	{ "intel-ipu7", {}, true },
 	{ "j721e-csi2rx", {}, true },
 	{ "mtk-seninf", { { "mtk-mdp", 3 } }, false },

Build it and then run:

./redhat-linux-build/src/apps/qcam/qcam -r gles

This will disable the softwareISP and instead has qcam using a shader to debayer/demosaic the image.

The same flickering does not happen when using the softwareISP.

After trying some other things I had a hunch I and thought maybe the problem is that doing things this way leaves the CPU mostly idle.

So I ran:

md5sum /dev/zero&

from the terminal to put 1 CPU core at 100% load and then rerun qcam in raw + shader debayer mode:

Quoted 6 lines

./redhat-linux-build/src/apps/qcam/qcam -r gles

And the problem is gone. So I believe that the problem is that when the CPU is not significantly loaded some other resource, maybe the ring-bus, maybe the DDR4 RAM speed is clocked down causing problems for the CSI2 receiver...

The driver is supposed to account for this somehow, using cpu_latency_qos_*(). ISYS_PM_QOS_VALUE is set to 300 today. Probably a smaller value (but how much?) could help; also tuning the watermark setting could address this (with likely a lesser effect on power consumption).

As a matter of fact, I've also seen this on Thinkpads occasionally but I thought it was a sensor issue.

Signature · 3 lines
Kind regards,

Sakari Ailus