zhhyu7 commented on PR #18011: URL: https://github.com/apache/nuttx/pull/18011#issuecomment-3784381088
> @zhhyu7 I tried on the `esp32-devkitc` and `esp32c6-devkit` because it has easier debug. Also, I enabled DEBUG_ASSERTIONS. On IPERF start, it immediately crashed: > > * ESP32: > > ``` > nsh> iperf -c 192.168.0.125 -i 3 -t 10 & > iperf [12:100] > nsh> IP: 192.168.0.85 > > mode=tcp-client sip=192.168.0.85:5001,dip=192.168.0.125:5001, interval=3, time=10 > > Interval Transfer Bandwidth > > [CPU1] dump_assert_info: Current Version: NuttX 10.4.0 21c19b7824 Jan 22 2026 09:56:18 xtensa > [CPU1] dump_assert_info: Assertion failed ((wrb)->wb_sent) <= ((wrb)->wb_iob->io_pktlen): at file: tcp/tcp_send_buffered.c:1173 task(CPU1): iperf_traffic process: iperf 0x4011a890 > ... > ``` > > * ESP32-C6: > > ``` > nsh> iperf -c 192.168.0.125 -i 3 -t 10 & > iperf [9:100] > nsh> IP: 192.168.0.3 > > mode=tcp-client sip=192.168.0.3:5001,dip=192.168.0.125:5001, interval=3, time=10 > > Interval Transfer Bandwidth > > dump_assert_info: Current Version: NuttX 10.4.0 21c19b7824 Jan 22 2026 10:04:02 risc-v > dump_assert_info: Assertion failed ((wrb)->wb_sent) <= ((wrb)->wb_iob->io_pktlen): at file: tcp/tcp_send_buffered.c:1173 task: lpwork process: Kernel 0x4200702e > ... > ``` > > Seems they crash at the same place. @fdcavalcanti Get, Will iperf return to normal if this patch is reverted? Then I'll revert this patch first, and after optimizing the implementation, I'll find several more devices locally for detailed verification before proceeding further. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
