Your message dated Sat, 15 Apr 2023 18:13:01 +0200
with message-id <[email protected]>
and subject line Re: Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal
after removing a Yubikey 4 (USB-C)
has caused the Debian Bug report #895703,
regarding Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey
4 (USB-C)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pcscd
Version: 1.8.23-2
Severity: normal
Dear maintainer,
This appears to be similar symptoms to bug #459827, but reporting
separately, as this has nothing to do with PCMCIA.
After removing a Yubikey 4 (USB-C) from my XPS 13 9360, syslog is filled
with errors like this about once a second:
```
Apr 04 11:04:56 zinc pcscd[4147]: 99999999 ccid_usb.c:849:WriteUSB() write
failed (3/2): -4 LIBUSB_ERROR_NO_DEVICE
Apr 04 11:04:56 zinc pcscd[4147]: 00000056 ifdwrapper.c:364:IFDStatusICC() Card
not transacted: 617
Apr 04 11:04:57 zinc pcscd[4147]: 01000882
eventhandler.c:334:EHStatusHandlerThread() Error communicating to: Yubico
Yubikey 4 OTP+U2F+CCID 00 00
Apr 04 11:04:57 zinc pcscd[4147]: 00000029 ccid_usb.c:1312:InterruptRead()
libusb_submit_transfer failed: LIBUSB_ERROR_NO_DEVICE
Apr 04 11:04:57 zinc pcscd[4147]: 00400296 ccid_usb.c:849:WriteUSB() write
failed (3/2): -4 LIBUSB_ERROR_NO_DEVICE
Apr 04 11:04:57 zinc pcscd[4147]: 00000017 ifdwrapper.c:364:IFDStatusICC() Card
not transacted: 617
```
This specific issue happened after a resume-from-suspend when the device
was removed between suspend and resume, but in general it happens any
time I remove the USB-C device.
This does not occur with a Yubikey Neo (USB 2.0).
I was also able to replicate it on a fellow developer's XPS 13 9350.
Please let me know if there is any other debugging information I can
provide.
Cheers,
Luke Faraone
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pcscd depends on:
ii libc6 2.27-3
ii libccid [pcsc-ifd-handler] 1.4.29-2
ii libpcsclite1 1.8.23-2
ii libsystemd0 238-4
ii libudev1 238-4
ii lsb-base 9.20170808
pcscd recommends no packages.
Versions of packages pcscd suggests:
ii systemd 238-4
-- no debconf information
--- End Message ---
--- Begin Message ---
Le 11/12/2021 à 16:25, Ludovic Rousseau a écrit :
Hello Luke,
On Sat, 21 Apr 2018 17:54:54 +0200 Ludovic Rousseau
<[email protected]> wrote:
I suggest to search for a firmware update from Dell. Maybe the USB-C is
(partly) bogus on your mother board.
For example I found a BIOS update on Dell web site:
Dell XPS 13 9360 System BIOS
Importance: Urgent
Version: 2.6.2 ,2.6.2 Older versions
Release Date: 22 Mar 2018
File Name: XPS_9360_2.6.2.exe
File size: 10.69 MB
Description: XPS 13 9360 2.6.2 BIOS
Tell me if a BIOS upgrade fixes the problem.
Any news or fix with the BIOS upgrade?
I would like to close this bug report.
No news since more than one year.
Closing now.
Bye
--
Dr. Ludovic Rousseau
--- End Message ---
