Acknowledgement sent
to miegiel <[email protected]>:
New Bug report received and forwarded. Copy sent to Debian EFI <[email protected]>.
Your message had a Version: pseudo-header with an invalid package
version:
fwupd/unstable,testing,now 2.0.2-2 amd64
please either use found or fixed to the control server with a correct
version, or reply to this report indicating the correct version so the
maintainer (or someone else) can correct it for you.
Subject: fwupd: "FuEngine failed to add device" error when inseting USB-stick
Date: Thu, 05 Dec 2024 22:03:48 +0100
Package: fwupd
Version: fwupd/unstable,testing,now 2.0.2-2 amd64
Severity: normal
Dear Maintainer,
Because this bug happens with only one USB-stick and not other sticks and fwupd not being the obvious cause , this bug might be more "important" than "normal"
When I insert my USB-stick (storage device) in my machine, it fails to mount and also unmounted access fails (like with partition managers).
In my syslog I found the fwupd errors like below::
2024-12-05T19:36:01.117422+01:00 machine fwupd[3123]: 18:36:01.117 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host1/target1:0:0/1:0:0:0/block/sdb: failed to setup: failed to read version: command fail with status 2, senseKey 0x05, asc 0x20, ascq 0x00
2024-12-05T19:37:46.585317+01:00 machine fwupd[3123]: 18:37:46.483 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host1/target1:0:0/1:0:0:0/block/sdb: failed to setup: no value for VEN
Since the USB-stick gave no problems in other machines, I decided to uninstall fwupd. This resolved the problem and reinstalling fwupd brought the problem back.
As I mentioned above it's just this one stick. It's old, released in nov 2011, purchased in july 2013, but it's not broken and I'd like to keep using it and fwupd.
Output of #lsusb -vd 0951:162b
Bus 004 Device 030: ID 0951:162b Kingston Technology DataTraveler HyperX 3.0
Couldn't open device, some information will be missing
Negotiated speed: SuperSpeed (5Gbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0951 Kingston Technology
idProduct 0x162b DataTraveler HyperX 3.0
bcdDevice 1.10
iManufacturer 1 Kingston
iProduct 2 DT HyperX 3.0
iSerial 3 20CF30E117F6BD51020304B2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x002c
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 896mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 14
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 14
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.11.10-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwupd depends on:
ii adduser 3.137
ii libarchive13t64 [libarchive13] 3.7.4-1.1
ii libblkid1 2.40.2-11
ii libc6 2.40-4
ii libcbor0.10 0.10.2-2
pn libcbor0.8 <none>
ii libcurl3t64-gnutls [libcurl3-gnutls] 8.11.0-1
ii libdrm-amdgpu1 2.4.123-1
ii libdrm2 2.4.123-1
ii libefiboot1t64 [libefiboot1] 38-3.1+b1
pn libflashrom1 <none>
pn libfwupd2 <none>
pn libfwupd3 <none>
pn libgcab-1.0-0 <none>
ii libglib2.0-0t64 [libglib2.0-0] 2.82.2-3
ii libgnutls30t64 [libgnutls30] 3.8.8-2
ii libgudev-1.0-0 238-5+b1
ii libgusb2 0.4.9-1+b1
pn libjcat1 <none>
ii libjson-glib-1.0-0 1.10.0+ds-3
ii liblzma5 5.6.3-1+b1
ii libmbim-glib4 1.30.0-1+b2
ii libmbim-proxy 1.30.0-1+b2
ii libmm-glib0 1.22.0-3+b2
ii libpolkit-gobject-1-0 125-2
ii libprotobuf-c1 1.4.1-1+b3
ii libqmi-glib5 1.34.0-2+b2
ii libqmi-proxy 1.34.0-2+b2
pn libsmbios-c2 <none>
ii libsqlite3-0 3.46.1-1
ii libsystemd0 257~rc3-1
pn libtss2-esys-3.0.2-0 <none>
pn libtss2-esys-3.0.2-0t64 <none>
ii libusb-1.0-0 2:1.0.27-1+b1
ii libxmlb2 0.3.21-1
ii shared-mime-info 2.4-5+b1
ii systemd [systemd-sysusers] 257~rc3-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages fwupd recommends:
pn bolt <none>
ii dbus 1.14.10-6
ii fwupd-amd64-signed [fwupd-signed] 1:1.7+1
pn jq <none>
ii python3 3.12.7-1
pn secureboot-db <none>
ii udisks2 2.10.1-11
Versions of packages fwupd suggests:
pn gir1.2-fwupd-2.0 <none>
Acknowledgement sent
to Mario Limonciello <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian EFI <[email protected]>.
Your message did not contain a Subject field. They are recommended and
useful because the title of a Bug is determined using this field.
Please remember to include a Subject field in your messages in future.
Can you please report a bug upstream for this issue? Please reproduce
while running the daemon with verbose mode (fwupd -vv) and capture the
output to attach.
On Thu, 19 Dec 2024 12:56:20 -0600 Mario Limonciello
<[email protected]> wrote:
> Can you please report a bug upstream for this issue? Please
> reproduce while running the daemon with verbose mode (fwupd -vv) and
> capture the output to attach.
>
>
Thankyou, I will.
Acknowledgement sent
to Benjamin Poirier <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian EFI <[email protected]>.
Your message did not contain a Subject field. They are recommended and
useful because the title of a Bug is determined using this field.
Please remember to include a Subject field in your messages in future.
I can confirm this bug. I'm having exact the same USB stick (same USB ID).
When booting the Debian live ISO (trixie) using GNOME desktop, after login
not all icons appear and I cannot open any application, so the live
system becomes unusable.
Using the toram kernel option I could start the live system, but after
like a minute or so the USB stick disappeared from /proc/partitions
and lsusb.
Plugging it out and in again, shows the stick as /dev/sdb for some
time but then is disappears again.
After stopping fwupd the stick was available without problems.
Attached is the log of fwupd -vv
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.