Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-06-12 Thread via GitHub
acassis closed issue #16462: [BUG] nxsem_wait_irq assertion failure URL: https://github.com/apache/nuttx/issues/16462 -- 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 unsubsc

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-06-10 Thread via GitHub
atr294 commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2960924152 @pussuw @acassis My apologies for the delay. It took me some time to get `CONFIG_MM_KMAP` working on my Litex target due to initial memory layout issues. After resolving those,

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-06-02 Thread via GitHub
acassis commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2930773395 Thank you for explanation @pussuw ! Do you think this new exception that @atr294 found while running monkey in foreground also have the same root cause? -- This is an automated mes

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-06-02 Thread via GitHub
pussuw commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2930874955 Yes, almost certainly. The wrong user mappings are active during the watchdog interrupt and atomic_read reads the sem counter from the wrong physical page, getting a garbage value.

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-06-02 Thread via GitHub
pussuw commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2929187000 Duplicate of https://github.com/apache/nuttx/issues/8917 The underlying issue is that when nxsem_wait_irq is called, the wrong mappings might be active. In order for it to work

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-06-01 Thread via GitHub
atr294 commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2928460730 @acassis thanks for the suggestion. I've tried the monkey test in the foreground, and it doesn't seem to trigger the same issue. Running `monkey -t 0x12 ` or `monkey -t 0x11` i

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-05-31 Thread via GitHub
acassis commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2925574719 @atr294 nice test idea! Did you try to run ostest in background and the monkey on foreground to see if the issue also happens? -- This is an automated message from the Apache Git S

Re: [I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-05-31 Thread via GitHub
acassis commented on issue #16462: URL: https://github.com/apache/nuttx/issues/16462#issuecomment-2925573049 @pussuw could you please take a look, it is related to your PR about sem_waitirq -- This is an automated message from the Apache Git Service. To respond to the message, please log

[I] [BUG] nxsem_wait_irq assertion failure [nuttx]

2025-05-29 Thread via GitHub
atr294 opened a new issue, #16462: URL: https://github.com/apache/nuttx/issues/16462 ### Description / Steps to reproduce the issue * Description: When running a time-consuming task in the background and repeatedly entering any rando keys in the NSH shell, a crash sometimes hap