Hi, something really weird is going on today on my system--debian stretch on an Apple MacBookPro 12,1.
Some time ago I noticed a strange issue with USB, which prevented the keyboard and the trackpad to work after bootup (they are both USB devices on MacBookPro's). Here's an extract of the kernel logs that I collected at the time: > Mar 29 09:06:25 alan kernel: usb 2-3: device not accepting address 2, error > -62 > Mar 29 09:06:36 alan kernel: usb 2-3: device not accepting address 3, error > -62 > Mar 29 09:06:55 alan kernel: xhci_hcd 0000:00:14.0: Stopped the command ring > failed, maybe the host is dead > Mar 29 09:06:55 alan kernel: xhci_hcd 0000:00:14.0: Abort command ring > failed Mar 29 09:06:55 alan kernel: xhci_hcd 0000:00:14.0: HC died; > cleaning up Mar 29 09:06:55 alan kernel: xhci_hcd 0000:00:14.0: HC died; > cleaning up Mar 29 09:06:55 alan kernel: xhci_hcd 0000:00:14.0: HC died; > cleaning up Mar 29 09:06:56 alan kernel: usb 2-3: device not accepting > address 4, error -108 > Mar 29 09:06:56 alan kernel: usb usb2-port3: couldn't allocate usb_device After some rest, everything started working again, and I didn't worried--till this morning, when I rebooted! Again, keyboard and trackpad no longer worked. Again I brutally switched of the laptop, and tried to wait some time, but nothing, this time it didn't help! I suspect the misbehaviour depends on the upgrade I carried on yesterday, since this was my first reboot since then. The really strange thing is that even grub now is sooo slow to show up. It takes 30 secs or more! Obviously, the keyboard does not work there. After some additional time, the kernel boots up, but it stalls for 30 seconds on the step "loading initial ramdisk". After that, it boots up correctly, displays the login manager, but as I said I have no keyboard nor trackpad. I tried many times. In the end I tried and plugged external usb mouse and keyboard. After bootup they didn't work either, but after some additional 30 seconds they started working, together with the integrated keyboard and the trackpad. No idea what's going on. I rebooted without the external usb devices plugged in, and waited for several minutes, but nothing happened, keyboard and trackpad didn't start working. I rebooted again, like before with the two external usb devices attached, and like before everything started working after some pretty long time. As I said, the culprit might be yesteday's upgrade. Among others, the kernel was upgraded: Start-Date: 2017-04-11 07:33:56 Commandline: packagekit role='update-packages' Requested-By: solitone (1000) Upgrade: [...] linux-image-4.9.0-2-amd64:amd64 (4.9.13-1, 4.9.18-1 ) [...] Everything worked fine before. Now the first steps (starting from grub) in the bootup process are unbelievably slow, and the laptop's keyboard and trackpad don't work unless I wait much time and do some weird ritual, like plugging in some external usb devices and again wait and wait. Now everything works well, but I fear that at the next reboot I'll have to struggle, hope, and pray that I can use my sytem again! Here are the kernel error message that I've collected during the last reboot: solitone@alan:~$ sudo journalctl -k -b -1 -p 3 -- Logs begin at Sun 2017-02-12 21:33:16 CET, end at Wed 2017-04-12 15:42:11 CEST. -- Apr 12 14:42:14 alan kernel: brcmfmac 0000:03:00.0: firmware: failed to load brcm/brcmfmac43602-pcie.txt (-2) Apr 12 14:42:14 alan kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c Apr 12 14:42:14 alan kernel: brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) Apr 12 14:42:15 alan kernel: brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error Apr 12 14:42:15 alan kernel: brcmfmac: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp3s0 type 10 failed: err=-16 Apr 12 14:42:21 alan kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 Apr 12 14:42:22 alan kernel: usb 2-3: device not accepting address 2, error -62 Apr 12 14:42:33 alan kernel: usb 2-3: device not accepting address 3, error -62 Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb ffff8ae9df53b840 failed to resubmit (22) Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb ffff8ae9df53b000 failed to resubmit (22) Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb ffff8ae9df53b900 failed to resubmit (22) Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb ffff8ae9df53bf00 failed to resubmit (22) Apr 12 14:42:39 alan kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up Apr 12 14:42:39 alan kernel: bcm5974 1-5:1.2: could not read from device Apr 12 14:46:12 alan kernel: INFO: task kworker/1:1:46 blocked for more than 120 seconds. Apr 12 14:46:12 alan kernel: Not tainted 4.9.0-2-amd64 #1 Apr 12 14:46:12 alan kernel: "echo 0 > /proc/sys/kernel/ hung_task_timeout_secs" disables this message. Apr 12 14:48:12 alan kernel: INFO: task kworker/1:1:46 blocked for more than 120 seconds. Apr 12 14:48:12 alan kernel: Not tainted 4.9.0-2-amd64 #1 Apr 12 14:48:12 alan kernel: "echo 0 > /proc/sys/kernel/ hung_task_timeout_secs" disables this message. As expected, kworker complaints depends on XHCI: solitone@alan:~$ sudo journalctl -k -b -1 -p 4 [...] Apr 12 14:48:12 alan kernel: INFO: task kworker/1:1:46 blocked for more than 120 seconds. Apr 12 14:48:12 alan kernel: Not tainted 4.9.0-2-amd64 #1 Apr 12 14:48:12 alan kernel: "echo 0 > /proc/sys/kernel/ hung_task_timeout_secs" disables this message. Apr 12 14:48:12 alan kernel: ffff8ae9e2d43c00 0000000000000000 ffff8ae9e4857040 ffff8ae9eec981c0 Apr 12 14:48:12 alan kernel: ffff8ae9e4da0000 ffffa26c00dffb70 ffffffff973f6403 000000005480022c Apr 12 14:48:12 alan kernel: 00ff8ae9e4da0000 ffff8ae9eec981c0 0000000000000246 ffff8ae9e4857040 Apr 12 14:48:12 alan kernel: Call Trace: Apr 12 14:48:12 alan kernel: [<ffffffff973f6403>] ? __schedule+0x233/0x6d0 Apr 12 14:48:12 alan kernel: [<ffffffff973f68d2>] ? schedule+0x32/0x80 Apr 12 14:48:12 alan kernel: [<ffffffff973f9ca3>] ? schedule_timeout +0x243/0x310 Apr 12 14:48:12 alan kernel: [<ffffffff96ee52f6>] ? add_timer+0x126/0x200 Apr 12 14:48:12 alan kernel: [<ffffffff973f72e1>] ? wait_for_completion +0xf1/0x130 Apr 12 14:48:12 alan kernel: [<ffffffff96ea17f0>] ? wake_up_q+0x70/0x70 Apr 12 14:48:12 alan kernel: [<ffffffffc0401afe>] ? xhci_setup_device+0x19e/ 0x730 [xhci_hcd] Apr 12 14:48:12 alan kernel: [<ffffffffc0387e21>] ? hub_port_init+0x181/0xba0 [usbcore] Apr 12 14:48:12 alan kernel: [<ffffffffc038c1d3>] ? hub_event+0xb43/0x14d0 [usbcore] Apr 12 14:48:12 alan kernel: [<ffffffff96e90384>] ? process_one_work +0x184/0x410 Apr 12 14:48:12 alan kernel: [<ffffffff96e9065d>] ? worker_thread+0x4d/0x480 Apr 12 14:48:12 alan kernel: [<ffffffff96e90610>] ? process_one_work +0x410/0x410 Apr 12 14:48:12 alan kernel: [<ffffffff96e90610>] ? process_one_work +0x410/0x410 Apr 12 14:48:12 alan kernel: [<ffffffff96e965ce>] ? kthread+0xce/0xf0 Apr 12 14:48:12 alan kernel: [<ffffffff96e24701>] ? __switch_to+0x2c1/0x6c0 Apr 12 14:48:12 alan kernel: [<ffffffff96e96500>] ? kthread_park+0x60/0x60 Apr 12 14:48:12 alan kernel: [<ffffffff973fb2f5>] ? ret_from_fork+0x25/0x30
