-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello Alan, On Wed, 2016-08-10 at 17:20 -0400, Alan Stern wrote: > On Wed, 10 Aug 2016, Ritesh Raj Sarraf wrote: > > The device was disconnected electronically. > > How often does this happen? After the disconnect occurs, does the card > reader remain disconnected until the next power cycle? > If I look at the systemd journal logs, this has been happening for months, or rather right from the time I've installed Linux on it. The bug does not trigger rightaway on boot. It mostly looks to be happening when power saving values are enabled for the USB devices. I said mostly, because for example, on this boot, while the power savings are active, the kernel has not reported any error. Part of the reason could also be because I blacklisted this specific USB device id under my power saving tool. But I need to check/confirm that. Once the bug is triggered, reboots still inherit the problem. A proper power off and start is the way to avoid the bug then. > > Upon reboot too, I noticed the error reported way early during initrd. > > > > After a full poweroff and boot, the usb device was back to being listed as > > normal. > > > > > > Is this a sign of the USB device going bad? > > Probably. > > > Or is it just another bug in Linux USB? > > Another?? Are there other bugs affecting you? > I guess so. I get frequent resets on my USB port for some of the hardware. kernel: usb 2-1: reset high-speed USB device number 17 using xhci_hcd I initially thought of this to be a faulty cable. But the same cable works fine on another laptop. I'm not sure if these resets could be related to the card reader issue above. May 15 17:06:55 learner kernel: usb 2-4: new high-speed USB device number 15 using xhci_hcd May 15 17:07:00 learner kernel: usb 2-4: new high-speed USB device number 16 using xhci_hcd May 15 17:07:00 learner kernel: usb 2-4: New USB device found, idVendor=0bda, idProduct=0129 May 15 17:07:00 learner kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 15 17:07:00 learner kernel: usb 2-4: Product: USB2.0-CRW May 15 17:07:00 learner kernel: usb 2-4: Manufacturer: Generic May 15 17:07:00 learner kernel: usb 2-4: SerialNumber: 20100201396000000 May 15 17:07:00 learner mtp-probe[26302]: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4" May 15 17:07:00 learner mtp-probe[26302]: bus: 2, device: 16 was not an MTP device May 15 17:07:00 learner laptop-mode[26375]: Laptop mode May 15 17:07:00 learner laptop-mode[26376]: enabled, active May 15 17:07:01 learner pkexec[26399]: Debian-gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemo May 15 17:07:01 learner gnome-settings-daemon.desktop[7174]: Error executing command as another user: Not authorized May 15 17:07:01 learner gnome-settings-daemon.desktop[7174]: This incident has been reported. May 15 17:07:01 learner kernel: usb 2-4: USB disconnect, device number 16 May 15 17:07:01 learner kernel: usb 2-4: new high-speed USB device number 17 using xhci_hcd May 15 17:07:01 learner kernel: usb 2-4: New USB device found, idVendor=0bda, idProduct=0129 May 15 17:07:01 learner kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 15 17:07:01 learner kernel: usb 2-4: Product: USB2.0-CRW May 15 17:07:01 learner kernel: usb 2-4: Manufacturer: Generic May 15 17:07:01 learner kernel: usb 2-4: SerialNumber: 20100201396000000 May 15 17:07:01 learner mtp-probe[26438]: checking bus 2, device 17: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4" May 15 17:07:01 learner mtp-probe[26438]: bus: 2, device: 17 was not an MTP device May 15 17:07:01 learner laptop-mode[26511]: Laptop mode May 15 17:07:01 learner laptop-mode[26512]: enabled, active May 15 17:08:01 learner CRON[26551]: pam_unix(cron:session): session opened for user news by (uid=0) May 15 17:08:01 learner CRON[26552]: (news) CMD (if [ -x /etc/news/leafnode/do- fetch-news ]; then /etc/news/leafnode/do-fetch-news; fi) May 15 17:08:03 learner fetchnews[26554]: news.gmane.org: connected to 80.91.229.13:119, reply: 200 May 15 17:08:03 learner systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... May 15 17:08:03 learner systemd[1]: Reloading Laptop Mode Tools. May 15 17:08:03 learner systemd[1]: Started Laptop Mode Tools - Battery Polling Service. May 15 17:08:03 learner laptop-mode[26612]: Laptop mode May 15 17:08:03 learner laptop_mode[26558]: Laptop mode May 15 17:08:03 learner laptop-mode[26613]: enabled, active [unchanged] May 15 17:08:03 learner laptop_mode[26558]: enabled, active [unchanged] May 15 17:08:03 learner systemd[1]: Reloaded Laptop Mode Tools. > > If a sign of a faulty USB device, what measures can be taken as a user? Is > it > > possible to effectively disable such devices, so that they do not consume > any > > power at all ? > > Maybe your BIOS settings will let you disable it. > No luck there. The BIOS is very limited with no such option to disable. The laptop is from Lenovo. http://shop.lenovo.com/us/en/laptops/lenovo/yoga-laptop-series/yoga-laptop-2-13/ - -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXrCIjAAoJEKY6WKPy4XVp3tgP/2eUUrbOepxUni7DmQloK026 ZL+HJiNYhRDbp7U3TlVLPmCJXjB1RYnJTHVoDxCGxwqTpp20xjGw921LFhYwH0HP hwZq9ML2WWbMoQB45joFm75vEn/TRKnw7X6WTeR1gTfhBqEIJsKJW8mxu9iDgBCb P/rbdTaGx8OeQ6I8XSC74ugESZSSe+CHT8AeSrAZkwntNGIYXi5VDDpQUtwUHuBj iJTYa/SDYaEnazHytX88IQ/jWJ7QeFr8ziS7HcwGYPRVFxynNMbYCBH3YWcLrbIP Z/dD+8vViaksBq2ielnoMy0QISGCliQDg7xCMWFvYyQyD51JdzLmecw5Q6Z30Lyx 3BOUSPppbiDdAfqmdKBY0E5ASQqxBxw5LgRUKJeVGMimp9dbf80YQTumpqLcCZ5Q /8Kjrwy9hm4A8EFog1VkkKllvp+gmhia2z7yI8fHdGiDt9m5+YnkQ7Io8R4d+TiH k9lOEGmqVOjjjBPqo3ICikdpVSWfLo4aj9gz6F6ch48C+ozLDHskNzccAv46nutS Xve14Yil8KQMWZlUCuYCLjA7yfUrGOWLSv1pRhDlqBaj90e0rs/uq08CXaIhe9+v Y+a1+0FXRSjGBfMVqv6sQYnArUmdpzg+RtC4ek3SyQtngIKUhX0Bb/VX7EPE+Q1z PI2gcGH0FQXmVrlyTini =DDKE -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
