masayuki2009 commented on PR #9859:
URL: https://github.com/apache/nuttx/pull/9859#issuecomment-1647659638
@anjiahao1
>I noticed that ostest with qemu-armv8a:netnsh_smp causes a deadlock.
The ostest crashed with qemu-armv8a:nsh_smp.
```
user_main: signal handler test
sighand_test: Initializing semaphore to 0
sighand_test: Starting waiter task
sighand_test: Started waiter_main pid=155
waiter_main: Waiter started
waiter_main: Unmasking signal 32
waiter_main: Registering signal handler
waiter_main: oact.sigaction=0 oact.sa_flags=0 oact.sa_mask=0000000000000000
waiter_main: Waiting on semaphore
sighand_test: Signaling pid=155 with signo=32 sigvalue=42
[CPU0] nxsig_queue: pid=0x0000009b signo=32 value=42
[CPU0] nxsig_tcbdispatch: TCB=0x40378700 pid=155 signo=32 code=1 value=42
masked=NO
[CPU0] up_schedule_sigaction: tcb=0x40378700 sigdeliver=0x4028b6e0
[CPU0] up_schedule_sigaction: rtcb=0x4037d550 CURRENT_REGS=0
[CPU1] arm64_fatal_error: reason = 1
[CPU1] arm64_fatal_error: CurrentEL: MODE_EL1
[CPU1] arm64_fatal_error: ESR_ELn: 0x1fe00000
[CPU1] arm64_fatal_error: FAR_ELn: 0x0
[CPU1] arm64_fatal_error: ELR_ELn: 0x40290994
[CPU1] print_ec_cause: Trapped access to SVE, Advanced SIMD, or
floating-point functionality
[CPU1] _assert: Current Version: NuttX 10.4.0 0092b3e30f Jul 24 2023
19:30:27 arm64
[CPU1] _assert: Assertion failed panic: at file: common/arm64_fatal.c:375
task(CPU1): waiter 0x402a2d24
[CPU1] up_dump_register: stack = 0x40373f30
[CPU1] up_dump_register: x0: 0x402c5ea8 x1: 0xdeaddead
[CPU1] up_dump_register: x2: 0x402bc0d0 x3: 0x40286b98
[CPU1] up_dump_register: x4: 0x402c5ee8 x5: 0x40287c94
[CPU1] up_dump_register: x6: 0x40378700 x7: 0x1
[CPU1] up_dump_register: x8: 0x402bc0d0 x9: 0x40286b98
[CPU1] up_dump_register: x10: 0x402c5ee8 x11: 0x40287c94
[CPU1] up_dump_register: x12: 0x40378700 x13: 0x1
[CPU1] up_dump_register: x14: 0x402c5ee4 x15: 0x40287cfc
[CPU1] up_dump_register: x16: 0x1 x17: 0x0
[CPU1] up_dump_register: x18: 0x402c5000 x19: 0x40378700
[CPU1] up_dump_register: x20: 0x402c5000 x21: 0x40286f94
[CPU1] up_dump_register: x22: 0x402bc150 x23: 0x0
[CPU1] up_dump_register: x24: 0x40378bac x25: 0x402bc150
[CPU1] up_dump_register: x26: 0x0 x27: 0x4028c2ec
[CPU1] up_dump_register: x28: 0x402bc150 x29: 0x402bc0d0
[CPU1] up_dump_register: x30: 0x40378bac
[CPU1] up_dump_register:
[CPU1] up_dump_register: STATUS Registers:
[CPU1] up_dump_register: SPSR: 0x4008e610
[CPU1] up_dump_register: ELR: 0x402bc168
[CPU1] up_dump_register: SP_EL0: 0x40374060
[CPU1] up_dump_register: SP_ELX: 0x40374060
[CPU1] up_dump_register: TPIDR_EL0: 0x40378700
[CPU1] up_dump_register: TPIDR_EL1: 0x40378700
[CPU1] up_dump_register: EXE_DEPTH: 0x1
[CPU1] dump_tasks: PID GROUP CPU PRI POLICY TYPE NPX STATE EVENT
SIGMASK STACKBASE STACKSIZE USED FILLED COMMAND
[CPU1] dump_tasks: ---- --- ---- --- -------- ------- --- -------
---------- -------- 0x402cb000 8192 8192 100.0%! irq
[CPU1] dump_task: 0 0 0 0 FIFO Kthread N-- Assigned
0000000000000000 0x402d1010 16368 1360 8.3% CPU0 IDLE
[CPU1] dump_task: 1 1 1 0 FIFO Kthread N-- Assigned
0000000000000000 0x402d5010 16368 1088 6.6% CPU1 IDLE
[CPU1] dump_task: 2 2 2 0 FIFO Kthread N-- Running
0000000000000000 0x402d9010 16368 1088 6.6% CPU2 IDLE
[CPU1] dump_task: 3 3 3 0 FIFO Kthread N-- Running
0000000000000000 0x402dd010 16368 1088 6.6% CPU3 IDLE
[CPU1] dump_task: 4 4 0 192 RR Kthread --- Waiting
Semaphore 0000000000000000 0x402e39f0 16320 1264 7.7% hpwork
0x402c64f8
[CPU1] dump_task: 5 5 0 100 RR Task --- Waiting
Semaphore 0000000000000000 0x402e8000 16336 2944 18.0% nsh_main
[CPU1] dump_task: 22 22 0 100 RR Task --- Running
0000000000000000 0x4036c6e0 16288 2320 14.2% ostest Arg1
Arg2 Arg3 Arg4
[CPU1] dump_task: 155 155 1 100 RR Task --- Running
0000000000000000 0x403706c0 16336 3552 21.7% waiter
[CPU1] dump_task: 15 15 0 100 RR Task --- Waiting
Semaphore 0000000000000000 0x40379530 16336 1984 12.1% ostest
```
Could you please confirm if the latest upstream works with qemu?
--
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]
