[BUG] media: intel: ipu6/ivsc camera fails after hibernate on Dell Latitude 9430, stale INT343E software node (-EEXIST) Hello,

[Filippo Veneri <filippo.veneri@gmail.com>]

Hello,

I would like to report a hibernate/resume issue affecting the
in-kernel Intel IPU6/IVSC camera stack on a Dell Latitude 9430.

System
------
Laptop: Dell Latitude 9430
BIOS: 1.37.0 (11/25/2025)
Distro: Arch Linux
Kernel: 6.19.8-arch1-1
Camera sensor: ov02c10
Userspace test: libcamera / qcam 0.7.0

Relevant kernel modules in use
------------------------------
intel_ipu6
intel_ipu6_isys
ivsc_csi
ivsc_ace
mei_vsc
mei_vsc_hw
ov02c10

I do not appear to have any out-of-tree IPU6/IVSC DKMS modules installed.
The only related package is:
  intel-ivsc-firmware r13.3377801-1

Problem summary
---------------
The camera works after a cold boot.

After resuming from hibernate, the camera no longer works. qcam reports:
  "No camera detected"

At that point, reloading the camera modules does not recover the device.
In the failing post-hibernate state, the kernel eventually reports duplicate
software-node registration for INT343E and the IPU/IVSC probe fails
with -EEXIST.

What I tested
-------------
1. After a fresh boot, the following unload/reload sequence works and the camera
   still works afterwards:

   sudo modprobe -rv -w 5000 intel_ipu6_isys intel_ipu6 ov02c10
ivsc_csi ivsc_ace mei_vsc mei_vsc_hw
   sudo modprobe -v mei_vsc_hw
   sudo modprobe -v mei_vsc
   sudo modprobe -v ivsc_ace
   sudo modprobe -v ivsc_csi
   sleep 1
   sudo modprobe -v intel_ipu6
   sudo modprobe -v intel_ipu6_isys
   sudo modprobe -v ov02c10

   So a normal runtime unload/reload after cold boot seems OK.

2. After hibernate resume, the same module reload sequence does not recover the
   camera.

3. I also tried removing/rescanning the IPU PCI device after hibernate:

   echo 1 | sudo tee /sys/bus/pci/devices/0000:00:05.0/remove
   sleep 1
   echo 1 | sudo tee /sys/bus/pci/rescan

   After that, I still get the duplicate INT343E software-node failure.

Observed logs
-------------
In the failing post-hibernate case I observed messages like:

  intel-ipu6 0000:00:05.0: IPU6 in non-secure mode
  vsc-tp spi-INTC1094:00: wakeup firmware failed ret: -110
  intel_vsc intel_vsc: silicon stepping version is 0:2
  ivsc_csi intel_vsc-92335fcf-3203-4472-af93-7b4453ac29da: mei-csi
probed without device fwnode!

After remove/rescan or reprobe in the broken state:

  sysfs: cannot create duplicate filename '/kernel/software_nodes/INT343E'
  kobject: kobject_add_internal failed for INT343E with -EEXIST, don't
try to register things with the same name in the same directory.
  intel-ipu6 0000:00:05.0: Failed to register the IPU HID node
  intel-ipu6 0000:00:05.0: error -EEXIST: IPU6 bridge init failed
  intel-ipu6 0000:00:05.0: probe with driver intel-ipu6 failed with error -17
  ivsc_csi intel_vsc-92335fcf-3203-4472-af93-7b4453ac29da: probe with
driver ivsc_csi failed with error -17

One failing journal excerpt:

  Mar 21 14:46:45 omega kernel: sysfs: cannot create duplicate
filename '/kernel/software_nodes/INT343E'
  Mar 21 14:46:45 omega kernel: ipu_bridge_init+0x152/0xe30 [ipu_bridge]
  Mar 21 14:46:45 omega kernel: ipu6_pci_probe+0x530/0xc40 [intel_ipu6]
  Mar 21 14:46:45 omega kernel: kobject: kobject_add_internal failed
for INT343E with -EEXIST, don't try to register things with the same
name in the same directory.
  Mar 21 14:46:45 omega kernel: intel-ipu6 0000:00:05.0: Failed to
register the IPU HID node
  Mar 21 14:46:45 omega kernel: intel-ipu6 0000:00:05.0: error
-EEXIST: IPU6 bridge init failed
  Mar 21 14:46:45 omega kernel: intel-ipu6 0000:00:05.0: probe with
driver intel-ipu6 failed with error -17
  Mar 21 14:47:12 omega kernel: sysfs: cannot create duplicate
filename '/kernel/software_nodes/INT343E'
  Mar 21 14:47:12 omega kernel: Workqueue: events mei_cl_bus_rescan_work [mei]
  Mar 21 14:47:12 omega kernel: ipu_bridge_init+0x152/0xe30 [ipu_bridge]
  Mar 21 14:47:12 omega kernel: mei_csi_probe+0x54/0x2f0 [ivsc_csi]
  Mar 21 14:47:12 omega kernel: mei_cl_device_probe+0x74/0xc0 [mei]
  Mar 21 14:47:12 omega kernel: mei_cl_bus_rescan_work+0x325/0x3e0 [mei]
  Mar 21 14:47:12 omega kernel: kobject: kobject_add_internal failed
for INT343E with -EEXIST, don't try to register things with the same
name in the same directory.
  Mar 21 14:47:12 omega kernel: pci 0000:00:05.0: Failed to register
the IPU HID node
  Mar 21 14:47:12 omega kernel: ivsc_csi
intel_vsc-92335fcf-3203-4472-af93-7b4453ac29da: probe with driver
ivsc_csi failed with error -17

Expected result
---------------
The camera should continue to work after hibernate resume, or at least recover
cleanly after reprobe/module reload.

Actual result
-------------
After hibernate resume, the camera is not detected. Subsequent reprobe/reload
attempts can fail with duplicate software-node registration for INT343E and
IPU/IVSC probe errors (-EEXIST / -17).

Notes
-----
Because a fresh-boot unload/reload works, this does not look like a generic
module dependency or early boot ordering problem. It appears to be specific to
the hibernate/resume path.

Please let me know if I should collect any additional logs, enable
dynamic debug,
or test a specific patch.

Thanks,
filippo veneri