You are not logged in.
After last update boot has slowed down considerable . apparently usb device 3:7 has issues.
full journal at https://paste.c-net.org/FightingDecisive
jun 26 21:01:00 mjoelnir kernel: usb 3-7: device descriptor read/64, error -110
jun 26 21:01:00 mjoelnir kernel: usb 3-7: device descriptor read/64, error -110
jun 26 21:01:00 mjoelnir kernel: usb 3-7: new high-speed USB device number 4 using xhci_hcd
jun 26 21:01:00 mjoelnir kernel: usb 3-7: device descriptor read/64, error -110
jun 26 21:01:00 mjoelnir kernel: usb 3-7: device descriptor read/64, error -110
jun 26 21:01:00 mjoelnir kernel: usb usb3-port7: attempt power cycle
jun 26 21:01:00 mjoelnir kernel: usb 3-7: new high-speed USB device number 5 using xhci_hcd
jun 26 21:01:00 mjoelnir kernel: usb 3-7: Device not responding to setup address.
jun 26 21:01:00 mjoelnir kernel: usb 3-7: Device not responding to setup address.
jun 26 21:01:00 mjoelnir kernel: usb 3-7: device not accepting address 5, error -71
jun 26 21:01:00 mjoelnir kernel: usb 3-7: new high-speed USB device number 6 using xhci_hcd
jun 26 21:01:00 mjoelnir kernel: usb 3-7: Device not responding to setup address.
jun 26 21:01:00 mjoelnir kernel: usb 3-7: Device not responding to setup address.
jun 26 21:01:00 mjoelnir kernel: usb 3-7: device not accepting address 6, error -71
jun 26 21:01:00 mjoelnir kernel: usb usb3-port7: unable to enumerate USB device
jun 26 21:01:00 mjoelnir kernel: usb 3-8: new high-speed USB device number 7 using xhci_hcd
jun 26 21:01:00 mjoelnir kernel: usb 3-8: New USB device found, idVendor=26ce, idProduct=0a0b, bcdDevice= 0.02
jun 26 21:01:00 mjoelnir kernel: usb 3-8: New USB device strings: Mfr=3, Product=1, SerialNumber=0
jun 26 21:01:00 mjoelnir kernel: usb 3-8: Product: USB Audio
jun 26 21:01:00 mjoelnir kernel: usb 3-8: Manufacturer: Genericlsusb doesn't show a usb-3:8 device and sound works fine.
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 003 Device 007: ID 26ce:0a0b Generic USB Audio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 002: ID 26ce:01a2 ASRock LED Controller
$ The last update included newer firmware so it may have to do with that
[2026-06-26T20:30:48+0200] [PACMAN] Running 'pacman -Syu'
[2026-06-26T20:30:48+0200] [PACMAN] synchronizing package lists
[2026-06-26T20:30:50+0200] [PACMAN] starting full system upgrade
[2026-06-26T20:31:16+0200] [ALPM] transaction started
[2026-06-26T20:31:16+0200] [ALPM] upgraded amd-ucode (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded glib2 (2.88.1-1 -> 2.88.2-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded libssh2 (1.11.1-4 -> 1.11.1-5)
[2026-06-26T20:31:16+0200] [ALPM] upgraded gpgme (2.1.0-1 -> 2.1.1-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded lame (3.101.r6531-1 -> 3.101.r6531-2)
[2026-06-26T20:31:16+0200] [ALPM] upgraded libarchive (3.8.8-1 -> 3.8.8-2)
[2026-06-26T20:31:16+0200] [ALPM] upgraded linux-firmware-whence (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded linux-firmware-amdgpu (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded linux-firmware-intel (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded linux-firmware-mediatek (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded linux-firmware-other (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] upgraded linux-firmware-realtek (20260519-1 -> 20260622-1)
[2026-06-26T20:31:16+0200] [ALPM] transaction completed
[2026-06-26T20:31:16+0200] [ALPM] running '35-systemd-update.hook'...
[2026-06-26T20:31:16+0200] [ALPM] running '90-mkinitcpio-install.hook'...
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] ==> Starting build: '7.0.13-arch1-1'
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2026-06-26T20:31:16+0200] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2026-06-26T20:31:17+0200] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2026-06-26T20:31:17+0200] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2026-06-26T20:31:17+0200] [ALPM-SCRIPTLET] -> Running build hook: [numlock]
[2026-06-26T20:31:17+0200] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2026-06-26T20:31:17+0200] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
[2026-06-26T20:31:18+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qat_6xxx'
[2026-06-26T20:31:18+0200] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2026-06-26T20:31:18+0200] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2026-06-26T20:31:19+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2026-06-26T20:31:19+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2026-06-26T20:31:19+0200] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2026-06-26T20:31:19+0200] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2026-06-26T20:31:19+0200] [ALPM] running 'rebuild-detector.hook'...
[2026-06-26T20:31:20+0200] [ALPM] running 'texinfo-install.hook'...Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
x-ref, https://bbs.archlinux.org/viewtopic.php?id=313864
Edit: do you miss any device or do journals of older boots reveal what usb 3-7 was?
Last edited by seth (Today 20:19:47)
Offline
jun 26 02:59:42 mjoelnir kernel: usb 3-7: new high-speed USB device number 3 using xhci_hcd
jun 26 02:59:42 mjoelnir kernel: ata3: SATA link down (SStatus 0 SControl 300)
jun 26 02:59:42 mjoelnir kernel: tsc: Refined TSC clocksource calibration: 4300.105 MHz
jun 26 02:59:42 mjoelnir kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x3dfbc6587b9, max_idle_ns: 440795231860 ns
jun 26 02:59:42 mjoelnir kernel: clocksource: Switched to clocksource tsc
jun 26 02:59:42 mjoelnir kernel: usb 3-7: New USB device found, idVendor=0e8d, idProduct=0717, bcdDevice= 1.00
jun 26 02:59:42 mjoelnir kernel: usb 3-7: New USB device strings: Mfr=5, Product=6, SerialNumber=7
jun 26 02:59:42 mjoelnir kernel: usb 3-7: Product: Wireless_Device
jun 26 02:59:42 mjoelnir kernel: usb 3-7: Manufacturer: MediaTek Inc.
jun 26 02:59:42 mjoelnir kernel: usb 3-7: SerialNumber: 000000000Looks like its the wifi which I don't use on this system . going to try to revert linux-firmware-mediatek .
The x-ref points to this thread, guess you don't want that ?
EDIT
it is not the firmware and disabling wan radio in uefi setup didn't make a difference.
Room temp is about 29 degrees Celsius. Highest temp since I got this system.
$ sensors
spd5118-i2c-17-53
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +39.5°C (low = +0.0°C, high = +55.0°C)
(crit low = +0.0°C, crit = +85.0°C)
r8169_0_700:00-mdio-0
Adapter: MDIO adapter
temp1: +49.0°C (high = +120.0°C)
nvme-pci-0400
Adapter: PCI adapter
Composite: +50.9°C (low = -273.1°C, high = +83.8°C)
(crit = +87.8°C)
Sensor 1: +56.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +50.9°C (low = -273.1°C, high = +65261.8°C)
amdgpu-pci-0300
Adapter: PCI adapter
vddgfx: 80.00 mV
fan1: 0 RPM (min = 0 RPM, max = 3600 RPM)
edge: +44.0°C (crit = +100.0°C, hyst = -273.1°C)
(emerg = +105.0°C)
junction: +46.0°C (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
mem: +44.0°C (crit = +105.0°C, hyst = -273.1°C)
(emerg = +110.0°C)
PPT: 8.00 W (cap = 175.00 W)
pwm1: 0%
sclk: 5 MHz
mclk: 1 GHz
spd5118-i2c-17-51
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +39.0°C (low = +0.0°C, high = +55.0°C)
(crit low = +0.0°C, crit = +85.0°C)
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +42.0°C
Tccd1: +34.2°C
Tccd2: +33.2°C
amdgpu-pci-7200
Adapter: PCI adapter
vddgfx: 1.02 V
vddnb: 1.08 V
edge: +40.0°C
PPT: 8.00 mW
sclk: 600 MHz
$ Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The x-ref points to this thread, guess you don't want that ?
Fake news ![]()
(Thanks for the heads up)
MTK is otr for botching the nvram, it might require a full power cycle (battery out, coffee, battery in) to revive.
The firmware update *might* have been semi-coincidental here.
Offline