FS#27122 - [libfprint] error opening file (power/control)

Attached to Project: Arch Linux
Opened by Vasyl Demin (zersaa) - Saturday, 19 November 2011, 16:16 GMT
Last edited by Tom Gundersen (tomegun) - Friday, 25 November 2011, 11:17 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Thinkpad T510, x86_64

During boot, after "Waiting for UDev uevents to be processes" I see:
udevd[246]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/power/control} for writing: No such file or directory
udevd[246]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/power/control} for writing: No such file or directory

Downgrading initscripts solves my problem (2011.11.3-1 -> 2011.10.2-1).

I've attached lspci and lsusb, the problem seems to be related to fingerprint sensor.

ls /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/power
async runtime_active_kids runtime_enabled runtime_status runtime_usage

   lspci (2.5 KiB)
   lsusb (0.6 KiB)
This task depends upon

Closed by  Tom Gundersen (tomegun)
Friday, 25 November 2011, 11:17 GMT
Reason for closing:  Upstream
Comment by Tom Gundersen (tomegun) - Sunday, 20 November 2011, 06:01 GMT
Initscripts should not be at fault here. At worst maybe we are now printing some errors that used to be hidden.

Do you have any custom udev rules that are trying to enable usb autosuspend? It looks like your device does not support that (there is no power/control file), so I guess the problem is that the custom rules apply to some devices that they should not.

Do you see any effects of this problem except for the error message, in particular is there a difference between the new and old initscripts except for the error message?
Comment by Vasyl Demin (zersaa) - Sunday, 20 November 2011, 11:28 GMT
>Do you see any effects of this problem except for the error message
No, fingerprint sensor seems to work.

You're right, I get error messages only if /lib/udev/rules.d/60-fprint-autosuspend.rules exist. I've attached this file, it belongs to libfprint 0.4.0-2.
   60-fprint-autosuspend.rules (1.9 KiB)
Comment by Tom Gundersen (tomegun) - Sunday, 20 November 2011, 12:21 GMT
This looks like a bug in libfprint to me. Reassigned.
Comment by Jan Alexander Steffens (heftig) - Sunday, 20 November 2011, 13:19 GMT
Does the error disappear if you replace every "power/control" with "power/level"?
Comment by Vasyl Demin (zersaa) - Sunday, 20 November 2011, 14:37 GMT
No,
udevd[258]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/power/level} for writing: No such file or directory

These rules contain my device 147e:2016 two times (why?), so I get two error strings.

As I said,
ls -1 /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/power
async
runtime_active_kids
runtime_enabled
runtime_status
runtime_usage

But I found 'level' and 'control' in other directory.
ls -1 /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/power
active_duration
async
autosuspend
autosuspend_delay_ms
connected_duration
control
level
persist
runtime_active_kids
runtime_active_time
runtime_enabled
runtime_status
runtime_suspended_time
runtime_usage
wakeup
wakeup_active
wakeup_active_count
wakeup_count
wakeup_hit_count
wakeup_last_time_ms
wakeup_max_time_ms
wakeup_total_time_ms
Comment by Jan Alexander Steffens (heftig) - Sunday, 20 November 2011, 15:11 GMT
Upstream problem then. Report the bug at FDO.

Looks like the udev rules need fixing.

Loading...