USB unplug crashes system - Assuming host is dying, halting host

[Guru Prasad]

Occasionally, when I unplug my Android phone (connected over USB), my machine crashes.
At first, I presumed the entire machine had halted since the keyboard and mouse stopped working.
However, I'm still able to SSH in although the screen is completely non-responsive. Pressing the power button on the CPU seems to bring up a window with Ubuntu's power options.

My Ubuntu version:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

Kernel version:
Linux nixentor 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I see the following output on dmesg:
[15563.650717] ------------[ cut here ]------------
[15563.650730] WARNING: CPU: 7 PID: 0 at /build/linux-3r7mVb/linux-3.13.0/drivers/usb/host/xhci-ring.c:1590 handle_cmd_completion+0xe56/0xe60()
[15563.650732] Modules linked in: qcserial usb_wwan usbserial ip6table_filter ip6_tables iptable_filter ip_tables x_tables cachefiles cfg80211 rfcomm bnep nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi btusb bluetooth usb_storage mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops joydev videobuf2_core snd_hda_codec_realtek videodev snd_usb_audio snd_usbmidi_lib 8812au(OX) snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_seq serio_raw snd_hwdep radeon snd_pcm mei_me snd_page_alloc mei snd_seq_device snd_timer snd ttm drm_kms_helper soundcore drm parport_pc i2c_algo_bit ppdev lp wmi parport video intel_smartconnect shpchp acpi_pad mac_hid hid_generic usbhid hid e1000e ahci psmouse ptp libahci pps_core
[15563.650804] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G OX 3.13.0-91-generic #138-Ubuntu
[15563.650807] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014
[15563.650809] 0000000000000000 ffff88041edc3d90 ffffffff81729906 0000000000000000
[15563.650813] 0000000000000009 ffff88041edc3dc8 ffffffff8106987d ffff880404062d60
[15563.650817] ffff8804040606b0 0000000000000010 00000004040606b0 ffff8804041a0000
[15563.650822] Call Trace:
[15563.650824] <IRQ> [<ffffffff81729906>] dump_stack+0x64/0x82
[15563.650836] [<ffffffff8106987d>] warn_slowpath_common+0x7d/0xa0
[15563.650840] [<ffffffff8106995a>] warn_slowpath_null+0x1a/0x20
[15563.650845] [<ffffffff815848c6>] handle_cmd_completion+0xe56/0xe60
[15563.650852] [<ffffffff8109aa65>] ? check_preempt_curr+0x75/0xa0
[15563.650857] [<ffffffff815861eb>] xhci_irq+0x33b/0xa50
[15563.650861] [<ffffffff8109fe35>] ? sched_clock_cpu+0xb5/0x100
[15563.650865] [<ffffffff81586911>] xhci_msi_irq+0x11/0x20
[15563.650870] [<ffffffff810c27be>] handle_irq_event_percpu+0x4e/0x220
[15563.650874] [<ffffffff810c29cd>] handle_irq_event+0x3d/0x60
[15563.650878] [<ffffffff810c5497>] handle_edge_irq+0x77/0x130
[15563.650886] [<ffffffff81016e3e>] handle_irq+0x1e/0x30
[15563.650893] [<ffffffff8173c79d>] do_IRQ+0x4d/0xc0
[15563.650898] [<ffffffff81731e2d>] common_interrupt+0x6d/0x6d
[15563.650900] <EOI> [<ffffffff815daaf2>] ? cpuidle_enter_state+0x52/0xc0
[15563.650910] [<ffffffff815daae8>] ? cpuidle_enter_state+0x48/0xc0
[15563.650915] [<ffffffff815dac3c>] cpuidle_idle_call+0xdc/0x220
[15563.650921] [<ffffffff8101e3fe>] arch_cpu_idle+0xe/0x30
[15563.650924] [<ffffffff810c1be1>] cpu_startup_entry+0xc1/0x2b0
[15563.650931] [<ffffffff8104278d>] start_secondary+0x21d/0x2d0
[15563.650934] ---[ end trace d9b5447d0ddb440a ]---
[15565.486066] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command.
[15565.486075] xhci_hcd 0000:00:14.0: Assuming host is dying, halting host.
[15565.486120] xhci_hcd 0000:00:14.0: HC died; cleaning up
[15568.853140] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[15568.853149] xhci_hcd 0000:00:14.0: Abort the command ring, but the xHCI is dead.
[15569.057055] usb 3-14: device not accepting address 92, error -108
[15574.055575] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[15574.055587] xhci_hcd 0000:00:14.0: Abort the command ring, but the xHCI is dead.
[15579.054167] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[15579.054176] xhci_hcd 0000:00:14.0: Abort the command ring, but the xHCI is dead.
[15584.052706] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[15584.052715] xhci_hcd 0000:00:14.0: Abort the command ring, but the xHCI is dead.
[15584.052841] usb 3-3: USB disconnect, device number 2
[15584.052854] usb 3-3.2: USB disconnect, device number 13
[15584.085404] usb 3-4: USB disconnect, device number 3
[15584.108793] usb 3-6: USB disconnect, device number 8
[15584.164694] usb 3-7: USB disconnect, device number 9
[15584.165426] usb 3-8: USB disconnect, device number 10
[15584.165634] usb 3-9: USB disconnect, device number 11
---
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: guru 2492 F.... pulseaudio
 /dev/snd/controlC0: guru 2492 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=bebe3ee7-4a81-4980-93ee-80daafd63772
InstallationDate: Installed on 2014-05-04 (808 days ago)
InstallationMedia: This
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=2e88994f-d021-4c26-a209-6b1a3aece4fc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-92-generic N/A
 linux-backports-modules-3.13.0-92-generic N/A
 linux-firmware 1.127.22
RfKill:
 1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-92-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-08-24 (696 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: Z97 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/23/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1603564/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

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

apport-collect 1603564

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.

[Joseph Salisbury (jsalisbury)]

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.7 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.7-rc7

[Guru Prasad (guru2411)]

I don't think I can run apport-collect. So far, I've had it happen about 3-4 times over 30 hours of uptime. If it does happen again, _and_ I'm able to start a vnc session, _and_ said vnc session works, I will definitely update this bug report with the logs.

[Guru Prasad (guru2411)]

First off, sorry if this comment is redundant.

I cannot say for sure whether the issue happened after an update. I run apt-get upgrade very often and thus cannot peg it down to an update. I have definitely not upgraded (dist-upgrade) my Ubuntu version.

I will give the latest kernel a shot, but, I have no way to 100% reproduce this bug every time. This may lead to false negatives.

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Guru Prasad (guru2411)]

apport information

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Guru Prasad, 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 understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]