[Bug 192831] acer_wmi spamming logs with iio-sensor-prox Could not open input accel Operation not permitted

[Bug 192831] acer_wmi spamming logs with iio-sensor-prox Could not open input accel Operation not permitted

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192831

Andy Shevchenko (andy.shevchenko@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andy.shevchenko@gmail.com

--- Comment #1 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
What kernel version is it?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 192831] acer_wmi spamming logs with iio-sensor-prox Could not open input accel Operation not permitted

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192831

Andy Shevchenko (andy.shevchenko@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INSUFFICIENT_DATA

--- Comment #2 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
The bug is against v4.10, now we are almost at v5.16. Please, retest with the
latest kernel and fell free to reopen if the bug is still reproducible.

Note v4.10 is LTS, so if the bug is still there in the latest stable version of
it, but there is no such bug in the latest vanilla, try to bisect the fix
commit and then you may require to backport it.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 192831] acer_wmi spamming logs with iio-sensor-prox Could not open input accel Operation not permitted

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=192831

--- Comment #3 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
(In reply to Andy Shevchenko from comment #2)

> Note v4.10 is LTS, so if the bug is still there in the latest stable version
> of it, but there is no such bug in the latest vanilla, try to bisect the fix
> commit and then you may require to backport it.

Oops, v4.9 and v4.14 are, v4.10 is not LTS (v5.10 is), sorry for the wrong
message above. It means if you are okay to switch either to vanilla or whatever
LTS kernel, which you want to have working it's fine. But in any case you need
to retest with latest vanilla first.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.