Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1352685 - systemd - udev rule not fired in FC24 (worked on FC23)
Summary: systemd - udev rule not fired in FC24 (worked on FC23)
Keywords:
Status: CLOSED DUPLICATE of bug 1357822
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 24
Hardware: armv7hl
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-04 17:49 UTC by Gerhard Wiesinger
Modified: 2016-07-19 14:07 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 14:07:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gerhard Wiesinger 2016-07-04 17:49:34 UTC
Description of problem:

I had the following configuration on FC23 (systemd-222-14.fc23) which worked perfectly (ARM system):

cat /etc/udev/rules.d/8-usb-modem.rules
# Huawei E169
SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", ATTRS{product}=="HUAWEI Mobile", ATTRS{version}==" 1.10", ENV{ID_USB_INTERFACE_NUM}=="00" SYMLINK+="ttyUSB-modem-at"
SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", ATTRS{product}=="HUAWEI Mobile", ATTRS{version}==" 1.10", ENV{ID_USB_INTERFACE_NUM}=="01" SYMLINK+="ttyUSB-modem-aux"
SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", ATTRS{product}=="HUAWEI Mobile", ATTRS{version}==" 1.10", ENV{ID_USB_INTERFACE_NUM}=="02" SYMLINK+="ttyUSB-modem-third"

After upgrade to FC24 (systemd-udev-229-8.fc24.armv7hl) I have the problem that ttyUSB-modem-at link is not set.

lrwxrwxrwx 1 root root           7 Jul  1 18:49 ttyUSB-modem-aux -> ttyUSB2
lrwxrwxrwx 1 root root           7 Jul  1 18:49 ttyUSB-modem-third -> ttyUSB3

I tried also:

# OK:
KERNEL=="ttyUSB1", SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", ATTRS{product}=="HUAWEI Mobile", ATTRS{version}==" 1.10" SYMLINK+="ttyUSB-modem-at"
# NOT OK:
KERNEL=="ttyUSB1", DRIVERS=="option", SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", ATTRS{product}=="HUAWEI Mobile", ATTRS{version}==" 1.10" SYMLINK+="ttyUSB-modem-at"

So when something more specific correct filter is added it doesn't work any more (I tried several different more distinct filters):

I tried already: udevadm info --attribute-walk /dev/ttyUSB1 which looks good

First lines are:

   looking at device '/devices/platform/soc@01c00000/1c14000.usb/usb3/3-1/3-1.1/3-1.1:1.0/ttyUSB1/tty/ttyUSB1':
     KERNEL=="ttyUSB1"
     SUBSYSTEM=="tty"
     DRIVER==""

   looking at parent device '/devices/platform/soc@01c00000/1c14000.usb/usb3/3-1/3-1.1/3-1.1:1.0/ttyUSB1':
     KERNELS=="ttyUSB1"
     SUBSYSTEMS=="usb-serial"
     DRIVERS=="option1"
     ATTRS{port_number}=="0"

   looking at parent device '/devices/platform/soc@01c00000/1c14000.usb/usb3/3-1/3-1.1/3-1.1:1.0':
     KERNELS=="3-1.1:1.0"
     SUBSYSTEMS=="usb"
     DRIVERS=="option"
     ATTRS{authorized}=="1"
     ATTRS{bAlternateSetting}==" 0"
     ATTRS{bInterfaceClass}=="ff"
     ATTRS{bInterfaceNumber}=="00"
     ATTRS{bInterfaceProtocol}=="ff"
     ATTRS{bInterfaceSubClass}=="ff"
     ATTRS{bNumEndpoints}=="03"
     ATTRS{interface}=="Data Interface"
     ATTRS{supports_autosuspend}=="1"

This one looks also good:

ls -l /dev/serial/by-id/usb-ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ_HUAWEI_Mobile-if00-port0
lrwxrwxrwx 1 root root 13 Jul  1 18:49 /dev/serial/by-id/usb-ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ_HUAWEI_Mobile-if00-port0 -> ../../ttyUSB1

I don't think I did anything wrong so it looks to be a bug.

Any ideas?


Version-Release number of selected component (if applicable):
systemd-udev-229-8.fc24.armv7hl

How reproducible:
See above

Steps to Reproduce:
1. see above

Actual results:
Symlink not set

Expected results:
Symlink set

Additional info:
see above

Comment 1 Gerhard Wiesinger 2016-07-04 17:52:34 UTC
See also: https://github.com/systemd/systemd/issues/3657

Comment 2 Michal Schmidt 2016-07-19 14:07:54 UTC
Possibly this is another case of the trie building bug (bug 1357822).

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


Note You need to log in before you can comment on or make changes to this bug.