Bug 1581520

Summary: usb device attach fails with msg from upowerd
Product: [Fedora] Fedora Reporter: Patrick Stanistreet <pystanis>
Component: upowerAssignee: Richard Hughes <rhughes>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 28CC: rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-12 11:37:20 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:
Attachments:
Description Flags
log msgs from journalctl none

Description Patrick Stanistreet 2018-05-23 01:42:31 UTC
Created attachment 1440381 [details]
log msgs  from journalctl

Description of problem:
insertion of usb device fails with msg from upowerd

device does work on  fedora 27


May 22 18:05:08 localhost.localdomain kernel: usb 7-1: FTDI USB Serial Device converter now attached to ttyUSB1
May 22 18:05:08 localhost.localdomain upowerd[1190]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:02.4/0000:03:00.0/usb7/7-1
May 22 18:05:08 localhost.localdomain upowerd[1190]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:02.4/0000:03:00.0/usb7/7-1/7-1:1.1
May 22 18:05:08 localhost.localdomain upowerd[1190]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:02.4/0000:03:00.0/usb7/7-1/7-1:1.0
May 22 18:05:21 localhost.localdomain ModemManager[785]: <warn>  (ttyUSB0): serial port closing_wait was reset!
May 22 18:05:21 localhost.localdomain ModemManager[785]: <warn>  (ttyUSB1): serial port closing_wait was reset!



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

device is a go board  and have created a modified udev rule that worked in f27


How reproducible:

f27  insert device  status ok and can use gtkterm 
f28  insert device  status as above    gtkterm no connection


Steps to Reproduce:
1.  
2.
3.

Actual results:


Expected results:




Additional info:

attached is journalctl -f     messages from usb connect of the go board



these dmesg   imply a connection and look normal but not correct in journal
[  508.585127] usb 7-1: new high-speed USB device number 4 using xhci_hcd
[  508.773534] usb 7-1: New USB device found, idVendor=0403, idProduct=6010
[  508.773545] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  508.773550] usb 7-1: Product: Dual RS232-HS
[  508.773555] usb 7-1: Manufacturer: FTDI
[  508.780529] ftdi_sio 7-1:1.0: FTDI USB Serial Device converter detected
[  508.780577] usb 7-1: Detected FT2232H
[  508.780859] usb 7-1: FTDI USB Serial Device converter now attached to ttyUSB0
[  508.781107] ftdi_sio 7-1:1.1: FTDI USB Serial Device converter detected
[  508.781146] usb 7-1: Detected FT2232H
[  508.781645] usb 7-1: FTDI USB Serial Device converter now attached to ttyUSB1

Comment 1 Patrick Stanistreet 2018-06-12 11:37:20 UTC
Not sure what has changed but I am current with updates since the
release and now the usb connection to the go fpga board is
working.