Open iz8mbw opened 1 year ago
I am also seeing this a lot on my installation.
RASPBERRY PI VERSION VERSION
RETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
Client: Docker Engine - Community Version: 24.0.2 API version: 1.43 Go version: go1.20.4 Git commit: cb74dfc Built: Thu May 25 21:50:59 2023 OS/Arch: linux/arm64 Context: default
DOCKER VERSION
Server: Docker Engine - Community Engine: Version: 24.0.2 API version: 1.43 (minimum version 1.12) Go version: go1.20.4 Git commit: 659604f Built: Thu May 25 21:50:59 2023 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0
Hello.
For now I have changed my setup so instead to use https://github.com/gianfrdp/SDM120C software to poll my SDM120 meter, I'm using mbusd and "call" it via mbpoll command.
So the software that uses the serial port is mbusd
and in this way I don't have any more Timed out waiting for FSM NP transfer to complete
on the /var/log/messages
.
I had the same issue with the 64bits edition of Raspberry Pi OS. I reinstalled the 32bits version, and the WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer
errors are completely gone.
At some points before reinstalling, the Raspberry Pi was even losing the network after a few hours. Everything is solved by moving back to the 32bits edition.
My model is: Raspberry Pi 3 Model B Plus Rev 1.3
The dwc_otg's driver makes heavy use of FIQs to improve performance. Until fairly recently the arm64 support didn't recognise FIQs; it looks like they are now supported to some extent, but the dwc_otg driver hasn't been updated to use it - you can bet that won't be a simple task.
For now, the advice on arm64 is the same as it's always been - use "dtoverlay=dwc2" to select the upstream DWC2 driver.
thank you for the pointer. however it appears to not be possible to boot from a usb drive using the dwc2 driver.
dtoverlay=dwc2,dr_mode=host
also disabling fiq in config.txt isn't taken into account by the driver, if it is even still possible. https://forums.raspberrypi.com/viewtopic.php?t=70437
dwc_otg.fiq_enable=0
dwc_otg.fiq_fsm_enable=0
$ dmesg | grep FIQ
dwc_otg: FIQ enabled
dwc_otg: FIQ split-transaction FSM enabled
I'll revert to armv7l as well.
edit : reverted to armv7l, issue does still appear, but much less often. edit2 : moved to emmc on sd adapter, no more issues.
Same, 64-bit Debian Bookworm on a Raspberry Pi 3+. I'm also using a USB-to-RJ45 cable to read my smart energy meter.
also disabling fiq in config.txt isn't taken into account by the driver, if it is even still possible. dwc_otg.fiq_enable=0 dwc_otg.fiq_fsm_enable=0
These setting go in cmdline.txt (on existing line), not config.txt.
Hello. Using a Raspberry Pi 3 Model B+ with latest Raspberry Pi OS (64-bit):
Linux rpi3 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux
On one USB port I have a USB to RS485 adapter (using PL2303 chip):
On this RS485 interface
/dev/ttyUSB0
I poll every 2 seconds a SDM120 Smart Meter (Modbus) with this software. All works well except I have lots ofWARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on
in/var/log/messages
.See here an extract:
I have the same warning on
messages
also if I try to use another USB ot RS485 adapter using the "ch341" chip.Thanks for your support.