RTEMS | bsps/i386: Fix the interrupt validation (!1573)
Sebastian Huber (@sebhub)
gitlab at rtems.org
Tue Nov 10 07:50:20 UTC 2026
Sebastian Huber created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1573
Project:Branches: sebhub/rtems:up/i386-intr to rtems/rtos/rtems:main
Author: Sebastian Huber
## Summary
Closes #5798.
**Problem:** `ts-validation-intr` fails on `i386/pc586-sse` with 10571 failed checks. `rtems_interrupt_vector_is_enabled()` returns `RTEMS_UNSATISFIED` for every vector, and `rtems_interrupt_is_pending()` answers only for the software interrupt. The test of `rtems_interrupt_entry_install()` finds no second vector which software can raise.
**Fix:**
- Report the enabled and pending state of each valid vector.
- Add `BSP_SOFTWARE_IRQ_2` with its own interrupt descriptor. The Local APIC raises it like the first one. tm27 names it as the alternative vector.
- Delete the expected-failure file of the BSP, because no validation test fails anymore.
**Review hints:**
- This MR is based on !1572. Its own commits start at 86d11adb6c1.
## Test
`i386/pc586-sse` with `USE_COM1_AS_CONSOLE = True` on Qemu:
| Test | `main` | this MR |
| --- | --- | --- |
| `ts-validation-intr` | N:18311 F:10571 | N:22572 F:0 |
| `ts-validation-io-kernel` | hangs | F:0 |
| 18 other validation suites | F:0 | F:0 |
| `tm27`, `rhilatency` | | pass |
`ts-performance-no-clock-0` (F:500) and `ts-validation-acfg-1` give the same result on `main` and on this MR.
## AI Details
<!-- Make sure you have read our statement at https://www.rtems.org/generative-ai/ -->
### Prompt used
None as a single prompt. The work was done in an interactive Claude Code session on the RTEMS tree. Each change was directed and reviewed.
### AI model used
Claude Opus 5.5 (claude-opus-5-5), through Claude Code.
### How AI was used for the contribution
- ( ) Formatting
- ( ) Test creation.
- (x) Code comments.
- ( ) The entire contribution was generated using AI
- ( ) AI code completion such as Copilot in VSCode.
The implementation was produced in that session under my direction, and the commit messages were drafted there.
### Access
I have not used a product which claims copyright in its output, and I have legitimate access to the one I used.
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1573
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-76xefdbnt4xhur4rnxaon9nn6-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20261110/9a3240b0/attachment.htm>
More information about the bugs
mailing list