Ouss4 commented on pull request #4403:
URL: https://github.com/apache/incubator-nuttx/pull/4403#issuecomment-905039145
I'm still seeing some sporadic deadlocks, like this:
```gdb
#0 up_cpu_pausereq (cpu=1) at common/xtensa_cpupause.c:67
#1 0x400d37e0 in irq_waitlock (cpu=1) at irq/irq_csection.c:127
#2 0x400d3941 in enter_critical_section () at irq/irq_csection.c:350
#3 0x400d89f6 in modifyreg32 (addr=1072955404, clearbits=0, setbits=16386)
at common/xtensa_modifyreg32.c:52
#4 0x400d95bb in esp32_txint (dev=<optimized out>, enable=<optimized out>)
at chip/esp32_serial.c:1760
#5 0x400f144c in uart_write (filep=<optimized out>, buffer=<optimized out>,
buflen=0) at serial/serial.c:1225
#6 0x4014673e in file_write (filep=<optimized out>, buf=0x3ffe0f70,
nbytes=1) at vfs/fs_write.c:89
#7 0x400e4430 in nx_write (fd=1, buf=0x3ffe0f70, nbytes=1) at
vfs/fs_write.c:138
#8 0x400e4443 in write (fd=1, buf=0x3ffe0f70, nbytes=1) at
vfs/fs_write.c:202
#9 0x400deeaf in readline_putc (vtbl=0x3ffe0fd0, ch=<optimized out>) at
readline.c:145
#10 0x400df195 in readline_common (vtbl=0x3ffe0fd0, buf=0x3ffcb01c "iperf -c
192.168.1.12 -p 124444", buflen=<optimized out>)
at readline_common.c:734
#11 0x400def40 in readline (buf=0x3ffcb01c "iperf -c 192.168.1.12 -p
124444", buflen=300, instream=<optimized out>,
outstream=0x3ffaf854) at readline.c:227
#12 0x400ddb97 in nsh_session (pstate=0x3ffcadb0, login=<optimized out>,
argc=<optimized out>, argv=0x3ffe0480) at nsh_session.c:159
#13 0x400da274 in nsh_consolemain (argc=1, argv=0x3ffe0480) at
nsh_consolemain.c:100
#14 0x400da224 in nsh_main (argc=1, argv=0x3ffe0480) at nsh_main.c:153
#15 0x400d5fdf in nxtask_startup (entrypt=0x400da1e0 <nsh_main>, argc=1,
argv=0x3ffe0480) at sched/task_startup.c:151
#16 0x400d41cb in nxtask_start () at task/task_start.c:130
```
I'll have to debug this a little more.
--
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]
