Bug 539808

Summary: udevd-work tries to set non-existent power level attribute for fingerprint scanner
Product: [Fedora] Fedora Reporter: Bradley <bbaetz>
Component: libfprintAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 12CC: bnocera, eddie, harald, jfeeney, nphilipp, pingou
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-17 14:50:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bradley 2009-11-21 05:40:35 UTC
Description of problem:

On bootup, I get the following message printed to the screen:

Starting udev: udevd-work[404]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1:1.0/power/level} for writing: No such file or directory

That device is a fingerprint sensor on my laptop:

Bus 006 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor

The power directory has a 'wakeup' file, but not a 'level' one. There isn't a kernel driver; its all handled in userspace through fprint (although I don't actually use it)

The message isn't logged anywhere; I took a photo with my phone camera to be able to copy it down exactly

Version-Release number of selected component (if applicable):

udev-145-12.fc12.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Boot computer
2.
3.
  
Actual results:

See error message

Expected results:

Don't see error message

Additional info:

If you know how I /can/ adjust the power level, that'd be good - powertop complains about it, but obviously can't do anything about it.

Comment 1 Bradley 2010-01-03 14:00:32 UTC
*** Bug 551968 has been marked as a duplicate of this bug. ***

Comment 2 Harald Hoyer 2010-01-26 11:12:35 UTC
/lib/udev/rules.d/65-libsane.rules:ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'"

$ rpm  -qf /lib/udev/rules.d/65-libsane.rules
sane-backends-1.0.20-10.fc12.x86_64

Comment 3 Harald Hoyer 2010-01-26 12:52:59 UTC
can you please give me the output of:

# grep -r level /{etc,lib}/udev/rules.d

Comment 4 Bradley 2010-01-26 13:03:58 UTC
[root@plum ~]# grep -r level /{etc,lib}/udev/rules.d
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="5501", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="2500", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="2580", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00bb", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00bc", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00bd", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="00ca", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="05ba", ATTRS{idProduct}=="0007", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="05ba", ATTRS{idProduct}=="0008", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="05ba", ATTRS{idProduct}=="000a", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="061a", ATTRS{idProduct}=="0110", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="147e", ATTRS{idProduct}=="2016", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="1600", ATTR{power/level}="auto"
/etc/udev/rules.d/60-fprint-autosuspend.rules:SUBSYSTEM=="usb", ATTRS{idVendor}=="08ff", ATTRS{idProduct}=="2810", ATTR{power/level}="auto"
/lib/udev/rules.d/70-printers.rules:# Low-level USB device add trigger
/lib/udev/rules.d/70-printers.rules:# Low-level USB device remove trigger
/lib/udev/rules.d/65-libsane.rules:ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'test -e /sys/$env{DEVPATH}/power/level && echo on > /sys/$env{DEVPATH}/power/level'"
/lib/udev/rules.d/70-acl.rules:# HPLIP devices (necessary for ink level check and HP tool maintenance)

Comment 5 Harald Hoyer 2010-01-26 14:04:34 UTC
$ rpm -qf /etc/udev/rules.d/60-fprint-autosuspend.rules
libfprint-0.1.0-14.pre2.fc12.x86_64

reassigning

Comment 6 Bastien Nocera 2010-01-26 14:51:34 UTC
That's Matthew's work.

Comment 7 Bastien Nocera 2010-08-17 14:50:36 UTC
Matthew fixed this already.

*** This bug has been marked as a duplicate of bug 505438 ***