So, “Where problems could occur” is meant to be a prompt for you, the domain expert, to identify the types of regression that might be possible with this update (and so should inform the test case - we should be checking that those regressions don't occur).
For a hardware support package like this, there are a range of common possibilities: 1. Sometimes, patches are just adding new PCI IDs (or similar) to the driver. In these cases, the only likely failure modes are a misbuild, or the appearance of a new supported device changing system behaviour in unwanted ways (One possible example here would be if a system played video fine without HW acceleration but adding the necessary FW to enable HW decoding exposed driver bugs which caused video playback to crash). * Notably, these type of updates take a device from definitely not working to (hopefully) working. There's virtually no¹ risk of regression on devices which currently work; this is an easy SRU. It's also generally easy for us, in the SRU team, to *see* that this is an easy SRU. 2. Sometimes, patches add both device IDs and a bunch of code that's only executed on the new devices. This is roughly the same case as above. * It might not be obvious to us, in the SRU team, that an update is in this category. You, as the domain expert, can help by identifying it for us :) 3. Sometimes, patches for adding hardware support require changing code that's shared with existing devices. In this case, the scope for problems extends beyond the new device - mistakes or oversights in the changes could break existing, working devices. Here you can help as a domain expert by identifying the set of existing devices that might be affected, how a problem might manifest (is it likely to fail completely? Is it likely to have sub-optimal quality? Is it likely to increase CPU usage but otherwise be invisible?), and how we will test to ensure users with existing, working, devices *don't* experience a regression. In this particular case, I see there's a bunch of data tables being added, some extra enum values, some extra descriptors in a format array; these are all type 1/2 updates. But I also see some changes to common code, and some changes to existing data arrays, what looks like a type 3 change. For these we want to know the scope of the hardware that this might apply to and whether that hardware is *currently* expected to work or not. ¹: Well, very little risk of regression. Misbuilds could break existing working hardware! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2084059 Title: OVTI08F4:00: number of CSI2 data lanes 2 is not supported Status in ipu6-drivers package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in ipu6-drivers source package in Noble: Won't Fix Status in linux source package in Noble: Won't Fix Status in linux-oem-6.11 source package in Noble: Fix Released Status in ipu6-drivers source package in Oracular: Incomplete Status in linux source package in Oracular: Fix Committed Status in linux-oem-6.11 source package in Oracular: Invalid Status in ipu6-drivers source package in Plucky: Fix Released Status in linux source package in Plucky: In Progress Status in linux-oem-6.11 source package in Plucky: Invalid Bug description: [SRU Justification] [Impact] OVTI08F4 camera sensor is used in a different hardware config that is not currently supported: ``` $ sudo dmesg ... usbio-i2c usbio-i2c.3.auto: hid INTC10B6 uid VIC0 new uid1 ov08x40 i2c-OVTI08F4:00: number of CSI2 data lanes 2 is not supported ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -22 ov08x40 i2c-OVTI08F4:00: probe with driver ov08x40 failed with error -22 ``` [Fix] Proposed fix in: * https://github.com/intel/ipu6-drivers/pull/286 There are two parts. One in the kernel tree that is to be SRU-ed in this pull request. It adds two additional link frequencies so that ipu-bridge may probe this case. The other part is in the camera sensor driver itself that goes to ipu6-drivers. [Test Case] With patch applied, install kernel and intel-ipu6-dkms from -proposed pocket: ``` $ sudo dmesg ... intel_ipu7_psys.psys intel_ipu7.psys.40: psys probe minor: 0 intel_ipu7_isys.isys intel_ipu7.isys.40: bind ov08x40 14-0036 nlanes is 2 port is 0 intel_ipu7_isys.isys intel_ipu7.isys.40: All sensor registration completed. ``` Check if camera actually works: ``` $ sudo gst-launch-1.0 icamerasrc ! autovideosink ``` [Where problems could occur] This is a new hardware configuration for OVTI08F4. Expect further issues. [Other Info] So far this configuration is bound to Intel Lunar Lake platform that is only supported by v6.11 kernels and ipu6-drivers/oracular, ipu7/drivers/oracular. Nominate for linux/oracular, linux- oem-6.11/noble and linux-unstable-6.12. ========== original bug report ========== $ sudo dmesg|grep ov0 [ 4.793991] ov08x40 i2c-OVTI08F4:00: number of CSI2 data lanes 2 is not supported [ 4.793997] ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -22 [ 4.815076] ov08x40 i2c-OVTI08F4:00: probe with driver ov08x40 failed with error -22 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: gdm 1400 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-10-18 (4 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) IwConfig: lo no wireless extensions. enx00e04c6801fa no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Dell Pro 14 Premium PA14250 Package: linux (not installed) ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1006-oem root=UUID=32c3d524-0a3b-48e2-802c-9cd4ca0503a3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-1006.6-oem 6.11.0 RelatedPackageVersions: linux-restricted-modules-6.11.0-1006-oem N/A linux-backports-modules-6.11.0-1006-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: noble Uname: Linux 6.11.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/06/2024 dmi.bios.release: 89.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.7.31 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AFTPASS dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 137.1 dmi.modalias: dmi:bvnDellInc.:bvr89.7.31:bd09/06/2024:br89.7:efr137.1:svnDellInc.:pnDellPro14PremiumPA14250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CE4: dmi.product.family: Dell Pro Laptops dmi.product.name: Dell Pro 14 Premium PA14250 dmi.product.sku: 0CE4 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: gdm 1385 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-10-18 (4 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) IwConfig: lo no wireless extensions. enx00e04c6801fa no wireless extensions. wwan0 no wireless extensions. MachineType: Dell Inc. Dell Pro 14 Premium PA14250 Package: linux (not installed) ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-9006-oem root=UUID=32c3d524-0a3b-48e2-802c-9cd4ca0503a3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-9006.6+exp.21-oem 6.11.0 RelatedPackageVersions: linux-restricted-modules-6.11.0-9006-oem N/A linux-backports-modules-6.11.0-9006-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: noble Uname: Linux 6.11.0-9006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/06/2024 dmi.bios.release: 89.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.7.31 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: AFTPASS dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 137.1 dmi.modalias: dmi:bvnDellInc.:bvr89.7.31:bd09/06/2024:br89.7:efr137.1:svnDellInc.:pnDellPro14PremiumPA14250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CE4: dmi.product.family: Dell Pro Laptops dmi.product.name: Dell Pro 14 Premium PA14250 dmi.product.sku: 0CE4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2084059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
