Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 910594

Summary: 75-net-description.rules not applied to /dev/hso0
Product: Red Hat Enterprise Linux 6 Reporter: Dan Williams <dcbw>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: azelinka, hesemeyt, kay, ngalvin, udev-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-31 09:08:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 909415, 960054, 1083163    
Attachments:
Description Flags
udev debug log of plugging in an Option GIO225 device none

Description Dan Williams 2013-02-12 23:05:21 UTC
Created attachment 696647 [details]
udev debug log of plugging in an Option GIO225 device

'hso' devices are a class of WWAN modems driven by the 'hso' driver, which provides one 'hsoX' net port and one or more 'ttyHSx' serial ports.  The serial ports *do* get the correct attributes (like ID_VENDOR_ID and ID_MODEL_ID) applied due to the very similar 75-tty-description.rules, but the netdev does not get those attributes applied.

I can't quite figure out why either; usb_id is getting executed and apparnetly returns the attributes, but they don't show up in the database as shown in 'udevadm info --export-db'.

Comment 1 Dan Williams 2013-02-12 23:06:32 UTC
All I get for udevadm info --export-db is:

P: /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0
E: DEVTYPE=wwan
E: INTERFACE=hso0
E: IFINDEX=6
E: SUBSYSTEM=net

where on more recent distros (eg, F17) we do see all the ID_VENDOR_ID, ID_MODEL_ID, ID_VENDOR_FROM_DATABASE, ID_MODEL_FROM_DATABASE, etc.

Comment 2 Dan Williams 2013-02-12 23:08:45 UTC
I'd at least expect to see the stuff that's set in the database for the ttyHSx devices, which includes:

E: ID_VENDOR=Option_N.V.
E: ID_VENDOR_ENC=Option\x20N.V.
E: ID_VENDOR_ID=0af0
E: ID_MODEL=Globetrotter_HSDPA_Modem
E: ID_MODEL_ENC=Globetrotter\x20HSDPA\x20Modem\x20\x20
E: ID_MODEL_ID=6971
E: ID_REVISION=0000
E: ID_SERIAL=Option_N.V._Globetrotter_HSDPA_Modem_Serial_Number
E: ID_SERIAL_SHORT=Serial_Number
E: ID_TYPE=generic
E: ID_BUS=usb
E: ID_USB_INTERFACES=:ffffff:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=hso
E: ID_VENDOR_FROM_DATABASE=Option
E: ID_MODEL_FROM_DATABASE=Globetrotter HSDPA Modem

Comment 3 Dan Williams 2013-02-12 23:11:32 UTC
Interesting bits from the udev logs include:

Feb 12 14:42:37 localhost udevd-work[6758]: remove db file for '/devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' in '/dev/.udev/db/net:hso0 = No such file or directory'
...
Feb 12 14:42:37 localhost udevd-work[6758]: IMPORT 'usb_id --export /device /pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' /lib/udev/rules.d/75-net-description.rules:6
Feb 12 14:42:37 localhost udevd-work[6758]: 'usb_id --export /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' started
...
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_VENDOR=Option_N.V.'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_VENDOR_ENC=Option\x20N.V.'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_VENDOR_ID=0af0'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_MODEL=Globetrotter_HSDPA_Modem'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_MODEL_ENC=Globetrotter\x20HSDPA\x20Modem\x20\x20'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_MODEL_ID=6971'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_REVISION=0000'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_SERIAL=Option_N.V._Globetrotter_HSDPA_Modem_Serial_Number'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_SERIAL_SHORT=Serial_Number'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_TYPE=generic'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_BUS=usb'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_USB_INTERFACES=:ffffff:'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_USB_INTERFACE_NUM=00'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb_id' (stdout) 'ID_USB_DRIVER=hso'
Feb 12 14:42:37 localhost udevd-work[6758]: 'usb_id --export /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' returned with exitcode 0
Feb 12 14:42:37 localhost udevd-work[6758]: IMPORT 'usb-db /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' /lib/udev/rules.d/75-net-description.rules:7
Feb 12 14:42:37 localhost udevd-work[6758]: 'usb-db /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' started
...
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'libudev: udev_device_new_from_syspath: '
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'device 0x2bc50d8 has devpath '//devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0''
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'libudev: udev_device_new_from_syspath: '
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'device 0x2bc52a8 has devpath '//devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net''
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'libudev: udev_device_new_from_syspath: '
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'device 0x2bc5438 has devpath '//devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0''
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'libudev: udev_device_new_from_syspath: '
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stderr) 'device 0x2bc5610 has devpath '//devices/pci0000:00/0000:00:1d.2/usb4/4-2''
...
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stdout) 'ID_VENDOR_FROM_DATABASE=Option'
Feb 12 14:42:37 localhost udevd-work[6758]: '/lib/udev/usb-db' (stdout) 'ID_MODEL_FROM_DATABASE=Globetrotter HSDPA Modem'
Feb 12 14:42:37 localhost udevd-work[6758]: 'usb-db /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/net/hso0' returned with exitcode 0
Feb 12 14:42:37 localhost udevd-work[6758]: RUN 'socket:@/org/freedesktop/hal/udev_event' /etc/udev/rules.d/90-hal.rules:2
Feb 12 14:42:37 localhost udevd-work[6758]: '/etc/sysconfig/network-scripts/net.hotplug' started


but none of those properties actually appear on in the database, despite usb_id and usb-db exiting with success.

Comment 5 Dan Williams 2013-02-12 23:43:07 UTC
Also, the hso0 device does not have ID_MM_CANDIDATE=1 set, which is applied to *all* net and tty devices.  The ttyHSx devices do have this set.

So it really looks like the hso-driven net devices just don't keep *any* database items that rules may set?

Comment 6 RHEL Program Management 2013-02-16 06:47:43 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 9 Harald Hoyer 2013-05-28 13:00:58 UTC
(In reply to Dan Williams from comment #5)
> Also, the hso0 device does not have ID_MM_CANDIDATE=1 set, which is applied
> to *all* net and tty devices.  The ttyHSx devices do have this set.
> 
> So it really looks like the hso-driven net devices just don't keep *any*
> database items that rules may set?

Hmm, if there is no device node, udev in RHEL-6 does not store any DB items, IIRC

Kay?

Comment 10 Dan Williams 2013-05-28 22:14:25 UTC
(In reply to Harald Hoyer from comment #9)
> (In reply to Dan Williams from comment #5)
> > Also, the hso0 device does not have ID_MM_CANDIDATE=1 set, which is applied
> > to *all* net and tty devices.  The ttyHSx devices do have this set.
> > 
> > So it really looks like the hso-driven net devices just don't keep *any*
> > database items that rules may set?
> 
> Hmm, if there is no device node, udev in RHEL-6 does not store any DB items,
> IIRC

What do you mean by no device node?  There definitely is an hso0 netdev, in both /sys and 'ifconfig', does udev on RHEL6 need something more than that?

Comment 11 Harald Hoyer 2013-05-31 09:08:51 UTC
rhel6 does not store properties in the udev db for network interfaces. sorry. not going to happen.

Comment 12 Dan Williams 2013-06-03 16:01:23 UTC
(In reply to Harald Hoyer from comment #11)
> rhel6 does not store properties in the udev db for network interfaces.
> sorry. not going to happen.

Ah, didn't realize that was the case, I assumed that since it stored them for ttys, it also stored them for any device.

Comment 13 Rashid Khan 2013-07-21 06:50:53 UTC
*** Bug 909415 has been marked as a duplicate of this bug. ***