System reboots instead of shutting down if xhci is enabled in BIOS and USB hub is connected

Bug #1606030 reported by Hasan Mahmood
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

When I connect the usb hub built into my monitor (http://www.samsung.com/uk/support/model/LS27D85KTSN/XU), the system will reboot instead of shutting down when I do a shut down. If I disable XCHI in the BIOS, the problem does not happen. If I disconnect the hub and enable XHCI, the problem does not occur.

Outputs of various commands are attached.

Possibly related bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=76291
https://bugzilla.kernel.org/show_bug.cgi?id=66171

WORKAROUND: Use kernel parameter: xhci_hcd.quirks=0x0004b810

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: hmahmood 3688 F.... pulseaudio
 /dev/snd/controlC0: hmahmood 3688 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Jul 24 11:18:09 2016
HibernationDevice: RESUME=UUID=0477be12-31b0-423b-9277-22490ca71561
InstallationDate: Installed on 2016-07-23 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=503e032f-c205-4594-a47f-cdc58ffa5dba ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic N/A
 linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2016
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0358.2016.0606.1423
dmi.board.name: NUC5i5RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H40999-503
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0358.2016.0606.1423:bd06/06/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:

Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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

Can you submit an SRU request[0] to the kernel team mailing list:
<email address hidden>

[0] https://wiki.ubuntu.com/StableReleaseUpdates

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

Not sure how to submit the SRU request. The page linked above talks about verifying patches, and there are none attached to this bug.

Revision history for this message
penalvch (penalvch) wrote :

Hasan Mahmood, to clarify, prior to reporting this issue or after, have you tested an upstream patch to confirm it addresses the issue for your hardware?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

No, I have not tested any upstream patches. Looking at those kernel bugs, I am not even sure how to get my hands on a patched kernel.

Revision history for this message
penalvch (penalvch) wrote :

Hasan Mahmood, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your help.

Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

Same behavior with 4.7 upstream kernel.

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

Hasan Mahmood, do either of the following kernel parameters provide a WORKAROUND:
reboot=pci
reboot=bios

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

Neither options make a difference.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Hasan Mahmood, to keep this relevant to upstream, could you please continue to test the latest mainline kernel (now 4.8-rc3) and advise to the results?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

Problem still exists in 4.8-rc3.

tags: added: kernel-bug-exists-upstream-4.8-rc3
Revision history for this message
penalvch (penalvch) wrote :

Hasan Mahmood, 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 Mathias Nyman 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.

tags: removed: kernel-bug-exists-upstream-4.7
tags: added: latest-bios-0358
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

Email sent to linux-usb.

Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :
Revision history for this message
Hasan Mahmood (hasan-mahm) wrote :

As per Mathias's email, setting xhci_hcd.quirks=0x0004b810 solves this problem. See message here: http://www.spinics.net/lists/linux-usb/msg146618.html

penalvch (penalvch)
description: updated
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.