RTEMS | riscv/riscv clockdrv may bsp_fatal even with correct behaviour/initialization (#5486)

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5486#note_144280


I encountered this on qemu with SMP. I see the same logic exists in arm (`a9mpcore_clock_secondary_initialization`). I don't know what it is really intending to do, because `cmpval - now > interval` should never happen, while `cmpval - now == interval` may happen in extreme circumstances.

I would just get rid of this check.
@sebhub ?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5486#note_144280
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260304/9b0a4c71/attachment-0001.htm>