lupyuen commented on issue #14808:
URL: https://github.com/apache/nuttx/issues/14808#issuecomment-2535825399
NuttX `ps` is crashing inside QEMU RISC-V 32-bit, causing CI Test to fail.
But why is `ps` crashing for `rv-virt:citest`, but not other configs? 🤔
```bash
## Start Docker Container for NuttX
sudo docker run \
-it \
ghcr.io/apache/nuttx/apache-nuttx-ci-linux:latest \
/bin/bash
## Inside Docker:
## We compile rv-virt:citest
cd
git clone https://github.com/apache/nuttx
git clone https://github.com/apache/nuttx-apps apps
pushd nuttx ; echo NuttX Source: https://github.com/apache/nuttx/tree/$(git
rev-parse HEAD) ; popd
pushd apps ; echo NuttX Apps:
https://github.com/apache/nuttx-apps/tree/$(git rev-parse HEAD) ; popd
cd nuttx
tools/configure.sh rv-virt:citest
make -j
qemu-system-riscv32 \
-M virt \
-bios ./nuttx \
-nographic
NuttShell (NSH) NuttX-12.7.0
nsh> uname -a
NuttX 12.7.0 5607eece84 Dec 11 2024 07:05:48 risc-v rv-virt
nsh> ps
PID GROUP PRI POLICY TYPE NPX STATE EVENT SIGMASK
STACK USED FILLED COMMAND
0 0 0 FIFO Kthread - Ready 0000000000000000
0001952 0000908 46.5% Idle_Task
1 0 224 RR Kthread - Waiting Semaphore 0000000000000000
0001904 0000508 26.6% hpwork 0x8014b1e4 0x8014b210
2 0 100 RR Kthread - Waiting Semaphore 0000000000000000
0001896 0000508 26.7% lpwork 0x8014b1a0 0x8014b1cc
riscv_exception: EXCEPTION: Load access fault. MCAUSE: 00000005, EPC:
80008bfe, MTVAL: 01473e00
riscv_exception: PANIC!!! Exception = 00000005
dump_assert_info: Current Version: NuttX 12.7.0 5607eece84 Dec 11 2024
07:05:48 risc-v
dump_assert_info: Assertion failed panic: at file:
common/riscv_exception.c:131 task: nsh_main process: nsh_main 0x8000a806
up_dump_register: EPC: 80008bfe
```
[(See the __Complete
Log__)](https://gist.github.com/lupyuen/4ec0df33c2b4b569c010fade5f471940)
--
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]
