USB 3.1 controller does weird magic: appears after Windows 10, disappears otherwise

Bug #1649039 reported by Nazar Mokrynskyi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB 3.1/Thunderbolt 3) ports, BIOS version F20b.

Both ports are "sleeping" on cold start - I can't boot from USB device plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as of December 11 doesn't see anything (no messages in dmesg).

But magically situation changes when involve Windows 10 to the party. I boot into Windows PE based on Windows 10 and it happily see flash drive and my Nexus 6P connected to both ports.

After this without unplugging mentioned devices I reboot into Ubuntu and "magic" - both flash drive and Nexus 6P work fine through these 2 USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't see anything.

nazar-pc  ~  lspci -d ::0c03 -k
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
 Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI Controller
 Kernel driver in use: xhci_hcd
0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge]
 Subsystem: Device 2222:1111
 Kernel driver in use: xhci_hcd

But things are even more interesting: when I unplug either Nexus 6P or flash drive and then plug back - they still work fine! But as soon as I unplug both of them - Ubuntu doesn't see anything and doesn't post anything into dmesg until I boot into Windows 10 again. Interestingly, USB 3.1 controller disappears:

nazar-pc  ~  lspci -d ::0c03 -k
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
 Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI Controller
 Kernel driver in use: xhci_hcd

nazar-pc  ~   cat /proc/version_signature
Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nazar-pc 3227 F.... pulseaudio
 /dev/snd/controlC1: nazar-pc 3227 F.... pulseaudio
CurrentDesktop: Custom
DistroRelease: Ubuntu 17.04
EcryptfsInUse: Yes
IwConfig: Error: [Errno 2] Немає такого файла або каталогу
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash intel_pstate=disable initrd=/efi/ubuntu_efi_stub/initrd.img
ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-10-lowlatency N/A
 linux-backports-modules-4.9.0-10-lowlatency N/A
 linux-firmware 1.162
RfKill: Error: [Errno 2] Немає такого файла або каталогу
Tags: zesty
Uname: Linux 4.9.0-10-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 11/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F20b
dmi.board.asset.tag: Default string
dmi.board.name: Z170X-UD5 TH-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: Z170X-UD5 TH
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1649039

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : CRDA.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : JournalErrors.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : Lspci.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : Lsusb.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : ProcEnviron.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : ProcModules.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : PulseList.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : UdevDb.txt

apport information

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :

No, it didn't start happening after update/upgrade because my PC is few weeks old and I didn't check 3.1 support ever before.

With mainline kernel 4.9.0-040900-lowlatency behavior is exactly the same

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :

I can do more testing if you need it or if you don't have access to this or similar motherboard.

penalvch (penalvch)
tags: added: bios-outdated-f20 kernel-bug-exists-upstream-4.9
removed: 3.1 type-c usb
tags: added: latest-bios-f20b
removed: bios-outdated-f20
Revision history for this message
penalvch (penalvch) wrote :

Nazar Mokrynskyi, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Greg Kroah-Hartman CC linux-usb)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :

Here is my message on mailing list: https://marc.info/?l=linux-usb&m=148237345520582

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.