Serial communication issue - "Got overrun errors"

Hi NaterGator,
Thanks for your interest in helping with this.

Here are the patches provided from Nvidia Dev team: Bitbucket

I just created this repo to share these patches.

Let me know if you have any questions.

-Glenn

Hi Glenn,

I wonder if the patch works properly or not. We encounter the “overrun error and crash” problem with ttyTHS1@576000bps sometimes (especially we run some program under the serial tty console) and ttyTHS1@921600bps always at the beginning. After applying the patch, the “overrun error” should not appear as the dev_err->dev_dbg, however, lots of data lost @576000bps.

Could you share your use case such as baud rate? Currently we are using the l4t 24.1. For some reasons, we cannot use 24.2 (we need ROS not supported by 64bit ubuntu 24.2 provided).

Thanks in advance.

Zhang,
In our application we were transferring at 10Mbs with no hardware flow control. After the patch we didn’t see the issues reappear. We have since changed our design to use USB.

I would recommend changing to a different communication bus such as i2c, SPI, CAN, or USB.

The issue is that rs232 isn’t designed well for high speed communication without hardware control.

You could try using the hardware flow control lines, and see if that helps.

Hope that helps. Let me know if you have further questions.

Hey glennjamin,
have you try this patch in real_time system with RT_preempt?
I still get these errors and dont know why.need help
Sep 23 13:01:57 tegra-ubuntu kernel: [ 2949.993841] tty_insert_flip_string_fixed_flag_lock: No space: Requested 4096, memory used: 65024
Sep 23 13:01:57 tegra-ubuntu kernel: [ 2950.002638] serial-tegra serial-tegra.0: RxData DMA copy to tty layer failed