apollon77

It seems that the kernel downgrade did the trick so far

Ok, Arnbian Firmware was not the reason, happened again .., I now downgraded kernel to the version it was before ... lets see how this goes

Ok, I check deeper ... so beside armbian firmware which was updated as I told also kernel is much newer ... > Welcome to Armbian 21.08.3 Buster with Linux 5.10.60-sunxi on the system where it makes issues > Welcome to Armbian 21.08.2 Buster with Linux 5.10.43-sunxi on the systems where it works I now downgradded armbian firmware to 21.08.2 and will see if it gets better. Next would be downgrading kernel too

I checked the different packages and it should be basically armbian-bsp-cli-zeropi/buster,now 21.08.2 armhf [installed] armbian-firmware/buster,now 21.08.2 all [installed] vs 21.0.3 SHould I try to revert these two packages using apt install? (or is armbian-firmware enough?

Hi, I use three ZeroPi hosts as USBIP hosts top just offer USB devices. The kernel till last update on one device was Linux usb2 5.10.43-sunxi #21.05.6 SMP Mon Jun 21 15:07:45 UTC 2021 armv7l GNU/Linux and the new kernel on the once device that makes issues now is Linux usb3 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l GNU/Linux The issues are that one of the USB devices become unavailable after some hours and I see this in the syslog: Second exception is e.g. I tried to google for such errors but were unsucessful to find anything. Maybe i used wrong keywords. If there were Kernels in betweenn I could also try to go backward to find the pot affecting version or such ... I just need to know how. Thank you for your support, Ingo

Confirm that 20.08.2 works too

Guys, thank you very much, usbip works again! You're awesome!

Yes normal "stock" image ... but got it working ... so will leave that way :-) Thank you

Ok, reboot worked :-) ingof@usb3:~$ uname -a Linux usb3 5.8.5-sunxi #trunk SMP Tue Sep 1 11:24:23 CEST 2020 armv7l GNU/Linux Will test USBIP tomorow morning

Ok tried ... ingof@usb3:~/kernel-fix$ sudo apt install make gcc libc6-dev bison flex libssl-dev Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: bison : Depends: m4 but it is not going to be installed Depends: libbison-dev (= 2:3.3.2.dfsg-1) but it is not going to be installed flex : Depends: m4 but it is not going to be installed gcc : Depends: cpp (= 4:8.3.0-1) but it is not going to be installed Depends: gcc-8 (>= 8.3.0-1~) but it is not going to be installed libc6-dev : Depends: libc-dev-bin (= 2.28-10) but it is not going to be installed Depends: linux-libc-dev but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). So I executed the fix broken command: ingof@usb3:~/kernel-fix$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: binutils binutils-arm-linux-gnueabihf binutils-common bison cpp cpp-8 flex gcc gcc-8 libasan5 libatomic1 libbinutils libbison-dev libc-dev-bin libc6-dev libcc1-0 libgcc-8-dev libgomp1 libisl19 libmpc3 libmpfr6 libsigsegv2 libssl-dev libubsan1 linux-libc-dev m4 make Suggested packages: binutils-doc bison-doc cpp-doc gcc-8-locales build-essential flex-doc gcc-multilib manpages-dev autoconf automake libtool gdb gcc-doc gcc-8-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan5-dbg liblsan0-dbg libtsan0-dbg libubsan1-dbg libmpx2-dbg libquadmath0-dbg glibc-doc libssl-doc m4-doc make-doc Recommended packages: libfl-dev manpages manpages-dev The following NEW packages will be installed: binutils binutils-arm-linux-gnueabihf binutils-common bison cpp cpp-8 flex gcc gcc-8 libasan5 libatomic1 libbinutils libbison-dev libc-dev-bin libc6-dev libcc1-0 libgcc-8-dev libgomp1 libisl19 libmpc3 libmpfr6 libsigsegv2 libssl-dev libubsan1 linux-libc-dev m4 make 0 upgraded, 27 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 28.7 MB of archives. After this operation, 93.1 MB of additional disk space will be used. Ok that corrected it ... Setting up linux-headers-current-sunxi (20.08.0-trunk) ... Compiling headers - please wait ... Processing triggers for libc-bin (2.28-10) ...

Hm ... headers do not want to install ... Preparing to unpack linux-dtb-current-sunxi_20.08.0-trunk_armhf.deb ... Unpacking linux-dtb-current-sunxi (20.08.0-trunk) over (20.08) ... Selecting previously unselected package linux-headers-current-sunxi. Preparing to unpack linux-headers-current-sunxi_20.08.0-trunk_armhf.deb ... Unpacking linux-headers-current-sunxi (20.08.0-trunk) ... Preparing to unpack linux-image-current-sunxi_20.08.0-trunk_armhf.deb ... update-initramfs: Deleting /boot/initrd.img-5.7.15-sunxi Removing obsolete file uInitrd-5.7.15-sunxi Unpacking linux-image-current-sunxi (20.08.0-trunk) over (20.08) ... Preparing to unpack linux-u-boot-current-zeropi_20.08.0-trunk_armhf.deb ... Unpacking linux-u-boot-zeropi-current (20.08.0-trunk) over (20.08) ... Setting up linux-dtb-current-sunxi (20.08.0-trunk) ... dpkg: dependency problems prevent configuration of linux-headers-current-sunxi: linux-headers-current-sunxi depends on make; however: Package make is not installed. linux-headers-current-sunxi depends on gcc; however: Package gcc is not installed. linux-headers-current-sunxi depends on libc6-dev; however: Package libc6-dev is not installed. linux-headers-current-sunxi depends on bison; however: Package bison is not installed. linux-headers-current-sunxi depends on flex; however: Package flex is not installed. linux-headers-current-sunxi depends on libssl-dev; however: Package libssl-dev is not installed. dpkg: error processing package linux-headers-current-sunxi (--install): dependency problems - leaving unconfigured Setting up linux-image-current-sunxi (20.08.0-trunk) ... update-initramfs: Generating /boot/initrd.img-5.8.5-sunxi update-initramfs: Converting to u-boot format Setting up linux-u-boot-zeropi-current (20.08.0-trunk) ... Errors were encountered while processing: linux-headers-current-sunxi should I install the missing packages and do the headers again?

Do you have a short info how to do? Do I need to fetch all of them? Or only the armhf ones? ANd then install them with dpkg -i directly?

So true ;-) I'm invested myself very deep in a Smart Home project (ioBroker) as one of the Core Developers (mainly Node.js based) ... so I know exactly what you mean ;-)

Awesome ... I can wait some days ... To be clear: With "Add a patch" you mean you do or I should do? If me then I need to know how :-) Thank you for this incredible fast support

Thank you for your answer. When I read "I just compiled 5.8.5 with your patch and usbip works correctly, thx!" (from the linked issue) again Im not sure that it is on 5.8.5 ... I read it more like "when I compile 5.8.5 with that patch it works" ,.. so 5.8.5 is not the solution unless we do a custom build with this patch :-( So downgrading to 5.6 is more forward or ?! When checking there are some older version of the linux-image-current-sunxi package available but I can not find out which kern is in there :-( ingof@usb3:~$ apt-cache policy linux-image-current-sunxi linux-image-current-sunxi: Installed: 20.08 Candidate: 20.08 Version table: *** 20.08 500 500 http://apt.armbian.com buster/main armhf Packages 100 /var/lib/dpkg/status 20.05.3 500 500 http://apt.armbian.com buster/main armhf Packages 20.05.2 500 500 http://apt.armbian.com buster/main armhf Packages 20.05.1 500 500 http://apt.armbian.com buster/main armhf Packages 20.05.0-trunk 500 500 http://apt.armbian.com buster/main armhf Packages 20.02.9 500 500 http://apt.armbian.com buster/main armhf Packages 20.02.7 500 500 http://apt.armbian.com buster/main armhf Packages 20.02.5 500 500 http://apt.armbian.com buster/main armhf Packages

Hey ... Ok googling more brought me to this ... https://bugzilla.kernel.org/show_bug.cgi?id=208267 And yes ... Proxmox is on kernel 5.4 and armbian on 5.7 ... according to this I could go down to kernel 5.6 or wait for 5.8.5+ ... Any instructions on how to go down to kernel 5.6?

Hi, I normally use Proxmox on Intel Nucs (also Buster based) and also had here usbip with some USB sticks on a USB hub. Now I decided to split that up a bit and so I got some ZeroPi devices and wanted to use them as USBIP hosts kind of. So I installed the buster image and also added usbip_host module to /etc/modules. The devices are seen by the Linux on the ZeroPi in general and also /usr/sbin/usbip list -l lists them successfully. Here the dmesg output too: [ 350.174305] usb 4-1: new high-speed USB device number 6 using ehci-platform [ 350.331127] usb 4-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 [ 350.331149] usb 4-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 350.331163] usb 4-1: Product: USB 2.0 Hub [ 350.332407] hub 4-1:1.0: USB hub found [ 350.332615] hub 4-1:1.0: 4 ports detected [ 350.738278] usb 4-1.2: new full-speed USB device number 7 using ehci-platform [ 350.968886] usb 4-1.2: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 [ 350.968907] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 350.968922] usb 4-1.2: Product: USB-Serial Controller [ 350.968935] usb 4-1.2: Manufacturer: Prolific Technology Inc. [ 350.970353] pl2303 4-1.2:1.0: pl2303 converter detected [ 350.972932] usb 4-1.2: pl2303 converter now attached to ttyUSB0 [ 351.154251] usb 4-1.3: new full-speed USB device number 8 using ehci-platform [ 351.384959] usb 4-1.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 351.384969] usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 351.384975] usb 4-1.3: Product: CP2104 USB to UART Bridge Controller [ 351.384980] usb 4-1.3: Manufacturer: Silicon Labs [ 351.384984] usb 4-1.3: SerialNumber: 01065F3B [ 351.386324] cp210x 4-1.3:1.0: cp210x converter detected [ 351.389285] usb 4-1.3: cp210x converter now attached to ttyUSB1 [ 351.590248] usb 4-1.4: new full-speed USB device number 9 using ehci-platform [ 351.820837] usb 4-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 351.820848] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 351.820854] usb 4-1.4: Product: CP2104 USB to UART Bridge Controller [ 351.820859] usb 4-1.4: Manufacturer: Silicon Labs [ 351.820864] usb 4-1.4: SerialNumber: 010625FA [ 351.822141] cp210x 4-1.4:1.0: cp210x converter detected [ 351.824928] usb 4-1.4: cp210x converter now attached to ttyUSB2 But as soon as I try to bind such a device (e.g. /usr/sbin/usbip bind --busid=4-1.2) it is said that the device is not connected and log (syslog this time) shows: Sep 1 09:03:55 usb3 usbipd: usbipd: info: starting usbipd (usbip-utils 2.0) Sep 1 09:03:55 usb3 usbipd: usbipd: info: listening on 0.0.0.0:3240 Sep 1 09:03:55 usb3 usbipd: usbipd: info: listening on :::3240 ... Sep 1 09:03:56 usb3 kernel: [ 414.661581] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 Sep 1 09:03:56 usb3 kernel: [ 414.661655] pl2303 4-1.2:1.0: device disconnected Sep 1 09:03:56 usb3 sh[1837]: usbip: error: error binding device 4-1.2 to driver: No such device Sep 1 09:03:56 usb3 sh[1837]: usbip: error: could not bind device to usbip-host Does anyone have an idea? Googl was also not that helpful so far. I reconnected the hub to the proxmox host and everythig works there agin without any problem :-(

I use one of my Cubietrucks to operate two IR-read/write heads to read out powermeters. Sometimes some kind of error happends and the device get's disconnected (not physically, but from system): dmesg output: [434913.929842] ohci-platform 1c14400.usb: frame counter not updating; disabled [434913.939546] ohci-platform 1c14400.usb: HC died; cleaning up [434913.947863] usb 3-1: USB disconnect, device number 3 [434913.949632] cp210x ttyUSB0: failed set request 0x0 status: -19 [434913.959197] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [434913.959273] cp210x 3-1:1.0: device disconnected I can fix it by rebooting only, also unplugging/re-plugging the cable physically is not working. I googled around and there are some ideas how to reset it, but nothing worked. Is there maybe anything special for Cubietruck that I could do? Any help would be great!

So results for another device (cubietruck2) ... limatester worked in all tested configs. Same u-boots as tested before to be compatible in the results ... (so latest ideas from ssvb not included) tpm8-u-boot-sunxi-with-spl_20170219_432_DCDC3_13v root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050605 active_windowing = 0 --> stable 3 u-boot armbian 5.20 root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050605 active_windowing = 0 -> stable u-boot armbian 5.25 root@cubietruck:~# a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050506 active_windowing = 0 -> stable I will post the RAM-chip-name from that device later on

Further infos on my problematicdevice: RAM-chips are from SKhynix I will start further testing with a mainly well working device today and will also send the RAM chips used there later on

3.) tpm8 432-DCDC3 (432 DRAM speed, modified DCDC3) stable with limatester 100MB root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x06060605 active_windowing = 0 And now ?! How to go further on the topic? Or are the affected devices simply "strange somehow" and can't use the default u-boot?!

3.) tpm8 384-DCDC3 (384 DRAM speed, modified DCDC3) freeze with limatester 100MB root@cubietruck:~# a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050506 active_windowing = 0

Second Device (cubietruck3), my problematic one: 1.) armbian u-boot 5.20 (432 DRAM speed) no freeze with limatester 1000MB root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x06060605 active_windowing = 0 2.) armbian u-boot 5.25 (384 DRAM speed) memory errors with limatester 1000MB and freeze/auto-restart with limatester 100MB root@cubietruck:~# a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050505 active_windowing = 0 Memory errors where: pagesize is 4096 pagesizemask is 0xfffff000 want 1000MB (1048576000 bytes) got 1000MB (1048576000 bytes), trying mlock ...locked. Loop 1: Stuck Address : testing 2FAILURE: possible bad address line at offset 0x1b05c300. Skipping to next test... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : testing 5WRITE FAILURE: 0xaaaaaaaa != 0xaaaa55aa at offset 0x1873ab40 (checkerboard). Bit Spread : ok Bit Flip : ok Walking Ones : ok Walking Zeroes : ok Loop 2: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : testing 1WRITE FAILURE: 0xaaaaaaaa != 0xaaaa55aa at offset 0x0a3c8b40 (checkerboard). Bit Spread : ok Bit Flip : ok ...

Ok, Results from "cubietruck5": 1.) armbian u-boot 5.20 (432 DRAM speed) freeze after 9h limatester 1000MB root@cubietruck:~# a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x06060606 active_windowing = 0 2.) armbian u-boot 5.25 (384 DRAM speed) no freeze in 24h with limatester 1000MB root@cubietruck:~# a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050505 active_windowing = 0 Will do the complete etst with my problem-device tomorrow I think. But as you see the values are exactly the same as in the post from tpm8 above for a probematic device. I fear i will find the same

I will collect some and post ...