Bug 258382

Summary:	comms/ser2net: uses 100% of CPU
Product:	Ports & Packages	Reporter:	Chris Johns <chrisj>
Component:	Individual Port(s)	Assignee:	Vinícius Zavam <egypcio>
Status:	Closed Not Enough Information
Severity:	Affects Only Me	Flags:	egypcio: maintainer-feedback+
Priority:	---
Version:	Latest
Hardware:	amd64
OS:	Any

Description Chris Johns 2021-09-09 07:46:01 UTC

# uname -v
FreeBSD 13.0-RELEASE-p1 #0: Wed May 26 22:15:09 UTC 2021     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC 

I have a hardware board (Xilinx Ultrascale Cortex-A53) with a USB FDTI serial console configured at 115200 baud and if I connect using telnet or the `rtems-test` command `ser2net` seems to spin with 100% CPU load.

I ran `ser2net` from the command line with a number of threads and a number of CPUs seems to max at 100%.

The serial output `set2net` sents over the telnet connection has dropped data. Observing the data stream from the RTEMS applications running on the Utlrascale hardware it seems the dropped data is from the start of a block. The UART has a TX FIFO and it is being used. 

Note, the `rtems-test` command uses Python's `telnetlib` to connect using the telnet protocol.

Comment 1 Vinícius Zavam freebsd_committer

2021-10-17 13:54:20 UTC

we sadly can't reproduce it, and are missing (detailed) information about the setup and how it's all build.

also, on top of that, this port must be updated. would you mind giving it a try and reporting back if the issue persists? from 3.5.1 it can jump to 4.3.4

Comment 2 Vinícius Zavam freebsd_committer

2021-12-27 19:18:27 UTC

as we did not receive any feedback at all regarding this issue, it will be tracked to a CLOSED status -- the port itself still lacks an update, and that's a well-known task to be accomplished.