You are not logged in.

#1 2013-02-13 19:45:34

Kleperat
Member
Registered: 2012-12-03
Posts: 4

Android USB caused crash.

I plugged my mobile phone into one of my usb ports in order to charge it, several seconds later my computer locked up for thirty seconds or so.
Journalctl shows the following.

Feb 13 19:17:33 hostname kernel: usb 2-1: new high-speed USB device number 2 using xhci_hcd
Feb 13 19:17:49 hostname kernel: xhci_hcd 0000:03:00.0: Timeout while waiting for address device command
Feb 13 19:17:49 hostname kernel: [sched_delayed] sched: RT throttling activated
Feb 13 19:17:50 hostname kernel: usb 2-1: Device not responding to set address.
Feb 13 19:17:50 hostname kernel: usb 2-1: device not accepting address 2, error -71
Feb 13 19:18:12 hostname kernel: xhci_hcd 0000:03:00.0: Timeout while waiting for a slot
Feb 13 19:18:12 hostname kernel: xhci_hcd 0000:03:00.0: Stopped the command ring failed, maybe the host is dead
Feb 13 19:18:12 hostname kernel: xhci_hcd 0000:03:00.0: Abort command ring failed
Feb 13 19:18:12 hostname kernel: xhci_hcd 0000:03:00.0: HC died; cleaning up
Feb 13 19:18:12 hostname kernel: hub 2-0:1.0: cannot reset port 1 (err = -19)
Feb 13 19:18:12 hostname kernel: hub 2-0:1.0: cannot disable port 1 (err = -19)
Feb 13 19:18:12 hostname kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
Feb 13 19:18:12 hostname kernel: IP: [<ffffffffa010de33>] xhci_free_dev+0x63/0x160 [xhci_hcd]
Feb 13 19:18:12 hostname kernel: PGD a58e8067 PUD ab75f067 PMD 0 
Feb 13 19:18:12 hostname kernel: Oops: 0002 [#1] PREEMPT SMP 
Feb 13 19:18:12 hostname kernel: Modules linked in: vboxdrv(O) ip6t_REJECT xt_hl ip6t_rt nf_conntrack_ipv6 nf_de
Feb 13 19:18:13 hostname kernel:  battery
Feb 13 19:18:13 hostname kernel:  nf_nat
Feb 13 19:18:13 hostname kernel:  ac
Feb 13 19:18:13 hostname kernel:  microcode
Feb 13 19:18:13 hostname kernel:  button
Feb 13 19:18:13 hostname kernel:  evdev
Feb 13 19:18:13 hostname kernel:  thermal
Feb 13 19:18:13 hostname kernel:  video
Feb 13 19:18:13 hostname kernel:  nf_conntrack_ftp
Feb 13 19:18:13 hostname kernel:  pcspkr
Feb 13 19:18:13 hostname kernel:  nf_conntrack
Feb 13 19:18:13 hostname kernel:  iptable_filter
Feb 13 19:18:13 hostname kernel:  ip_tables
Feb 13 19:18:13 hostname kernel:  x_tables
Feb 13 19:18:13 hostname kernel:  ext4
Feb 13 19:18:13 hostname kernel:  crc16
Feb 13 19:18:13 hostname kernel:  jbd2
Feb 13 19:18:13 hostname kernel:  mbcache
Feb 13 19:18:13 hostname kernel:  sr_mod
Feb 13 19:18:13 hostname kernel:  cdrom
Feb 13 19:18:13 hostname kernel:  sd_mod
Feb 13 19:18:13 hostname kernel:  ahci
Feb 13 19:18:13 hostname kernel:  libahci
Feb 13 19:18:13 hostname kernel:  xhci_hcd
Feb 13 19:18:13 hostname kernel:  libata
Feb 13 19:18:13 hostname kernel:  scsi_mod
Feb 13 19:18:13 hostname kernel:  ehci_hcd
Feb 13 19:18:13 hostname kernel:  usbcore
Feb 13 19:18:13 hostname kernel:  usb_common
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel: CPU 1 
Feb 13 19:18:13 hostname kernel: Pid: 77, comm: khubd Tainted: G           O 3.7.7-1-ARCH #1 ASUSTeK Computer In
Feb 13 19:18:13 hostname kernel: RIP: 0010:[<ffffffffa010de33>] 
Feb 13 19:18:13 hostname kernel:  [<ffffffffa010de33>] xhci_free_dev+0x63/0x160 [xhci_hcd]
Feb 13 19:18:13 hostname kernel: RSP: 0018:ffff8800ab9c9d38  EFLAGS: 00010246
Feb 13 19:18:13 hostname kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb 13 19:18:13 hostname kernel: RDX: ffff8800ad488000 RSI: ffff880031ad6000 RDI: ffff8800ab878c00
Feb 13 19:18:13 hostname kernel: RBP: ffff8800ab9c9d78 R08: 0000000000000001 R09: ffffffffa01197ee
Feb 13 19:18:13 hostname kernel: R10: 0000000000000000 R11: 0000000000000418 R12: 0000000000000000
Feb 13 19:18:13 hostname kernel: R13: ffff880031ad6000 R14: ffff8800ad488000 R15: 0000000000000040
Feb 13 19:18:13 hostname kernel: FS:  0000000000000000(0000) GS:ffff8800b2220000(0000) knlGS:0000000000000000
Feb 13 19:18:13 hostname kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 13 19:18:13 hostname kernel: CR2: 0000000000000040 CR3: 00000000a5a96000 CR4: 00000000000427e0
Feb 13 19:18:13 hostname kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 13 19:18:13 hostname kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 13 19:18:13 hostname kernel: Process khubd (pid: 77, threadinfo ffff8800ab9c8000, task ffff8800ad4fe9a0)
Feb 13 19:18:13 hostname kernel: Stack:
Feb 13 19:18:13 hostname kernel:  ffff8800ad532000
Feb 13 19:18:13 hostname kernel:  ffff8800ab878c00
Feb 13 19:18:13 hostname kernel:  ffff8800ad6ee800
Feb 13 19:18:13 hostname kernel:  0000000000000001
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  ffff8800ad532000
Feb 13 19:18:13 hostname kernel:  ffff880031ad6000
Feb 13 19:18:13 hostname kernel:  ffff8800ad6ee800
Feb 13 19:18:13 hostname kernel:  00000000ffffff00
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  ffff8800ab9c9eb8
Feb 13 19:18:13 hostname kernel:  ffffffffa000b8c1
Feb 13 19:18:13 hostname kernel:  ffff8800ab9c9ea8
Feb 13 19:18:13 hostname kernel:  ffffffff814b9f55
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel: Call Trace:
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffffa000b8c1>] hub_thread+0xe31/0x1720 [usbcore]
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff814b9f55>] ? __schedule+0x435/0x920
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff8107be70>] ? abort_exclusive_wait+0xb0/0xb0
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffffa000aa90>] ? usb_remote_wakeup+0x70/0x70 [usbcore]
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff8107b180>] kthread+0xc0/0xd0
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff81010000>] ? perf_trace_xen_mmu_set_pte_at+0xb0/0x100
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff8107b0c0>] ? kthread_freezable_should_stop+0x70/0x70
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff814c2f6c>] ret_from_fork+0x7c/0xb0
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel:  [<ffffffff8107b0c0>] ? kthread_freezable_should_stop+0x70/0x70
Feb 13 19:18:13 hostname kernel: Code: 
Feb 13 19:18:13 hostname kernel: ff 
Feb 13 19:18:13 hostname kernel: ff 
Feb 13 19:18:13 hostname kernel: 83 
Feb 13 19:18:13 hostname kernel: f8 
Feb 13 19:18:13 hostname kernel: ed 
Feb 13 19:18:13 hostname kernel: 0f 
Feb 13 19:18:13 hostname kernel: 85 
Feb 13 19:18:13 hostname kernel: e5 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 49 
Feb 13 19:18:13 hostname kernel: 63 
Feb 13 19:18:13 hostname kernel: 85 
Feb 13 19:18:13 hostname kernel: c0 
Feb 13 19:18:13 hostname kernel: 04 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 31 
Feb 13 19:18:13 hostname kernel: db 
Feb 13 19:18:13 hostname kernel: 4d 
Feb 13 19:18:13 hostname kernel: 8b 
Feb 13 19:18:13 hostname kernel: a4 
Feb 13 19:18:13 hostname kernel: c6 
Feb 13 19:18:13 hostname kernel: 10 
Feb 13 19:18:13 hostname kernel: 01 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 4d 
Feb 13 19:18:13 hostname kernel: 8d 
Feb 13 19:18:13 hostname kernel: 7c 
Feb 13 19:18:13 hostname kernel: 24 
Feb 13 19:18:13 hostname kernel: 40 
Feb 13 19:18:13 hostname kernel: 0f 
Feb 13 19:18:13 hostname kernel: 0f 
Feb 13 19:18:13 hostname kernel: 1f 
Feb 13 19:18:13 hostname kernel: 80 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 48 
Feb 13 19:18:13 hostname kernel: 63 
Feb 13 19:18:13 hostname kernel: c3 
Feb 13 19:18:13 hostname kernel: <41> 
Feb 13 19:18:13 hostname kernel: 83 
Feb 13 19:18:13 hostname kernel: 27 
Feb 13 19:18:13 hostname kernel: fb 
Feb 13 19:18:13 hostname kernel: 83 
Feb 13 19:18:13 hostname kernel: c3 
Feb 13 19:18:13 hostname kernel: 01 
Feb 13 19:18:13 hostname kernel: 48 
Feb 13 19:18:13 hostname kernel: 69 
Feb 13 19:18:13 hostname kernel: c0 
Feb 13 19:18:13 hostname kernel: e8 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 49 
Feb 13 19:18:13 hostname kernel: 81 
Feb 13 19:18:13 hostname kernel: c7 
Feb 13 19:18:13 hostname kernel: e8 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 00 
Feb 13 19:18:13 hostname kernel: 
Feb 13 19:18:13 hostname kernel: RIP 
Feb 13 19:18:13 hostname kernel:  [<ffffffffa010de33>] xhci_free_dev+0x63/0x160 [xhci_hcd]
Feb 13 19:18:13 hostname kernel:  RSP <ffff8800ab9c9d38>
Feb 13 19:18:13 hostname kernel: CR2: 0000000000000040
Feb 13 19:18:13 hostname kernel: ---[ end trace 07ea92d389ac57d8 ]---

I'd quite like to know what casued this and if there's anything I could or should do about it.

00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
        Subsystem: ASUSTeK Computer Inc. Device 1147
        Kernel driver in use: ehci_hcd


00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
        Subsystem: ASUSTeK Computer Inc. Device 1147
        Kernel driver in use: ehci_hcd

03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
        Subsystem: ASUSTeK Computer Inc. Device 1059
        Kernel driver in use: xhci_hcd

Last edited by Kleperat (2013-02-13 19:54:29)

Offline

#2 2013-02-13 20:01:08

SolarBoyMatt
Member
From: Columbus, Ohio
Registered: 2012-01-07
Posts: 258
Website

Re: Android USB caused crash.

Does this happen every time? What device specifically are you trying to attach?

Feb 13 19:17:49 hostname kernel: xhci_hcd 0000:03:00.0: Timeout while waiting for address device command

I'm not quite sure what could have caused this either, but to me that line looks a little suspicious. Does this happen with all of your USB ports? If not it could be an issue with that xhci_hcd module or which ever USB port is using it.

Last edited by SolarBoyMatt (2013-02-13 20:02:32)

Offline

#3 2013-02-13 20:05:32

Kleperat
Member
Registered: 2012-12-03
Posts: 4

Re: Android USB caused crash.

I've tried plugging it into the same port it was in when the crash happened as well as the other usb ports, nothing unusual happened with any of them.

Offline

#4 2013-02-19 16:51:18

szym
Member
Registered: 2007-11-16
Posts: 14

Re: Android USB caused crash.

Just experienced the same thing yesterday. Twice.

Switching between two Android devices on the same hub (unplugging one, plugging the other) caused the oops in xhci_free_dev+0x63/0x160. The system still works, but newly plugged-in USB devices are no longer detected until reboot. Reboot has to be forced, because the kernel can't unmount /tmp or /home (probably in use by the failed module).

Offline

#5 2013-07-31 11:18:38

Legogris
Member
Registered: 2012-09-11
Posts: 36

Re: Android USB caused crash.

I just had this happen when connecting my ZTE Blade. My USB mouse stopped working and nothing happens when I reconnect it.

Offline

#6 2014-04-26 20:58:21

TheBodziO
Member
From: Dukla, Poland
Registered: 2006-07-28
Posts: 228
Website

Re: Android USB caused crash.

Sorry for necromancing… :>

I've got suspiciously similar problem with my Android dev and 3.14.1 kernel. Plugging it in causes the xhci_hcd subsystem to… well… see for yourself:

[127812.960714] usb 3-2.4: new high-speed USB device number 7 using xhci_hcd
[127828.027343] usb 3-2.4: device descriptor read/64, error -110
[127828.130427] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6.
[127828.197313] usb 3-2.4: new high-speed USB device number 8 using xhci_hcd
[127843.263914] usb 3-2.4: device descriptor read/64, error -110
[127843.367095] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7.
[127843.433942] usb 3-2.4: new high-speed USB device number 9 using xhci_hcd
[127848.433633] xhci_hcd 0000:00:14.0: Timeout while waiting for setup address command
[127853.636969] xhci_hcd 0000:00:14.0: Timeout while waiting for setup address command
[127853.840283] usb 3-2.4: device not accepting address 9, error -62
[127853.907234] usb 3-2.4: new high-speed USB device number 10 using xhci_hcd
[127858.906915] xhci_hcd 0000:00:14.0: Timeout while waiting for setup address command
[127864.110251] xhci_hcd 0000:00:14.0: Timeout while waiting for setup address command
[127864.313593] usb 3-2.4: device not accepting address 10, error -62
[127864.313874] hub 3-2:1.0: unable to enumerate USB device on port 4
[127869.323543] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command.
[127869.323553] xhci_hcd 0000:00:14.0: Assuming host is dying, halting host.
[127869.323588] xhci_hcd 0000:00:14.0: HC died; cleaning up
[127869.323645] usb 3-2: USB disconnect, device number 2
[127869.324051] usb 3-3: USB disconnect, device number 6
[127869.324321] usb 3-9: USB disconnect, device number 4
[127869.490680] usb 3-10: USB disconnect, device number 5
[128621.099541] xhci_hcd 0000:03:00.0: remove, state 4
[128621.099552] usb usb6: USB disconnect, device number 1
[128621.106240] xhci_hcd 0000:03:00.0: USB bus 6 deregistered
[128621.106251] xhci_hcd 0000:03:00.0: remove, state 4
[128621.106261] usb usb5: USB disconnect, device number 1
[128621.112031] xhci_hcd 0000:03:00.0: USB bus 5 deregistered
[128621.112128] xhci_hcd 0000:00:14.0: remove, state 4
[128621.112136] usb usb4: USB disconnect, device number 1
[128621.112344] xhci_hcd 0000:00:14.0: USB bus 4 deregistered
[128621.112349] xhci_hcd 0000:00:14.0: remove, state 1
[128621.112354] usb usb3: USB disconnect, device number 1
[128621.113132] xhci_hcd 0000:00:14.0: USB bus 3 deregistered

Leaving the phone plugged in and reloading the xhci_hcd module fixes the problem—host gets up, devices spring to life and the phone charges as intended. The sole question remains: why? ;}


It's not the best thing when they call you a "member" you know… wink

Offline

Board footer

Powered by FluxBB