dabozz Posted November 15, 2025 Posted November 15, 2025 Hi, I currently have the issue of a non working usb port on my odroidhc4. dmesg output: [ 133.464610] usb usb1-port2: connect-debounce failed The port does not show up when lsusb is entered. uname -a: Linux odroidhc4 6.12.56-current-meson64 #1 SMP PREEMPT Wed Oct 29 13:09:02 UTC 2025 aarch64 GNU/Linux I solved this temporairly a while ago by booting an older kernel (linux-image-6.12.43+deb12-arm64) like mentioned here: Are there any progresses on how to fix this reliably? Because I think still running kernel 6.6.63 is not save. Thanks for your answer in advance, if you need more information I am happy to deliver. 0 Quote
Igor Posted November 23, 2025 Posted November 23, 2025 On 11/15/2025 at 11:59 AM, dabozz said: running kernel 6.6.63 is not save 6.6 is LTS kernel https://www.kernel.org/category/faq.html When some security issue is found, it goes into all LTS kernels. Higher version number does not guarantee bigger safety. Most recent has more functional bug fixes and new features and is generally more fragile - bugs / holes yet to be found. On 11/15/2025 at 11:59 AM, dabozz said: Are there any progresses on how to fix this reliably? Yes, v25.11.1 with 6.12.y https://www.armbian.com/odroid-hc4/ doesn't have those problems. At least I could not recreate them. Booting HC4, plugged in two usb devices, all good: https://paste.armbian.com/ibifozegof P.S. Life is deadly dangerous 0 Quote
dabozz Posted November 24, 2025 Author Posted November 24, 2025 Great news! So a simple apt update/upgrade will fix it for me? 0 Quote
Igor Posted November 24, 2025 Posted November 24, 2025 1 hour ago, dabozz said: Great news! So a simple apt update/upgrade will fix it for me? Yes, but packages hasn't been pushed out yet. We need to test and possibly fix last problems on images. In 10-14 days. 0 Quote
dabozz Posted December 8, 2025 Author Posted December 8, 2025 Hi Igor, I recently updated to Armbian 25.11.2 bookworm aarch64 with kernel Linux odroidhc4 6.12.58-current-meson64. This should be a working version? There I still get the same connect-debounce error. Do you have any advice? 0 Quote
savoy Posted April 23 Posted April 23 I'm having the same issue after upgrading. I do backups on an HDD via USB for the two drives on my HC4 I was on Bullseye this year and was planning on moving up to Bookworm for a bit, but was hit with the issue. I decided to jump then into Trixie in the hopes that a more recent kernel would fix it, but I'm still facing it. kernel: Linux odroidhc4 6.18.10-current-meson64 dmesg error msg: usb usb1-port2: connect-debounce failed 0 Quote
Winnize Posted 2 hours ago Posted 2 hours ago (edited) Quote root@odroidhc4 [22:53:05] [~] -> # dmesg | grep failed [ 4.378109] usb usb1-port2: connect-debounce failed root@odroidhc4 [22:53:13] [~] -> # uname -a Linux odroidhc4 6.18.34-current-meson64 #1 SMP PREEMPT Mon Jun 1 15:51:08 UTC 2026 aarch64 GNU/Linux root@odroidhc4 [22:58:39] [~] -> # /lib/nut/usbhid-ups -DDDDD -a ups Network UPS Tools - Generic HID driver 0.52 (2.8.1) USB communication driver (libusb 1.0) 0.46 0.000000 [D5] do_upsconf_args: confupsname=ups, var=driver, val=usbhid-ups 0.000032 [D5] do_upsconf_args: call main_arg() 0.000049 [D3] main_arg: var='driver' val='usbhid-ups' 0.000064 [D5] do_upsconf_args: not a main_arg() 0.000076 [D5] do_upsconf_args: this is a 'driver' setting, may we proceed? 0.000090 [D5] do_upsconf_args: 'driver' setting already applied with this value 0.000106 [D5] do_upsconf_args: confupsname=ups, var=port, val=auto 0.000119 [D5] do_upsconf_args: call main_arg() 0.000131 [D3] main_arg: var='port' val='auto' 0.000158 [D5] send_to_all: SETINFO driver.parameter.port "auto" 0.000185 [D5] do_upsconf_args: confupsname=ups, var=user, val=root 0.000199 [D5] do_upsconf_args: call main_arg() 0.000212 [D3] main_arg: var='user' val='root' 0.000225 [D1] testval_reloadable: setting 'user' exists and differs: new value 'root' vs. 'nut' 0.000238 [D1] Overriding previously specified user 'nut' with 'root' specified for driver section 0.000270 [D1] Network UPS Tools version 2.8.1 (release/snapshot of 2.8.1) built with gcc (Debian 14.2.0-19) 14.2.0 and configured with flags: --build=aarch64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/aarch64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --prefix=/usr --sysconfdir=/etc/nut --includedir=/usr/include --mandir=/usr/share/man --libdir=${prefix}/lib/aarch64-linux-gnu --libexecdir=/usr/libexec --with-ssl --with-nss --with-cgi --with-dev --enable-static --with-statepath=/run/nut --with-altpidpath=/run/nut --with-drvpath=/usr/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/aarch64-linux-gnu/pkgconfig --with-user=nut --with-group=nut --with-udev-dir=/usr/lib/udev --with-systemdsystemunitdir=/usr/lib/systemd/system --with-systemdshutdowndir=/usr/lib/systemd/system-shutdown --with-systemdtmpfilesdir=/usr/lib/tmpfiles.d --with-python=python3 --with-python3=/usr/bin/python3 --with-doc=man 0.000342 [D1] debug level is '5' 0.000361 [D5] send_to_all: SETINFO driver.debug "5" 0.000377 [D5] send_to_all: SETFLAGS driver.debug RW NUMBER 0.002619 [D1] Succeeded to become_user(root): now UID=0 GID=0 0.002705 [D5] send_to_all: SETINFO device.type "ups" 0.002725 [D5] send_to_all: SETINFO driver.state "init.device" 0.002740 [D1] upsdrv_initups (non-SHUT)... 0.002754 [D2] Initializing an USB-connected UPS with library libusb-1.0.28 (API: 0x100010a) (NUT subdriver name='USB communication driver (libusb 1.0)' ver='0.46') 0.008856 [D2] Checking device 1 of 2 (1D6B/0003) 0.034527 [D1] nut_libusb_open: invalid libusb bus number 0 0.035013 [D2] - VendorID: 1d6b 0.035043 [D2] - ProductID: 0003 0.035062 [D2] - Manufacturer: Linux 6.18.34-current-meson64 xhci-hcd 0.035086 [D2] - Product: xHCI Host Controller 0.035101 [D2] - Serial Number: xhci-hcd.1.auto 0.035116 [D2] - Bus: 002 0.035129 [D2] - Bus Port: unknown 0.035147 [D2] - Device: 001 0.035161 [D2] - Device release number: 0618 0.035175 [D2] Trying to match device 0.035195 [D2] match_function_subdriver (non-SHUT mode): matching a device... 0.035225 [D2] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID 0.035242 [D2] Device does not match - skipping 0.035287 [D2] Checking device 2 of 2 (1D6B/0002) 6.482574 [D1] nut_libusb_open: invalid libusb bus number 0 83.858558 [D2] - VendorID: 1d6b 83.859395 [D2] - ProductID: 0002 83.860200 [D2] - Manufacturer: Linux 6.18.34-current-meson64 xhci-hcd 83.860222 [D2] - Product: xHCI Host Controller 83.860233 [D2] - Serial Number: xhci-hcd.1.auto 83.860241 [D2] - Bus: 001 83.860250 [D2] - Bus Port: unknown 83.860259 [D2] - Device: 001 83.860267 [D2] - Device release number: 0618 83.860275 [D2] Trying to match device 83.860287 [D2] match_function_subdriver (non-SHUT mode): matching a device... 83.860309 [D2] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID 83.860319 [D2] Device does not match - skipping 89.039367 [D2] libusb1: No appropriate HID device found 89.040205 libusb1: Could not open any HID devices: insufficient permissions on everything 89.040223 No matching HID UPS found 89.040248 [D5] send_to_all: SETINFO driver.state "cleanup.exit" 89.040269 upsnotify: notify about state 4 with libsystemd: was requested, but not running as a service unit now, will not spam more about it 89.040286 upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Hello, Same issue with debian trixie and my UPS connected by usb, not working but work on old kernel. Edited 2 hours ago by Winnize Duplicate message 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.