[Bug 2093315] Re: Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device

This bug is awaiting verification that the linux-oem-6.11/6.11.0-1012.12
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.11'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.11' to 'verification-failed-
noble-linux-oem-6.11'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2093315

Title:
Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1
device

Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.11 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
New
Status in linux-oem-6.11 source package in Oracular:
Invalid
Status in linux source package in Plucky:
New
Status in linux-oem-6.11 source package in Plucky:
Invalid

Bug description:
[Impact]
While using iio_info to read the devices info, it stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device

[Fix]
The patch invalidates this kind of device, so interface won't be created

https://lore.kernel.org/lkml/20250109040006.1273797-1-acelan.kao@canonical.com/T/

[Test]
1. Boots up the machine with this USB camera which comes with an invalid i2c sensor
Bus 003 Device 002: ID 0408:5473 Quanta Computer, Inc. HP 5MP Camera
2. Run iio_info, it should return the iio information immediately

[Where problems could occur]
It won't impact the existing iio devices, the index lower than 0 is invalid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2093315/+subscriptions