有时,当我在命令行中使用sudo时,20+秒内什么也不会发生。在那之后,需要的事情发生了,这就是我被告知要在指纹阅读器上滑动我的手指,或者,如果没有,输入一个密码。
类似地,有时当屏幕被锁定,我试图解锁/恢复时,有时它对20+秒没有任何作用。
如何调试这种令人恼火的行为?其他人看到了吗?
谢谢!
更新:下面是syslog在其中一个事件中的一个示例:
Apr 7 10:31:21 T450s-high kernel: [1007821.465715] usb 2-7: new full-speed USB device number 95 using xhci_hcd
Apr 7 10:31:21 T450s-high kernel: [1007821.601740] usb 2-7: device descriptor read/64, error -71
Apr 7 10:31:22 T450s-high dbus-daemon[1621]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.16814' (uid=0 pid=3682008 comm="sudo emacs /etc/hosts " label="unconfined")
Apr 7 10:31:22 T450s-high systemd[1]: Starting Fingerprint Authentication Daemon...
Apr 7 10:31:35 T450s-high systemd[3073]: Started Application launched by gsd-media-keys.
Apr 7 10:31:35 T450s-high systemd[3073]: Started VTE child process 3682066 launched by gnome-terminal-server process 1924388.
Apr 7 10:31:37 T450s-high kernel: [1007837.313788] usb 2-7: device descriptor read/64, error -110
Apr 7 10:31:37 T450s-high kernel: [1007837.549784] usb 2-7: new full-speed USB device number 96 using xhci_hcd
Apr 7 10:31:37 T450s-high kernel: [1007837.681771] usb 2-7: device descriptor read/64, error -71
Apr 7 10:31:37 T450s-high kernel: [1007837.925788] usb 2-7: device descriptor read/64, error -71
Apr 7 10:31:37 T450s-high kernel: [1007838.033835] usb usb2-port7: attempt power cycle
Apr 7 10:31:38 T450s-high kernel: [1007838.693813] usb 2-7: new full-speed USB device number 97 using xhci_hcd
Apr 7 10:31:38 T450s-high kernel: [1007838.693956] usb 2-7: Device not responding to setup address.
Apr 7 10:31:38 T450s-high kernel: [1007838.901916] usb 2-7: Device not responding to setup address.
Apr 7 10:31:38 T450s-high kernel: [1007839.109764] usb 2-7: device not accepting address 97, error -71
Apr 7 10:31:38 T450s-high kernel: [1007839.241739] usb 2-7: new full-speed USB device number 98 using xhci_hcd
Apr 7 10:31:38 T450s-high kernel: [1007839.241879] usb 2-7: Device not responding to setup address.
Apr 7 10:31:39 T450s-high kernel: [1007839.449901] usb 2-7: Device not responding to setup address.
Apr 7 10:31:39 T450s-high kernel: [1007839.661741] usb 2-7: device not accepting address 98, error -71
Apr 7 10:31:39 T450s-high kernel: [1007839.661817] usb usb2-port7: unable to enumerate USB device
Apr 7 10:31:39 T450s-high dbus-daemon[1621]: [system] Successfully activated service 'net.reactivated.Fprint'
Apr 7 10:31:39 T450s-high systemd[1]: Started Fingerprint Authentication Daemon.
下面是kern.log:
Apr 7 10:31:01 T450s-high kernel: [1007801.937805] usb usb2-port7: unable to enumerate USB device
Apr 7 10:31:21 T450s-high kernel: [1007821.465715] usb 2-7: new full-speed USB device number 95 using xhci_hcd
Apr 7 10:31:21 T450s-high kernel: [1007821.601740] usb 2-7: device descriptor read/64, error -71
Apr 7 10:31:37 T450s-high kernel: [1007837.313788] usb 2-7: device descriptor read/64, error -110
Apr 7 10:31:37 T450s-high kernel: [1007837.549784] usb 2-7: new full-speed USB device number 96 using xhci_hcd
Apr 7 10:31:37 T450s-high kernel: [1007837.681771] usb 2-7: device descriptor read/64, error -71
Apr 7 10:31:37 T450s-high kernel: [1007837.925788] usb 2-7: device descriptor read/64, error -71
Apr 7 10:31:37 T450s-high kernel: [1007838.033835] usb usb2-port7: attempt power cycle
Apr 7 10:31:38 T450s-high kernel: [1007838.693813] usb 2-7: new full-speed USB device number 97 using xhci_hcd
Apr 7 10:31:38 T450s-high kernel: [1007838.693956] usb 2-7: Device not responding to setup address.
Apr 7 10:31:38 T450s-high kernel: [1007838.901916] usb 2-7: Device not responding to setup address.
Apr 7 10:31:38 T450s-high kernel: [1007839.109764] usb 2-7: device not accepting address 97, error -71
Apr 7 10:31:38 T450s-high kernel: [1007839.241739] usb 2-7: new full-speed USB device number 98 using xhci_hcd
Apr 7 10:31:38 T450s-high kernel: [1007839.241879] usb 2-7: Device not responding to setup address.
Apr 7 10:31:39 T450s-high kernel: [1007839.449901] usb 2-7: Device not responding to setup address.
Apr 7 10:31:39 T450s-high kernel: [1007839.661741] usb 2-7: device not accepting address 98, error -71
Apr 7 10:31:39 T450s-high kernel: [1007839.661817] usb usb2-port7: unable to enumerate USB device
usb错误看起来不太好。这有用吗?
$ lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 030: ID 0bc2:ab34 Seagate RSS LLC Backup Plus
Bus 003 Device 029: ID 17ef:1010 Lenovo ThinkPad Ultra Dock Hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 008: ID 04ca:703c Lite-On Technology Corp. Integrated Camera
Bus 002 Device 123: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor
Bus 002 Device 003: ID 04f3:0418 Elan Microelectronics Corp. Touchscreen
Bus 002 Device 087: ID 047d:1022 Kensington Orbit Optical
Bus 002 Device 086: ID 046d:0826 Logitech, Inc. HD Webcam C525
Bus 002 Device 083: ID 17ef:100f Lenovo ThinkPad Ultra Dock Hub
Bus 002 Device 080: ID 17ef:1010 Lenovo ThinkPad Ultra Dock Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
更新
@Rinzwind可能会帮助我解决一个不相关的问题(USB)。与此相关,我列出了我的/etc/modprobe.d的内容:
lrwxrwxrwx 1 root root 41 Jun 30 2021 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r-- 1 root root 2733 Mar 30 2020 alsa-base.conf
-rw-r--r-- 1 root root 1518 Apr 12 2019 blacklist.conf
-rw-r--r-- 1 root root 677 Apr 12 2019 blacklist-framebuffer.conf
-rw-r--r-- 1 root root 154 Aug 24 2018 intel-microcode-blacklist.conf
-rw-r--r-- 1 root root 154 Jun 26 2018 amd64-microcode-blacklist.conf
-rw-r--r-- 1 root root 325 May 28 2018 blacklist-ath_pci.conf
-rw-r--r-- 1 root root 210 May 28 2018 blacklist-firewire.conf
-rw-r--r-- 1 root root 583 May 28 2018 blacklist-rare-network.conf
-rw-r--r-- 1 root root 347 May 28 2018 iwlwifi.conf
-rw-r--r-- 1 root root 127 Feb 7 2017 dkms.conf
-rw-r--r-- 1 root root 2507 Jul 30 2015 alsa-base.conf~
-rw-r--r-- 1 root root 156 Jul 30 2015 blacklist-modem.conf
没有“选项:”文件。我应该创造它吗?
至于域名解析的可能性是个问题,我怎么知道呢?我在一个由以太网连接的主要大学校园里,但可能是因为我自己的主机名有问题吗?
发布于 2022-04-07 19:39:51
这回答了日志中的错误,可能不是问题的答案,所以如果不是,请PM我,我会删除它。
device descriptor read/64, error -110
可能是由-71
引起的。关于device descriptor read/64, error -71
。这个错误可能是造成长时间延迟的原因。
变更文件
/etc/modprobe.d/options:
再加上
options usbcore use_both_schemes=y
可能需要重新启动。
来源及其解释:
“旧方案”是Linux在2.6.10之前的工作方式。当插入一个新设备时,系统首先给它分配一个地址,然后读取设备描述符的初始8个字节,然后读取整个18字节的设备描述符。“新方案”基本上是Windows的工作方式。(不足为奇的是,有些设备不会以其他方式工作。)当插入新设备时,系统首先为设备描述符发出64字节的读取请求,然后重置设备,然后分配地址,然后读取实际的18字节设备描述符。这些恶作剧的原因是,在全速设备的情况下,端点0 (ep0maxpacket)的最大数据包大小事先还不清楚。它可以是8、16、32或64字节。(低速设备必须使用8,高速设备必须使用64。)ep0maxpacket值存储在设备描述符的初始8个字节中,但是要读取设备描述符,必须使用端点0!上述两种方案是解决这一鸡与蛋问题的两种常见办法。旧方案是USB实现者论坛推荐的方案(使其成为“标准”);新方案是Microsoft使用的方案(这使其成为另一种“标准”!)一个设计良好的符合标准的设备在任何一种方案下都能正常工作。不幸的是,不管你选择哪种方案,一些设计糟糕的不符合规定的设备都无法工作。在特别糟糕的情况下,还有一个额外的usbcore.ko模块参数可以使用: use_both_schemes=y --这将导致系统尝试其中一个方案,如果失败,则尝试另一个方案。(也许这应该永远是默认的.)
https://askubuntu.com/questions/1400223
复制相似问题