Created attachment 1123128 [details] dmesg Description of problem: [ 1.250069] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 1.250071] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.250073] usb usb2: Product: xHCI Host Controller [ 1.250075] usb usb2: Manufacturer: Linux 4.3.4-300.fc23.x86_64 xhci-hcd [ 1.250077] usb usb2: SerialNumber: 0000:00:14.0 [ 1.250856] usb: failed to peer usb2-port4 and usb1-port7 by location (usb2-port4:none) (usb1-port7:usb2-port3) [ 1.250859] usb usb2-port4: failed to peer to usb1-port7 (-16) [ 1.250860] usb: port power management may be unreliable Which I believe is causing problems devices connected to the USB ports. Such as the mouse appearing to be a sleep or it may even be when another USB device is communicating it pauses the mouse. Version-Release number of selected component (if applicable): Linux 4.3.4-300.fc23.x86_64 How reproducible: Every boot and every time using the mouse. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: No warning of usb peering problems. USB devices working correctly. Additional info: dmesg attached
lsusb Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0cf3:3121 Atheros Communications, Inc. Bus 001 Device 033: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 005: ID 048d:8350 Integrated Technology Express, Inc. Bus 001 Device 004: ID 06cb:3150 Synaptics, Inc. Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 08:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
Can provide dmidecode and acpidump
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
Sorry for delay in replying. I did upgrade to Fedora 24 during July (faulty screen on old laptop, wife inherited this particular machine). Kernel-4.5.5-300.fc24 the problem appears to be resolved. Kernel-4.7.5-200.fc24 dmesg reports [ 5.394495] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 5.394497] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.394499] usb usb2: Product: xHCI Host Controller [ 5.394501] usb usb2: Manufacturer: Linux 4.7.5-200.fc24.x86_64 xhci-hcd [ 5.394502] usb usb2: SerialNumber: 0000:00:14.0 [ 5.394625] hub 2-0:1.0: USB hub found [ 5.394636] hub 2-0:1.0: 9 ports detected lsusb Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 007: ID 0cf3:3121 Atheros Communications, Inc. Bus 002 Device 005: ID 048d:8350 Integrated Technology Express, Inc. Bus 002 Device 004: ID 06cb:3150 Synaptics, Inc. Bus 002 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Only problem with USB I can see is USB 2-7 [ 7.265723] usb 2-7: new full-speed USB device number 6 using xhci_hcd [ 7.430768] usb 2-7: New USB device found, idVendor=0cf3, idProduct=3121 [ 7.430769] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Error/warning [ 22.428296] usb 2-7: device descriptor read/64, error -110 Then new USB found for USB 2-7 [ 27.694458] usb 2-7: New USB device found, idVendor=0cf3, idProduct=3121 [ 27.694466] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.