Bug 1597333 - xHCI host controller not responding, assume dead
Summary: xHCI host controller not responding, assume dead
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-02 15:34 UTC by jeremy9856
Modified: 2018-10-01 21:35 UTC (History)
23 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-01 21:35:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description jeremy9856 2018-07-02 15:34:34 UTC
Hello,

I see this message that appear :

xHCI host controller not responding, assume dead
HC died; cleaning up

There is more infos here : https://bbs.archlinux.org/viewtopic.php?id=236536

It seems that there is a patch available that will be included in 4.18 but it would be nice if it could be included in current Fedora 28 kernel (don't know if it's the latest version) :

https://marc.info/?l=linux-usb&m=152544392822763&w=2

Thanks !

Comment 1 Laura Abbott 2018-07-02 15:54:47 UTC
THat's labeled as TESTPATCH so I really don't want to pick it up. It looks like something was supposed to be queued in the maintainer's tree so if you can find it there, we can see about bringing it in.

Comment 4 jeremy9856 2018-07-12 05:34:11 UTC
The relevant patch is this one https://patchwork.kernel.org/patch/10479909/ and it has been commited to kernel 4.18 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.18-rc4&id=229bc19fd7aca4f37964af06e3583c1c8f36b5d6

Can we include it in Fedora ?

Comment 5 Robert-André Mauchin 🐧 2018-07-12 19:16:48 UTC
Can we backport the fix? With 4.17, I'm hitting this bug constantly.

Comment 6 Jeremy Cline 2018-07-13 14:30:50 UTC
I've picked it up to be included in the next stable kernel update (v4.17.7).

Comment 7 jeremy9856 2018-07-14 07:35:05 UTC
Thank you.

Comment 8 Justin M. Forbes 2018-07-17 15:50:24 UTC
This patch alone doesn't even build, it is being dropped from 4.17.7 until I can find a better solution.

Comment 9 Jeremy Cline 2018-07-17 16:02:01 UTC
It looks like it depends on commit bcaa9d5c5900 ("xhci: Create new structures to store xhci port information") at least, which a non-trivial patch. It may be safer to just wait for the 4.18 rebase or for that patch to also get picked up for stable. Sorry about that.

Comment 10 Robert-André Mauchin 🐧 2018-07-17 16:08:55 UTC
I'm using 4.18.0-0.rc4.git1.1.fc29.x86_64 from Rawhide in the meantime because this bug kills my Bluetooth mouse often. It works fine. If 4.18 is planned to come to F28 at one point it would be great.

Thanks for your work.

Comment 11 jeremy9856 2018-08-03 05:53:04 UTC
It seem that there is a backport of the patch

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784921/comments/6

Comment 12 Alexey Brodkin 2018-08-03 07:44:22 UTC
Jeremy, you may even get packaged kernel for Fedora 28 which contains that back-port (it's in 4.17.10+) from Bodhi, see https://bodhi.fedoraproject.org/updates/FEDORA-2018-cc812838fb

Comment 13 Máirín Duffy 2018-08-10 04:06:54 UTC
Hi, in case it's useful info:

I have a 3rd gen Yoga X1 Carbon, out of nowhere got hit with this bug when using an external DVD drive while running on kernel-4.17.5-200.fc28.x86_64. (It worked fine all day then suddenly stopped being able to mount anything and I saw the error described here.)

I upgraded to kernel kernel-4.17.12-200.fc28.x86_64 but am still hitting the issue.

Comment 14 Laura Abbott 2018-10-01 21:11:18 UTC
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 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  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 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 15 Robert-André Mauchin 🐧 2018-10-01 21:27:34 UTC
@Laura: I don't have this issue anymore on F29, and was not having it on kernel-4.18.9-200.fc28

Comment 16 Laura Abbott 2018-10-01 21:35:30 UTC
thanks for letting us know


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