RTEMS / RTOS / RTEMS¶
Go to Issues or Merge Requests
Issues Summary
Merge Requests Summary
Issues¶
5311 - Backport Chris’s libio fix to 6 branch¶
Id |
5311 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-07-25T01:54:35.008Z |
Closed |
2025-10-10T00:02:36.043Z |
Updated |
2025-10-10T00:02:36.117Z |
Milestone |
6.2 |
Link |
|
Merges |
1 |
The following discussion from !536 should be addressed:
[] @opticron started a discussion: (+3 comments)
I ran the added test without the fix and didn’t get a crash on zynqmp_qemu. On what platform did you encounter this failure?
Author: Kinsey Moore
2025-07-25T01:54:35.120Z
set status to To do
Author: Kinsey Moore
2025-07-25T01:54:46.677Z
added rtems#10 as parent epic
Author: Amar Takhar
2025-07-25T01:55:00.945Z
mentioned in merge request !536
Author: Kinsey Moore
2025-07-27T02:23:04.122Z
This backports cleanly and builds without errors.
Author: Kinsey Moore
2025-07-27T02:26:28.377Z
mentioned in merge request !635
Author: Kinsey Moore
2025-07-31T01:42:11.816Z
assigned to @opticron
Author: Kinsey Moore
2025-07-31T01:42:26.171Z
set status to Done
Author: Kinsey Moore
2025-07-31T01:42:26.667Z
This has been merged.
Author: Sebastian Huber
2025-09-15T06:59:33.957Z
set status to To do
Author: Sebastian Huber
2025-09-15T07:00:44.260Z
The commit 0cf6de01df734c11212e63134551ee344a10ecec introduced a couple of issues:
ABI changes on a release branch
Redundant LIBIO_FLAGS_FREE flag: an iop is free if and only if it is on the free list.
When the iop is freed, its reference count was set to zero. The iop reference count must never be set to a specific value after initialization at system start. The only valid operations are increments and decrements.
In the iop free handling, there was a deadlock potential by obtaining the libio lock while owning a file system lock.
The reference counting did not work at all under concurrent access. This was indicated by the failing spintrcritical24 test program.
The spintrcritical24 test was specifically added to test the file descriptor reference counting. It fails now on at least the sparc/gr740 and arm/xilinx_zynq_zc702 simulators. It fails since
rtems_libio_free()may free the iop by looking at the current flags. This is plainly wrong, actions must be carried out when certain state changes happen. Consider this sequence of events:int close( int fd ) { rtems_libio_t *iop; unsigned int flags; int rc; if ( (uint32_t) fd >= rtems_libio_number_iops ) { rtems_set_errno_and_return_minus_one( EBADF ); } iop = rtems_libio_iop( fd ); flags = rtems_libio_iop_flags( iop ); while ( true ) { unsigned int desired; bool success; if ( ( flags & LIBIO_FLAGS_OPEN ) == 0 ) { rtems_set_errno_and_return_minus_one( EBADF ); } /* The expected flags depends on close when busy flag. If set * there can be references held when calling the close handler */ if ( ( flags & LIBIO_FLAGS_CLOSE_BUSY ) == 0 ) { flags &= LIBIO_FLAGS_FLAGS_MASK; } desired = flags & ~LIBIO_FLAGS_OPEN; success = _Atomic_Compare_exchange_uint( &iop->flags, &flags, desired, ATOMIC_ORDER_ACQ_REL, ATOMIC_ORDER_RELAXED ); if ( success ) { break; } if ( ( flags & LIBIO_FLAGS_REFERENCE_MASK ) != 0 ) { rtems_set_errno_and_return_minus_one( EBUSY ); } } <--- Lets suppose LIBIO_FLAGS_CLOSE_BUSY is cleared. At this point we cleared LIBIO_FLAGS_OPEN above and the reference count is zero. Let an interrupt call for example fstat(fd). It will hold and drop the iop. The drop will call rtems_libio_free() which will calle rtems_libio_free_iop() since the iop is no longer open and has a zero reference count. This will clear the iop->pathinfo. This will lead to a NULL pointer access here: rc = (*iop->pathinfo.handlers->close_h)( iop ); rtems_libio_free( iop ); return rc; }
Author: Sebastian Huber
2025-09-15T07:03:54.174Z
mentioned in merge request !725
Author: Sebastian Huber
2025-09-15T07:11:59.522Z
The !725 changes the API which requires changes in libbsd:
https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/97
Author: Sebastian Huber
2025-09-15T07:11:25.591Z
mentioned in merge request rtems/pkg/rtems-libbsd!97
Author: Aaron Nyholm
2025-10-09T22:32:29.528Z
mentioned in merge request !774
Author: Aaron Nyholm
2025-10-09T22:42:02.675Z
mentioned in merge request !775
Author: Kinsey Moore
2025-10-10T00:02:36.096Z
set status to Done
Author: Kinsey Moore
2025-10-10T00:02:36.783Z
I believe the issue has been resolved with Aaron’s recent fixes in !775 and !774.
5336 - Backport rtems_barrier_get_number_waiting()¶
Id |
5336 |
State |
closed |
Type |
ISSUE |
Author |
Sebastian Huber |
Assignee(s) |
Sebastian Huber |
Closed by |
Kinsey Moore |
Created |
2025-09-12T01:03:03.539Z |
Closed |
2025-10-09T22:22:44.564Z |
Updated |
2025-10-09T22:22:44.636Z |
Milestone |
6.2 |
Labels |
api::classic |
Link |
|
Merges |
0 |
Author: Sebastian Huber
2025-09-12T01:03:03.661Z
added rtems#10 as parent epic
Author: Sebastian Huber
2025-09-12T01:03:03.754Z
set status to To do
Author: Sebastian Huber
2025-09-12T01:03:03.876Z
assigned to @sebhub
Author: Sebastian Huber
2025-09-12T01:12:45.882Z
mentioned in merge request !720
Author: Kinsey Moore
2025-10-09T22:22:44.615Z
set status to Done
5337 - Backport storage class qualifier rearrangements¶
Id |
5337 |
State |
closed |
Type |
ISSUE |
Author |
Sebastian Huber |
Assignee(s) |
Sebastian Huber |
Closed by |
Kinsey Moore |
Created |
2025-09-12T01:18:00.904Z |
Closed |
2025-10-09T22:22:35.749Z |
Updated |
2025-10-09T22:22:35.828Z |
Milestone |
6.2 |
Labels |
rtems::testing |
Link |
|
Merges |
0 |
Author: Sebastian Huber
2025-09-12T01:18:01.057Z
added rtems#10 as parent epic
Author: Sebastian Huber
2025-09-12T01:18:01.154Z
set status to To do
Author: Sebastian Huber
2025-09-12T01:18:01.299Z
assigned to @sebhub
Author: Sebastian Huber
2025-09-12T01:30:53.201Z
mentioned in merge request !721
Author: Kinsey Moore
2025-10-09T22:22:35.806Z
set status to Done
5369 - Backport jffs2 flashdev NAND support to 6 branch¶
Id |
5369 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-10-03T14:19:52.181Z |
Closed |
2025-10-09T22:21:44.062Z |
Updated |
2025-10-09T22:21:44.138Z |
Milestone |
6.2 |
Labels |
filesystem::jffs2 |
Link |
|
Merges |
0 |
The following discussion from !764 should be addressed:
[] @opticron started a discussion:
This is should be backported to 6 branch.
Author: Kinsey Moore
2025-10-03T14:19:52.321Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-10-03T14:19:52.389Z
set status to To do
Author: Kinsey Moore
2025-10-03T14:19:52.474Z
assigned to @opticron
Author: Kinsey Moore
2025-10-03T14:21:32.091Z
mentioned in merge request !765
Author: Kinsey Moore
2025-10-09T22:21:44.118Z
set status to Done
5284 - Backport mvme3100 fixes to 6 (!541)¶
Id |
5284 |
State |
closed |
Type |
ISSUE |
Author |
Jeremy Lorelli |
Closed by |
Kinsey Moore |
Created |
2025-06-30T01:03:53.061Z |
Closed |
2025-10-09T22:20:25.201Z |
Updated |
2025-10-09T22:20:25.290Z |
Milestone |
6.2 |
Labels |
arch:powerpc, backport |
Link |
|
Merges |
0 |
Summary¶
Backport !541 to RTEMS 6, once it’s merged.
Pre-set options¶
Author: Jeremy Lorelli
2025-06-30T01:04:28.988Z
mentioned in merge request !541
Author: Gedare Bloom
2025-06-30T14:54:49.549Z
changed type from task to issue
Author: Gedare Bloom
2025-06-30T14:56:00.396Z
added rtems#10 as parent epic
Author: Chris Johns
2025-10-02T23:32:01.362Z
Ping. Are you able to make an MR for the 6 branch for the 6.2 release?
Author: Jeremy Lorelli
2025-10-03T04:01:33.198Z
I’ve opened !762
Author: Jeremy Lorelli
2025-10-06T17:51:23.035Z
mentioned in merge request !762
Author: Kinsey Moore
2025-10-09T22:20:25.268Z
set status to Done
5371 - Backport ZynqMP XQspiPsu flashdev backend addition to 6 branch¶
Id |
5371 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-10-03T14:44:41.411Z |
Closed |
2025-10-09T22:13:30.563Z |
Updated |
2025-10-09T22:13:30.646Z |
Milestone |
6.2 |
Labels |
device::flash |
Link |
|
Merges |
0 |
The following discussion from !766 should be addressed:
[] @opticron started a discussion:
This functionality is present in 6 branch and this should be backported.
Author: Kinsey Moore
2025-10-03T14:44:41.552Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-10-03T14:44:41.619Z
set status to To do
Author: Kinsey Moore
2025-10-03T14:47:01.916Z
mentioned in merge request !767
Author: Kinsey Moore
2025-10-09T22:13:30.624Z
set status to Done
5372 - Backport Make flash config table static to 6 branch¶
Id |
5372 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-10-08T20:36:16.877Z |
Closed |
2025-10-09T15:23:18.862Z |
Updated |
2025-10-09T15:23:18.941Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
The following discussion from !771 should be addressed:
[] @opticron started a discussion:
This patch needs to be backported to 6 branch.
Author: Kinsey Moore
2025-10-08T20:36:17.054Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-10-08T20:36:17.150Z
set status to To do
Author: Kinsey Moore
2025-10-08T20:36:17.297Z
assigned to @opticron
Author: Kinsey Moore
2025-10-08T20:37:18.692Z
mentioned in merge request !772
Author: Kinsey Moore
2025-10-09T15:23:18.919Z
set status to Done
5365 - Backport live lock fix for split readsӦ
Id |
5365 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-09-29T16:43:21.615Z |
Closed |
2025-10-03T14:00:17.725Z |
Updated |
2025-10-03T14:00:17.803Z |
Milestone |
6.2 |
Labels |
filesystem::jffs2 |
Link |
|
Merges |
0 |
The following discussion from !757 should be addressed:
[] @opticron started a discussion:
This needs to be backported to 6 branch.
Author: Kinsey Moore
2025-09-29T16:43:21.769Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-09-29T16:43:21.869Z
set status to To do
Author: Kinsey Moore
2025-09-29T16:43:21.959Z
assigned to @opticron
Author: Kinsey Moore
2025-09-29T16:45:51.149Z
mentioned in merge request !758
Author: Joel Sherrill
2025-10-02T14:26:16.030Z
mentioned in merge request !759
Author: Kinsey Moore
2025-10-03T14:00:17.781Z
set status to Done
5350 - Backport flashdev NAND support to 6 branch¶
Id |
5350 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-09-23T19:36:41.159Z |
Closed |
2025-10-03T13:58:08.487Z |
Updated |
2025-10-03T13:58:08.565Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
The following discussion from !740 should be addressed:
[] @eagleirony started a discussion: (+5 comments)
Looks good to me. :))
Author: Kinsey Moore
2025-09-23T19:36:41.302Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-09-23T19:36:41.362Z
set status to To do
Author: Kinsey Moore
2025-09-23T19:36:41.454Z
assigned to @opticron
Author: Kinsey Moore
2025-09-23T19:38:37.009Z
mentioned in merge request !743
Author: Kinsey Moore
2025-10-03T13:58:08.543Z
set status to Done
5347 - Backport JFFS2 filesystem size enforcement to 6 branch¶
Id |
5347 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Closed by |
Chris Johns |
Created |
2025-09-23T01:46:11.963Z |
Closed |
2025-10-02T23:32:51.282Z |
Updated |
2025-10-02T23:32:51.286Z |
Milestone |
6.2 |
Labels |
filesystem::jffs2 |
Link |
|
Merges |
0 |
The following discussion from !735 should be addressed:
[] @opticron started a discussion:
This will need a backport to 6 branch as it’s a bug fix.
Author: Kinsey Moore
2025-09-23T01:46:12.300Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-09-23T01:46:12.455Z
set status to To do
Author: Kinsey Moore
2025-09-23T01:49:29.270Z
mentioned in merge request !742
Author: Chris Johns
2025-09-24T13:56:59.480Z
mentioned in commit b05ae8a6d49327225abfc202b8dcbb1bb97c88a3
Author: Chris Johns
2025-10-02T23:32:51.311Z
set status to Done
5348 - Backport libdebugger ARM SMP fixes¶
Id |
5348 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Closed by |
Chris Johns |
Created |
2025-09-23T03:17:54.786Z |
Closed |
2025-10-02T23:32:29.609Z |
Updated |
2025-10-02T23:32:29.660Z |
Milestone |
6.2 |
Labels |
cpukit::debugger |
Link |
|
Merges |
0 |
Backport the ARM SMP fix (https://gitlab.rtems.org/rtems/rtos/rtems/-/commit/f30157f988df3c9f75c201124573520c03edf6a3).
Author: Chris Johns
2025-09-23T03:17:54.919Z
added rtems#15 as parent epic
Author: Chris Johns
2025-09-23T03:17:54.983Z
set status to In progress
Author: Chris Johns
2025-09-23T03:17:55.157Z
assigned to @chris
Author: Chris Johns
2025-09-25T04:26:25.896Z
mentioned in merge request !748
Author: Chris Johns
2025-09-26T02:14:55.726Z
added rtems#10 as parent epic
Author: Chris Johns
2025-10-02T23:32:29.639Z
set status to Done
5180 - Backport stack-smash-protect feature to the 6 branch¶
Id |
5180 |
State |
closed |
Type |
ISSUE |
Author |
Mohamed Hassan |
Closed by |
Chris Johns |
Created |
2024-12-19T06:41:58.704Z |
Closed |
2025-10-02T23:30:44.368Z |
Updated |
2025-10-02T23:30:44.416Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
Summary¶
This issue tracks the backporting of the feature stack protection to the 6 branch to ensure consistency and availability of this feature in the 6.1 release.
Reference¶
Author: Gedare Bloom
2024-12-19T16:34:05.516Z
Author: Gedare Bloom
2024-12-19T16:36:31.672Z
mentioned in merge request !348
Author: Chris Johns
2025-10-02T23:30:44.395Z
set status to Won’t do
5303 - Deprecate and Remove Mongoose Web Server¶
Id |
5303 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Closed by |
Chris Johns |
Created |
2025-07-18T13:42:50.921Z |
Closed |
2025-10-02T23:27:50.696Z |
Updated |
2025-10-02T23:27:50.743Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
Summary¶
The Mongoose webserver (mghttpd) in RTEMS is old and pre-dates the change to GPL. The project forked and the permissive licensed code lives on as Civitweb. The mghttpd code in RTEMS is from before the split and is unmaintained upstream.
Civitweb can be built using the RSB. It is an active project.
It is recommended that users migrate to Civitweb.
The mghttd code is deprecated in RTEMS 6 and will be removed before RTEMS 7 branches.
Pre-set options¶
Author: Joel Sherrill
2025-07-18T13:44:44.807Z
changed the description
Author: Joel Sherrill
2025-07-18T13:45:29.487Z
mentioned in issue #5304
Author: Joel Sherrill
2025-07-24T22:55:11.149Z
mentioned in issue #5310
Author: Chris Johns
2025-10-02T23:24:55.117Z
added rtems#10 as parent epic
Author: Chris Johns
2025-10-02T23:26:11.606Z
added rtems#15 as parent epic
Author: Chris Johns
2025-10-02T23:26:36.234Z
added rtems#10 as parent epic
Author: Chris Johns
2025-10-02T23:27:00.486Z
cloned to #5367
Author: Chris Johns
2025-10-02T23:27:50.723Z
set status to Done
Author: Chris Johns
2025-10-02T23:28:08.428Z
The notice is given in the generated release notes.
5216 - Deprecate powerpc/mvme5500 in favor of powerpc/beatnik¶
Id |
5216 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Gedare Bloom |
Closed by |
Chris Johns |
Created |
2025-02-14T22:36:47.150Z |
Closed |
2025-10-02T23:24:39.324Z |
Updated |
2025-10-02T23:24:39.329Z |
Milestone |
6.2 |
Labels |
arch:powerpc, bsp |
Link |
|
Merges |
0 |
The beatnik primarily targets the mvme6100 but it also supports the mvme5500. This issue notices that the powerpc/mvme5500 is deprecated in the 6 release series and will be removed in 7.
Author: Gedare Bloom
2025-02-14T22:36:47.351Z
cloned from #4160
Author: Gedare Bloom
2025-02-14T22:36:47.239Z
assigned to @gedare
Author: Gedare Bloom
2025-02-14T22:38:04.310Z
changed title from {-Obsolete -}mvme5500 in favor of {-B-}eatnik to {+Deprecate powerpc/+}mvme5500 in favor of {+powerpc/b+}eatnik
Author: Gedare Bloom
2025-02-14T22:38:04.339Z
changed the description
Author: Gedare Bloom
2025-02-14T22:38:13.212Z
Author: Gedare Bloom
2025-02-14T22:57:48.491Z
[x] add this to the release notes
[x] add a note in Beatnik documentation
Author: Gedare Bloom
2025-02-14T22:57:48.491Z
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/25
Author: Gedare Bloom
2025-02-14T22:57:48.491Z
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/153
Author: Gedare Bloom
2025-02-14T22:53:43.694Z
mentioned in commit gedare/rtems-docs@72286dba503c0879486b8877c2e88522b146bad0
Author: Gedare Bloom
2025-02-14T22:54:05.231Z
mentioned in merge request rtems/docs/rtems-docs!153
Author: Gedare Bloom
2025-02-20T23:18:23.121Z
mentioned in commit gedare/rtems-docs@3ec35416774b6a7baf9106ebc0ac4a935e84cb48
Author: Amar Takhar
2025-05-08T23:16:06.202Z
mentioned in commit amar/rtems-docs@38a25aad78332ef1f507620040c3e8541a1ab048
Author: Amar Takhar
2025-05-08T23:19:01.833Z
mentioned in commit gedare/rtems-docs@701f0230e962b7d559dd7bb55b4443c37b82d67f
Author: Chris Johns
2025-10-02T23:24:39.352Z
set status to Done
5222 - RTEMS Priority range API change (regression)¶
Id |
5222 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Closed by |
Chris Johns |
Created |
2025-02-27T21:44:09.559Z |
Closed |
2025-10-02T22:52:45.561Z |
Updated |
2025-10-02T22:52:45.635Z |
Milestone |
6.2 |
Labels |
api |
Link |
|
Merges |
0 |
The following discussion from !436 should be addressed:
[] @chris started a discussion: (+4 comments)
Yes I could add
CONFIGURE_MAXIMUM_PRIORITYwith255to resolve the problem in my application. Why should I? The code base that brought this problem to my attention was originally developed on RTEMS 4 on a Zynq and the user wants to use SMP?My investigation to understand the problem has raised a number of concerns and I do not think this MR is the place to discuss them. The MR may in the end be a suitable resolution however we need to first have a wider discussion.
I believe the changing of the priority range is a _regression_ with respect to the historical user interfaces until we decide otherwise. I do not remember a specific discussion about the range changing in regards to this context, the effects, other possible options or how we convey this to users? I believe a number of separate changes over a period of time have come together to bring about my concerns. Each piece on its own makes sense and seems reasonable however together there are issues. We need to respect our users, existing code and the need to make things as simple as possible simple configurations.
I am also using this specific example to bring about a policy change. API changes needs to be announced and a specific discussion happen for the change to accepted. Approval and merging of changes in isolation does not mean an acceptable of change. If this happens we need to discuss the impact, look at solutions I have labelled this MR API however I wonder if we need an
api-changelabel as well?—
A discourse topic discussing this issue can be found at https://users.rtems.org/t/scheduler-maximum-regression-in-rtems-6/78
Author: Chris Johns
2025-02-27T21:44:09.713Z
assigned to @chris
Author: Chris Johns
2025-02-27T21:45:07.643Z
changed the description
Author: Chris Johns
2025-02-28T02:19:24.550Z
changed the description
Author: Sebastian Huber
2025-03-05T13:15:56.927Z
The default SMP scheduler is an EDF scheduler. This has other implications. For example, the use of rate-monotonic objects changes drastically. If you want maximum backward compatibility, the default SMP scheduler could be changed back to deterministic priority.
Author: Chris Johns
2025-10-02T22:52:45.602Z
set status to Won’t do
5346 - Backport flashdev destructor changes to 6 branch¶
Id |
5346 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-09-23T00:00:31.514Z |
Closed |
2025-09-23T00:07:02.358Z |
Updated |
2025-09-23T19:36:15.569Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
Summary¶
The destructor changes were a critical bug fix that needs to be applied to 6 branch to allow for flashdev device destruction to occur correctly.
Steps to reproduce¶
Pre-set options¶
Author: Kinsey Moore
2025-09-23T00:00:31.691Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-09-23T00:00:31.806Z
set status to To do
Author: Kinsey Moore
2025-09-23T00:01:33.931Z
mentioned in merge request !741
Author: Kinsey Moore
2025-09-23T00:07:02.438Z
set status to Done
Author: Kinsey Moore
2025-09-23T19:36:15.537Z
assigned to @opticron
5130 - aarch64/raspberrypi: improve UART¶
Id |
5130 |
State |
closed |
Type |
ISSUE |
Author |
Ning Yang |
Closed by |
Kinsey Moore |
Created |
2024-09-20T07:33:39.925Z |
Closed |
2024-10-28T15:12:37.664Z |
Updated |
2025-09-19T00:51:12.909Z |
Milestone |
6.2 |
Link |
|
Merges |
1 |
Add support for four new ports, UART2-UART5.
Add build options to allow console device configuration.
Segregate device-specific definitions from the device family files. X macros
are used to maintain a single source of truth and have the configuration done at compile-time * Add raspberrypi_uart_init() to make it convenient for users to install uart devices
Author: Ning Yang
2024-09-20T07:38:15.123Z
changed the description
Author: Ning Yang
2024-09-20T07:38:53.845Z
mentioned in merge request !234
5218 - RTEMS Release 6.1 build error texinfo-7.0.3 on arm64-apple-darwin24.3.0-1¶
Id |
5218 |
State |
closed |
Type |
ISSUE |
Author |
Heinz Junkes |
Closed by |
Heinz Junkes |
Created |
2025-02-16T12:47:08.095Z |
Closed |
2025-02-18T16:24:10.787Z |
Updated |
2025-09-19T00:38:52.644Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
Summary¶
RTEMS Tools Project - Source Builder Error Report
Build: error: building texinfo-7.0.3-arm64-apple-darwin24.3.0-1
Command Line: ../source-builder/sb-set-builder --prefix=/Volumes/Epics/RTEMS_MVME6100_legacy_stack/rtems/6.1 6/rtems-powerpc
Python: 3.12.8 (main, Feb 9 2025, 14:26:38) [Clang 16.0.0 (clang-1600.0.26.4)]
RSB: not a valid repo
Darwin Mac.fritz.box 24.3.0 Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:23 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6020 arm64
Tail of the build log:
/opt/homebrew/opt/perl/lib/perl5/5.40/darwin-thread-multi-2level/CORE/XSUB.h:340:38: note: expanded from macro 'XSRETURN_EMPTY'
340 | #define XSRETURN_EMPTY STMT_START { XSRETURN(0); } STMT_END
...
/opt/homebrew/opt/perl/lib/perl5/5.40/darwin-thread-multi-2level/CORE/XSUB.h:325:5: note: expanded from macro 'XSRETURN'
325 | STMT_START { \\
| ^~~~~~~~~~
../../../../texinfo-7.0.3/tp/Texinfo/XS/ppport.h:4001:28: note: expanded from macro 'STMT_START'
4001 | # define STMT_START (void)( /* gcc supports ``({ STATEMENTS; })'' */
| ^
parsetexi/Parsetexi.c:626:5: note: '{' token is here
626 | XSRETURN_EMPTY;
junkes@Mac rtems % tail rsb-report-texinfo-7.0.3-arm64-apple-darwin24.3.0-1.txt
mv -f parsetexi/.deps/Parsetexi_la-context_stack.Tpo parsetexi/.deps/Parsetexi_la-context_stack.Plo
mv -f parsetexi/.deps/Parsetexi_la-debug.Tpo parsetexi/.deps/Parsetexi_la-debug.Plo
mv -f parsetexi/.deps/Parsetexi_la-convert.Tpo parsetexi/.deps/Parsetexi_la-convert.Plo
make[4]: *** [all-recursive] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
shell cmd failed: /bin/sh -ex /Volumes/Epics/RTEMS_MVME6100_legacy_stack/rtems-source-builder-6.1/rtems/build/texinfo-7.0.3-arm64-apple-darwin24.3.0-1/do-build
error: building texinfo-7.0.3-arm64-apple-darwin24.3.0-1%
Steps to reproduce¶
#!/bin/bash
#RTEMS development
export RTEMS_VERSION=6
export RTEMS_RELEASE=6.1
export RTEMS_CPU=powerpc
export RTEMS_BSP=beatnik
export RTEMS_ARCH=${RTEMS_CPU}-rtems${RTEMS_VERSION}
SCRIPT=$(readlink -f $0)
export RTEMS_ROOT=`dirname $SCRIPT`/rtems/${RTEMS_RELEASE}
#install rsb
wget https://ftp.rtems.org/pub/rtems/releases/6/6.1/sources/rtems-source-builder-6.1.tar.xz
tar Jxf rtems-source-builder-6.1.tar.xz
#build the tools, kernel and all packages for the beatnik board
cd rtems-source-builder-6.1/rtems
../source-builder/sb-set-builder \\
--prefix=${RTEMS_ROOT} \\
6/rtems-${RTEMS_CPU}
do-build in rtems-source-builder-6.1/rtems/build/texinfo-7.0.3-arm64-apple-darwin24.3.0-1
...
libtool: link: ( cd ".libs" && rm -f "MiscXS.la" && ln -s "../MiscXS.la" "MiscXS.la" )
/bin/sh ./libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I../../../../texinfo-7.0.3/tp/Texinfo/XS -I../../../../texinfo-7.0.3/tp/Texinfo/XS/parsetexi -I../../../../texinfo-7.0.3/tp/Texinfo/XS -I../../../../texinfo-7.0.3/tp/Texinfo/XS/gnulib/lib -I./gnulib/lib -DDATADIR=\\"/Volumes/Epics/RTEMS_MVME6100_legacy_stack/rtems-source-builder-6.1/rtems/build/tmp/sb-501-internal/share\\" -fno-common -DPERL_DARWIN -mmacosx-version-min=15.2 -DNO_THREAD_SAFE_QUERYLOCALE -DNO_POSIX_2008_LOCALE -fno-strict-aliasing -pipe -fstack-protector-strong -O3 -DVERSION=\\"0\\" -DXS_VERSION=\\"0\\" -I/opt/homebrew/opt/perl/lib/perl5/5.40/darwin-thread-multi-2level/CORE -MT parsetexi/Parsetexi_la-api.lo -MD -MP -MF parsetexi/.deps/Parsetexi_la-api.Tpo -c -o parsetexi/Parsetexi_la-api.lo `test -f 'parsetexi/api.c' || echo '../../../../texinfo-7.0.3/tp/Texinfo/XS/'`parsetexi/api.c
libtool: compile: cc -DHAVE_CONFIG_H -I. -I../../../../texinfo-7.0.3/tp/Texinfo/XS -I../../../../texinfo-7.0.3/tp/Texinfo/XS/parsetexi -I../../../../texinfo-7.0.3/tp/Texinfo/XS -I../../../../texinfo-7.0.3/tp/Texinfo/XS/gnulib/lib -I./gnulib/lib -DDATADIR=\\"/Volumes/Epics/RTEMS_MVME6100_legacy_stack/rtems-source-builder-6.1/rtems/build/tmp/sb-501-internal/share\\" -fno-common -DPERL_DARWIN -mmacosx-version-min=15.2 -DNO_THREAD_SAFE_QUERYLOCALE -DNO_POSIX_2008_LOCALE -fno-strict-aliasing -pipe -fstack-protector-strong -O3 -DVERSION=\\"0\\" -DXS_VERSION=\\"0\\" -I/opt/homebrew/opt/perl/lib/perl5/5.40/darwin-thread-multi-2level/CORE -MT parsetexi/Parsetexi_la-api.lo -MD -MP -MF parsetexi/.deps/Parsetexi_la-api.Tpo -c ../../../../texinfo-7.0.3/tp/Texinfo/XS/parsetexi/api.c -fno-common -DPIC -o parsetexi/.libs/Parsetexi_la-api.o
../../../../texinfo-7.0.3/tp/Texinfo/XS/parsetexi/api.c:33:10: fatal error: 'libintl.h' file not found
33 | #include <libintl.h>
| ^~~~~~~~~~~
1 error generated.
homebrew gettext is installed:
junkes@Mac rtems % /opt/homebrew/bin/xgettext -V
xgettext (GNU gettext-tools) 0.23.1
Copyright (C) 1995-2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Ulrich Drepper.
Author: Heinz Junkes
2025-02-18T16:24:10.427Z
Fixed by ‘brew install texinfo”
Author: Chris Johns
2025-02-18T20:39:56.622Z
@junkes I built a set of tools on MacOs ARM64 yesterday without any brew packages without error.
5302 - Backport pthread_sigmask return fixup to 6 branch¶
Id |
5302 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-07-17T14:12:12.223Z |
Closed |
2025-07-31T01:42:54.897Z |
Updated |
2025-07-31T01:42:54.909Z |
Milestone |
6.2 |
Link |
|
Merges |
0 |
The following discussion from !546 should be addressed:
[] @gedare started a discussion: (+2 comments)
https://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_sigmask.html Upon successful completion, pthread_sigmask() shall return 0; otherwise, it shall return the corresponding error number. @joel do you want to backport this ?
Author: Kinsey Moore
2025-07-17T14:12:12.373Z
added rtems#10 as parent epic
Author: Joel Sherrill
2025-07-18T21:38:29.442Z
It wasn’t captured but… yes, please backport to 6
Author: Kinsey Moore
2025-07-31T01:42:52.074Z
assigned to @opticron
Author: Kinsey Moore
2025-07-31T01:42:54.944Z
set status to Done
5309 - Backport missing header guard and extern declarations to 6 branch¶
Id |
5309 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-07-23T20:14:31.002Z |
Closed |
2025-07-31T01:42:35.960Z |
Updated |
2025-07-31T01:42:35.972Z |
Milestone |
6.2 |
Link |
|
Merges |
1 |
The following discussion from !625 should be addressed:
[] @opticron started a discussion:
This needs to be backported to 6 branch.
Author: Kinsey Moore
2025-07-23T20:14:31.163Z
set status to To do
Author: Kinsey Moore
2025-07-23T20:19:07.237Z
mentioned in merge request !626
Author: Kinsey Moore
2025-07-23T20:19:17.777Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-07-25T01:11:53.050Z
mentioned in commit 84d4c11c3062d9773774e6a7465028dce4e94377
Author: Kinsey Moore
2025-07-25T01:11:53.235Z
mentioned in commit b1dbd9eeae9ad1c1dbc1b9593039e41e1101a4ce
Author: Kinsey Moore
2025-07-31T01:42:32.387Z
assigned to @opticron
Author: Kinsey Moore
2025-07-31T01:42:36.006Z
set status to Done
5313 - Backport use of generic TLS accessor¶
Id |
5313 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-07-27T22:41:21.386Z |
Closed |
2025-07-31T01:41:04.759Z |
Updated |
2025-07-31T01:41:04.772Z |
Milestone |
6.2 |
Labels |
cpukit::debugger |
Link |
|
Merges |
1 |
The following discussion from !636 should be addressed:
[] @opticron started a discussion:
This needs to be backported to 6 branch.
Author: Kinsey Moore
2025-07-27T22:41:21.564Z
added rtems#10 as parent epic
Author: Kinsey Moore
2025-07-27T22:41:21.664Z
set status to To do
Author: Kinsey Moore
2025-07-27T22:46:50.224Z
mentioned in merge request !637
Author: Kinsey Moore
2025-07-31T01:40:49.540Z
assigned to @opticron
Author: Kinsey Moore
2025-07-31T01:41:04.807Z
set status to Done
Author: Kinsey Moore
2025-07-31T01:41:05.354Z
The associated MR has been merged.
4956 - Deadlock caused by locking inversion in JFFS2¶
Id |
4956 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2023-09-20T16:58:43.000Z |
Closed |
2025-07-30T18:52:51.774Z |
Updated |
2025-07-30T18:52:51.787Z |
Milestone |
6.2 |
Labels |
priority::normal, tickettype::defect |
Link |
|
Merges |
0 |
When the code for delayed writes was added to support JFFS2 on NAND, it introduced a possible locking inversion when managing the delayed write work queue.
This has been partially addressed by fa85760c99a72b8186c70c896b98efe0d7cde2b6, but there are other issues with this code that need to be addressed as well.
First is that when not compiling with RTEMS_DEBUG, nodes are not automatically set as off the chain upon extraction and this behavior is depended upon.
~~Second is that protected (ISR-locked) chain calls are used when they are not necessary due to already being locked.~~ This code has been restructured and this component is no longer relevant.
Third is that the bug fixed by the referenced commit needs a test that verifies the fix.
Author: Trac Migrate
2023-09-26T00:41:07.000Z
Hey i’m interested working on this ticket would the nodes be set off only if
Author: Kinsey Moore
2023-09-26T13:16:46.000Z
Hey, thanks for the interest. I actually have a patch on the mailing list that just got approved for fixing this, so it should be going into the codebase shortly. I still need to write a test that produces the original issue, though.
Author: Trac Migrate
2023-09-26T13:38:00.000Z
In [changeset:”99c637fbd973a3d2f6e5adf38aac8f3f588cbb7e/rtems” 99c637f/rtems]:
cpukit/jffs2: Avoid use of off-chain semantics This reworks the JFFS2 delayed work queue to avoid use of on-chain/off-chain semantics since they vary in behavior under RTEMS_DEBUG and are not guaranteed to be safe to use in SMP systems. This adds all delayed work structs to the chain on FS init and does not remove them until umount. Updates #4956
Author: Kinsey Moore
2024-02-16T00:35:11.000Z
Owner set to @kinsey
Status changed from new to assigned
Author: Kinsey Moore
2024-05-02T23:19:35.303Z
A baseline set of tests has been added to the RTEMS testsuite to test JFFS2 on a simulated NAND device. This baseline set of tests does not trigger the original condition that necessitated this ticket and I have thus far been unable to trigger the deadlock from a test with rolled-back code.
Author: Kinsey Moore
2024-05-17T02:59:17.993Z
changed the description
Author: Gedare Bloom
2024-12-04T21:40:37.334Z
Author: Kinsey Moore
2025-07-30T18:51:59.645Z
changed the description
Author: Kinsey Moore
2025-07-30T18:52:51.829Z
set status to Done
Author: Kinsey Moore
2025-07-30T18:52:52.583Z
This issue has been resolved by rolling back to global locking.
5271 - Backport libdebugger TLS support to the RTEMS 6 branch¶
Id |
5271 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-06-17T19:15:41.599Z |
Closed |
2025-07-30T18:29:43.508Z |
Updated |
2025-07-30T18:29:43.582Z |
Milestone |
6.2 |
Labels |
arch:aarch64, cpukit::debugger |
Link |
|
Merges |
1 |
The following discussion from !517 should be addressed:
[] @opticron started a discussion:
This needs to be backported to the 6 branch.
Author: Kinsey Moore
2025-06-17T19:15:42.193Z
assigned to @opticron
Author: Kinsey Moore
2025-06-17T19:15:42.692Z
Author: Kinsey Moore
2025-06-17T19:19:46.270Z
mentioned in merge request !518
Author: Kinsey Moore
2025-07-30T18:29:43.561Z
set status to Done
5273 - Backport libdebugger setjmp fix to 6 branch¶
Id |
5273 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-06-18T18:52:51.524Z |
Closed |
2025-07-30T18:29:36.664Z |
Updated |
2025-07-30T18:29:36.746Z |
Milestone |
6.2 |
Labels |
arch:aarch64, cpukit::debugger |
Link |
|
Merges |
1 |
The following discussion from !523 should be addressed:
[] @opticron started a discussion:
This needs to be backported to 6.
Author: Kinsey Moore
2025-06-18T18:52:52.066Z
assigned to @opticron
Author: Kinsey Moore
2025-06-18T18:52:53.254Z
Author: Kinsey Moore
2025-06-18T18:55:47.388Z
mentioned in merge request !524
Author: Kinsey Moore
2025-06-19T22:52:52.933Z
mentioned in commit 3d8b56f10c9cabe8cc731ada636af59f71e8e10b
Author: Kinsey Moore
2025-07-30T18:29:36.723Z
set status to Done
4675 - sleep should be a thread cancellation point¶
Id |
4675 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2022-07-07T10:17:28.000Z |
Closed |
2025-07-25T14:20:23.129Z |
Updated |
2025-07-25T14:20:23.259Z |
Milestone |
6.2 |
Labels |
api::posix, priority::normal, tickettype::defect, version::6 |
Link |
|
Merges |
1 |
Original author: aoliva
GCC has worked around, in the libstdc++ testsuite, the fact that nanosleep (as well as sleep and clock_nanosleep) should be thread cancellation points, per POSIX, but RTEMS may want to make them so. https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597003.html
(I haven’t checked that other functions that should be thread cancellation points are, I only noticed that this one wasn’t, and decided to file this ticket because for other issues in which I explicitly identified RTEMS I got a request to do so)
Author: Trac Migrate
2022-07-07T12:40:48.000Z
Original author: aoliva
Thanks for reporting the issue. I think we have currently no cancellation points in RTEMS at all. I think this is intentional, so I would mark this bug as WONTFIX.
Author: Joel Sherrill
2023-03-18T17:43:07.000Z
Original author: aoliva
Do you have a test to show something isn’t right? sleep() and nanonsleep() ultimately call clock_nanosleep() and the requested blocking state is “STATES_WAITING_FOR_TIME | STATES_INTERRUPTIBLE_BY_SIGNAL”
https://git.rtems.org/rtems/tree/cpukit/posix/src/clocknanosleep.c#n77
RTEMS state bits consist of the type of object is being blocked on and attributes such as interruptible. It has been this way for a LONG time.
As a random thought, if you don’t build RTEMS with POSIX enabled, then POSIX signals are disabled and then this likely wouldn’t work.
Author: Joel Sherrill
2023-03-18T17:43:24.000Z
Original author: aoliva
Milestone set to %”6.1”
Author: Trac Migrate
2023-04-22T05:32:10.000Z
Original author: aoliva
The unpatched libstdc++ testcase is a test that shows the problem. An explicit pthread_testcancel shouldn’t be needed. Functions that are cancellation points should (as-if) call it implicitly.
Author: Joel Sherrill
2023-06-22T20:52:53.000Z
Original author: aoliva
Owner set to @kinsey
Status changed from new to assigned
Author: Amar Takhar
2024-05-17T00:42:51.649Z
Hi there Kinsey can this be moved to %6.2?
Author: Amar Takhar
2024-05-17T01:08:02.038Z
changed the description
Author: Kinsey Moore
2024-05-17T02:53:23.124Z
@joel Do you have opinions on this? It’s in my backlog of things to get to, but I have many things that come before it.
Author: Amar Takhar
2024-05-17T03:23:52.870Z
@opticron this was already moved to %6.2 :) .. Joel asked to move it.
Author: Kinsey Moore
2024-05-17T03:23:52.870Z
I saw that it got moved, but not the rationale. I was driving at the time.
Author: Amar Takhar
2024-05-17T03:23:52.870Z
Ah, makes sense I should have noted that it was Joel that asked, too.
Author: Gedare Bloom
2024-12-04T21:40:37.120Z
Author: Kinsey Moore
2025-07-21T16:36:59.448Z
mentioned in merge request !616
Author: Kinsey Moore
2025-07-24T22:37:00.486Z
mentioned in merge request !623
5281 - RTEMS 6.1 GR740 Multiprocessing build fails¶
Id |
5281 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Matteo Concas |
Closed by |
Matteo Concas |
Created |
2025-06-24T20:26:51.026Z |
Closed |
2025-07-04T06:49:45.863Z |
Updated |
2025-07-04T06:49:45.876Z |
Milestone |
6.2 |
Link |
|
Merges |
1 |
Summary¶
When building the GR740 BSP with RTEMS_MULTIPROCESSING set to true , the build will fail.
Steps to reproduce¶
The INI file contents are:
[DEFAULT]
RTEMS_POSIX_API = True
[sparc/gr740_mp]
INHERIT=gr740
RTEMS_MULTIPROCESSING=True
I configure the Waf system with:
./waf configure --prefix=$RTEMS_PREFIX --rtems-config=gr740.ini
And then ./waf to build the BSP. I get the following output:
Waf: Entering directory `/scratch/matteo/rtems-build/src/rtems-6.1/build'
Waf: Leaving directory `/scratch/matteo/rtems-build/src/rtems-6.1/build'
'build' finished successfully (0.081s)
Waf: Entering directory `/scratch/matteo/rtems-build/src/rtems-6.1/build/sparc/gr740_mp'
[ 167/1641] Compiling bsps/sparc/leon3/clock/ckinit.c
In file included from ../../../bsps/sparc/leon3/clock/ckinit.c:46:
../../../bsps/sparc/leon3/clock/ckinit.c: In function 'leon3_clock_initialize':
../../../bsps/sparc/leon3/include/bsp/leon3.h:221:5: error: 'leon3_timer_core_index' undeclared (first use in this function); did you mean 'leon3_timecounter'?
221 | ( leon3_timer_core_index != 0 ? 0 : 2 * LEON3_Cpu_Index )
| ^~~~~~~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/clock/ckinit.c:181:36: note: in expansion of macro 'LEON3_CLOCK_INDEX'
181 | timer = &LEON3_Timer_Regs->timer[LEON3_CLOCK_INDEX];
| ^~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/include/bsp/leon3.h:221:5: note: each undeclared identifier is reported only once for each function it appears in
221 | ( leon3_timer_core_index != 0 ? 0 : 2 * LEON3_Cpu_Index )
| ^~~~~~~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/clock/ckinit.c:181:36: note: in expansion of macro 'LEON3_CLOCK_INDEX'
181 | timer = &LEON3_Timer_Regs->timer[LEON3_CLOCK_INDEX];
| ^~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/clock/../../../shared/dev/clock/clockimpl.h: In function '_Clock_Initialize':
../../../bsps/sparc/leon3/include/bsp/leon3.h:221:5: error: 'leon3_timer_core_index' undeclared (first use in this function); did you mean 'leon3_timecounter'?
221 | ( leon3_timer_core_index != 0 ? 0 : 2 * LEON3_Cpu_Index )
| ^~~~~~~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/clock/ckinit.c:137:49: note: in expansion of macro 'LEON3_CLOCK_INDEX'
137 | #define Adjust_clkirq_for_node() do { clkirq += LEON3_CLOCK_INDEX; } while(0)
| ^~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/clock/ckinit.c:145:7: note: in expansion of macro 'Adjust_clkirq_for_node'
145 | Adjust_clkirq_for_node(); \\
| ^~~~~~~~~~~~~~~~~~~~~~
../../../bsps/sparc/leon3/clock/../../../shared/dev/clock/clockimpl.h:249:3: note: in expansion of macro 'Clock_driver_support_find_timer'
249 | Clock_driver_support_find_timer();
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Waf: Leaving directory `/scratch/matteo/rtems-build/src/rtems-6.1/build/sparc/gr740_mp'
Build failed
-> task in '/bsps/sparc/leon3/obj' failed with exit status 1 (run with -v to display more information)
Expected behaviour¶
Build should complete successfully.
Possible fix¶
From my own investigation this comes from bsps/sparc/leon3/include/bsp/leon3.h . leon3_timer_core_index is only declared if LEON3_GPTIMER_BASE is not defined but later in the file the LEON3_CLOCK_INDEX macro is defined in the following way:
/**
* @brief This constant defines the index of the GPTIMER timer used by the
* clock driver.
*/
#if defined(RTEMS_MULTIPROCESSING)
#define LEON3_CLOCK_INDEX \\
( leon3_timer_core_index != 0 ? 0 : 2 * LEON3_Cpu_Index )
#else
#define LEON3_CLOCK_INDEX 0
#endif
So when RTEMS_MULTIPROCESSING is used the LEON3_CLOCK_INDEX will expand to use the leon3_timer_core_index variable which won’t be declared as the GPTIMER base is defined for the GR740 BSP.
I don’t fully understand why the LEON3_CLOCK_INDEX macro is defined this way but changing it’s define conditional to:
#if defined(RTEMS_MULTIPROCESSING) && !defined(LEON3_GPTIMER_BASE)
Will make the BSP build successfully, I haven’t had the time to test this fix, it might break something else at runtime.
Author: Gedare Bloom
2025-06-24T20:26:51.204Z
cloned from #5258
Author: Gedare Bloom
2025-06-24T20:28:54.720Z
Author: Gedare Bloom
2025-06-24T20:30:26.097Z
@matteo.concas
Author: Gedare Bloom
2025-06-24T20:30:46.754Z
assigned to @matteo.concas
Author: Gedare Bloom
2025-06-24T20:31:37.061Z
mentioned in merge request !532
5288 - Backport RISC-V Double Trap extension fix to 6¶
Id |
5288 |
State |
closed |
Type |
ISSUE |
Author |
Matteo Concas |
Closed by |
Matteo Concas |
Created |
2025-07-03T08:07:26.897Z |
Closed |
2025-07-04T06:48:43.417Z |
Updated |
2025-07-04T06:48:43.431Z |
Milestone |
6.2 |
Labels |
arch:riscv |
Link |
|
Merges |
1 |
If the Double Trap Extension is implemented, the MDT bit of the mstatus (or mstatush in RV32) register will be set when a trap is to be taken.
The MIE (Machine Interrupt Enable) bit can only be set to 1 if the MDT bit is zero.
Thus, we need to clear MDT first if we want to enable interrupts when dispatching a thread.
MDT is also cleared in register a1 before restoring the interrupt frame as writing 1 to MDT will cause MIE to be set to 0. In RV64 this happens regardless of the value written to MIE in the same write.
In RV32, MDT is in mstatush so we do not need to clear during restore as this register is not restored.
With this change all 60 SMP tests pass (compared to 20/60 before the fix). The tests have been run on hardware using two RV64 CPUs that implement the double trap extension.
Author: Matteo Concas
2025-07-03T08:10:45.328Z
mentioned in merge request !548
Author: Kinsey Moore
2025-07-03T13:10:32.134Z
added rtems#10 as parent epic
5283 - Backport 6.2: bsps/noelv: Fix using console in polled mode¶
Id |
5283 |
State |
closed |
Type |
ISSUE |
Author |
Matteo Concas |
Closed by |
Gedare Bloom |
Created |
2025-06-27T07:40:58.098Z |
Closed |
2025-06-28T15:36:17.903Z |
Updated |
2025-06-28T15:36:17.916Z |
Milestone |
6.2 |
Link |
|
Merges |
1 |
Summary¶
bsps/noelv: Fix using console in polled mode
The console driver needs BSP_CONSOLE_USE_INTERRUPTS to be defined or it does not build. The intent was to use polled mode if the macro was equal to zero but not using interrupt means the macro won’t be defined instead.
This is the faulty code:
if (BSP_CONSOLE_USE_INTERRUPTS) {
handler = &apbuart_handler_interrupt;
}
In bsps/riscv/noel/console/console-config.c .
Steps to reproduce¶
Create a INI with the following contents:
[riscv/noel64imafd_polling]
INHERIT = noel64imafd
RTEMS_SMP = True
BSP_CONSOLE_USE_INTERRUPTS = 0
Build the RTEMS kernel, it will fail to build due to BSP_CONSOLE_USE_INTERRUPTS being undefined.
Expected behaviour¶
BSP should build successfully.
Author: Matteo Concas
2025-06-27T07:43:21.023Z
mentioned in merge request !537
Author: Kinsey Moore
2025-06-27T12:59:09.680Z
Author: Matteo Concas
2025-06-28T15:35:42.404Z
mentioned in commit dd490c5c2d02e472c83b7052612b554e8b74358f
Author: Gedare Bloom
2025-06-28T15:36:18.541Z
fixed in https://gitlab.rtems.org/rtems/rtos/rtems/-/commit/dd490c5c2d02e472c83b7052612b554e8b74358f
5254 - i386/pc BSP ATA driver asserts with node errors on FAT disk mount¶
Id |
5254 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Closed by |
Kinsey Moore |
Created |
2025-05-28T02:54:29.731Z |
Closed |
2025-05-30T13:34:36.579Z |
Updated |
2025-05-30T13:34:36.593Z |
Milestone |
6.2 |
Labels |
arch:i386 |
Link |
|
Merges |
1 |
Summary¶
With RTEMS_DEBUG enabled the PC ATA driver asserts with a failure because a node’s link pointer is not set to NULL. The assert is:
assertion "_Chain_Is_node_off_chain( the_node )" failed: file "../../../cpukit/include/rtems/score/chainimpl.h", line 691, function: _Chain_Append_unprotected
A back trace is:
(gdb) bt
#0 0x00162c55 in bsp_reset (source=source@entry=RTEMS_FATAL_SOURCE_ASSERT, code=code@entry=1872624) at ../../../bsps/i386/pc386/start/bspreset.c:39
#1 0x00161b15 in bsp_fatal_extension (source=RTEMS_FATAL_SOURCE_ASSERT, always_set_to_false=false, code=1872624) at ../../../bsps/shared/start/bspfatal-default.c:213
#2 0x001189b3 in _User_extensions_Iterate (arg=arg@entry=0x1c92b8, visitor=0x118900 <_User_extensions_Fatal_visitor>, direction=CHAIN_ITERATOR_FORWARD) at ../../../cpukit/score/src/userextiterate.c:194
#3 0x0011321f in _User_extensions_Fatal (error=1872624, source=RTEMS_FATAL_SOURCE_ASSERT) at ../../../cpukit/include/rtems/score/userextimpl.h:467
#4 _Terminate (the_source=the_source@entry=RTEMS_FATAL_SOURCE_ASSERT, the_error=the_error@entry=1872624) at ../../../cpukit/score/src/interr.c:66
#5 0x001077ec in rtems_fatal (fatal_code=1872624, fatal_source=RTEMS_FATAL_SOURCE_ASSERT) at ../../../cpukit/include/rtems/fatal.h:160
#6 __assert_func (file=file@entry=0x189a64 "../../../cpukit/include/rtems/score/chainimpl.h", line=691, func=0x1a0378 <__func__.0> "_Chain_Append_unprotected", failedexpr=0x189a3c "_Chain_Is_node_off_chain( the_node )") at ../../../cpukit/libcsupport/src/__assert.c:71
#7 0x0016c03d in _Chain_Append_unprotected (the_node=0x1cbbc0, the_chain=0x1aae4c <ata_ide_ctrls+44>) at ../../../cpukit/include/rtems/score/chainimpl.h:691
#8 0x0016c0dc in _Chain_Append_unprotected (the_node=0x1cbbc0, the_chain=0x1aae4c <ata_ide_ctrls+44>) at ../../../cpukit/sapi/src/chainprotected.c:99
#9 rtems_chain_append (chain=chain@entry=0x1aae4c <ata_ide_ctrls+44>, node=0x1cbbc0) at ../../../cpukit/sapi/src/chainprotected.c:97
#10 0x00160cb9 in ata_add_to_controller_queue (ctrl_minor=0, areq=0x1cbbc0) at ../../../bsps/shared/dev/ide/ata.c:540
#11 0x00160ea1 in ata_io_data_request (ata_dev=<optimized out>, req=0x1c9450) at ../../../bsps/shared/dev/ide/ata.c:228
#12 ata_ioctl (dd=0x1bee44, cmd=3222815233, argp=0x1c9450) at ../../../bsps/shared/dev/ide/ata.c:949
#13 0x00102f5e in rtems_bdbuf_execute_transfer_request (dd=dd@entry=0x1bee44, req=req@entry=0x1c9450, cache_locked=cache_locked@entry=true) at ../../../cpukit/libblock/src/bdbuf.c:1878
#14 0x001032c9 in rtems_bdbuf_execute_read_request (dd=dd@entry=0x1bee44, bd=<optimized out>, bd@entry=0x1bbe2c, transfer_count=transfer_count@entry=1) at ../../../cpukit/libblock/src/bdbuf.c:1994
#15 0x001044df in rtems_bdbuf_read (dd=dd@entry=0x1bee44, block=block@entry=0, bd_ptr=bd_ptr@entry=0x1c9558) at ../../../cpukit/libblock/src/bdbuf.c:2094
#16 0x00131f67 in rtems_bdpart_read_record (dd=0x1bee44, index=0, block=0x1c9558) at ../../../cpukit/libblock/src/bdpart-read.c:220
#17 0x00132190 in rtems_bdpart_read (disk_name=disk_name@entry=0x1ca62e "/dev/hda", format=format@entry=0x1c95dc, pt=pt@entry=0x1c9630, count=count@entry=0x1c95d4) at ../../../cpukit/libblock/src/bdpart-read.c:273
#18 0x00119a5e in rtems_bdpart_shell_main (argc=2, argv=0x1c9b30) at ../../../cpukit/libmisc/shell/fdisk.c:236
#19 0x0012dacd in shell_main_loop (shell_env=shell_env@entry=0x1c9ec8, interactive=interactive@entry=true, line_editor_output=<optimized out>) at ../../../cpukit/libmisc/shell/shell.c:1215
#20 0x0012ed18 in rtems_shell_main_loop (shell_env=shell_env@entry=0x1c9ec8) at ../../../cpukit/libmisc/shell/shell.c:1383
#21 0x0012ed38 in rtems_shell_task (task_argument=1875656) at ../../../cpukit/libmisc/shell/shell.c:1038
#22 0x00115adb in _Thread_Handler () at ../../../cpukit/score/src/threadhandler.c:164
#23 0xa5a5a5a5 in ?? ()
Steps to reproduce¶
INI file:
[DEFAULT]
RTEMS_DEBUG = True
RTEMS_POSIX_API = True
[i386/pc686]
BUILD_TESTS = True
Run the fileio.exe test, enter the shell and then enter the following command:
fdisk /dev/hda
The shell session is:
*** BEGIN OF TEST FILE I/O ***
*** TEST VERSION: 7.0.0.34c362fee100659e36a6945204f77e71cb1c2f7e
*** TEST STATE: USER_INPUT
*** TEST BUILD: RTEMS_DEBUG RTEMS_POSIX_API
*** TEST TOOLS: 13.3.0 20240521 (RTEMS 7, RSB 170160cb918e7c68b4b35d8f0a42db6df81168e7, Newlib 1b3dcfd)
Press any key to start file I/O sample (20s remaining)
=========================
RTEMS FILE I/O Test Menu
=========================
p -> part_table_initialize
f -> mount all disks in fs_table
l -> list file
r -> read file
w -> write file
s -> start shell
Enter your selection ==>s
Creating /etc/passwd and group with four useable accounts:
root/pwd
test/pwd
rtems/NO PASSWORD
chroot/NO PASSWORD
Only the root user has access to all available commands.
=========================
starting shell
=========================
Welcome to rtems-7.0.0 (Intel i386/Pentium/pc686)
Copyright (C) 1989, 2021 RTEMS Project and contributors
Login into RTEMS
/dev/foobar login: root
Password:
RTEMS Shell on /dev/foobar. Use 'help' to list commands.
SHLL [/] # fdisk /dev/hda
assertion "_Chain_Is_node_off_chain( the_node )" failed: file "../../../cpukit/include/rtems/score/chainimpl.h", line 691, function: _Chain_Append_unprotected
Pre-set options¶
Author: Chris Johns
2025-05-28T02:54:30.004Z
cloned from #5253
Author: Chris Johns
2025-05-28T02:54:43.589Z
assigned to @chris
Author: Chris Johns
2025-05-28T02:54:53.933Z
Author: Chris Johns
2025-05-28T02:56:00.050Z
changed title from i38{-p-}/pc BSP ATA driver asserts with node errors on FAT disk mount to i38{+6+}/pc BSP ATA driver asserts with node errors on FAT disk mount
Author: Chris Johns
2025-05-28T03:02:54.791Z
mentioned in merge request !492
Author: Chris Johns
2025-05-30T13:34:27.984Z
mentioned in commit cb3fba044770f0bb6a96bd2b93e09df90d1e2e34
5232 - Backport “spec: Install missing header files for GRLIB and SPARC” to 6 branch¶
Id |
5232 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Kinsey Moore |
Created |
2025-03-26T15:53:40.588Z |
Closed |
2025-03-26T16:50:40.530Z |
Updated |
2025-03-26T16:50:40.542Z |
Milestone |
6.2 |
Labels |
grlib |
Link |
|
Merges |
2 |
The following discussion from !458 should be addressed:
[] @joel started a discussion: (+1 comment)
Is this also being applied to the 6 branch?
Author: Kinsey Moore
2025-03-26T15:53:40.797Z
assigned to @opticron
Author: Kinsey Moore
2025-03-26T15:53:41.118Z
Author: Kinsey Moore
2025-03-26T15:54:02.665Z
Author: Kinsey Moore
2025-03-26T16:00:38.727Z
changed the description
Author: Matteo Concas
2025-03-26T16:48:52.616Z
mentioned in merge request !459
5173 - powerpc/qoriq: Avoid spurious interrupt fatal errors¶
Id |
5173 |
State |
closed |
Type |
ISSUE |
Author |
Sebastian Huber |
Assignee(s) |
Sebastian Huber |
Closed by |
Gedare Bloom |
Created |
2024-12-05T23:47:28.576Z |
Closed |
2025-02-07T23:22:10.064Z |
Updated |
2025-02-11T05:38:23.897Z |
Milestone |
6.2 |
Labels |
arch:powerpc |
Link |
|
Merges |
3 |
Summary¶
The interrupt dispatching routine erroneously invokes the fatal error handler if a spurious interrupt is acknowledged.
Pre-set options¶
Author: Sebastian Huber
2024-12-05T23:47:28.686Z
assigned to @sebhub
Author: Sebastian Huber
2024-12-05T23:47:36.803Z
cloned to #5174
Author: Sebastian Huber
2024-12-05T23:47:47.386Z
Author: Sebastian Huber
2024-12-06T10:22:32.171Z
mentioned in merge request !345
Author: Chris Johns
2024-12-22T03:38:40.991Z
Author: Gedare Bloom
2025-02-07T23:22:09.483Z
Fixed in e421c922a87842f0613a269054acd041e46c91cd
Author: Sebastian Huber
2025-02-11T05:38:23.477Z
mentioned in commit e421c922a87842f0613a269054acd041e46c91cd
5205 - Back port “grlib/occan: Fix baud rate calculation” to 6¶
Id |
5205 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Closed by |
Gedare Bloom |
Created |
2025-02-07T15:07:07.522Z |
Closed |
2025-02-07T20:37:37.624Z |
Updated |
2025-02-11T05:38:23.820Z |
Milestone |
6.2 |
Link |
|
Merges |
3 |
The following discussion from !340 should be addressed:
[] @gedare started a discussion: (+1 comment)
@thesummer Should this be back-ported to 6?
Yes. @thesummer please use this issue to back port the fix to 6.
Author: Joel Sherrill
2025-02-07T15:07:26.994Z
Author: Gedare Bloom
2025-02-07T15:51:54.551Z
mentioned in merge request !404
Author: Jan Sommer
2025-02-11T05:38:23.247Z
mentioned in commit a0e4be53f4e30ee02d6d0c9221d613d18c72f426
5189 - Backport libdl ARM trampoline crash fix¶
Id |
5189 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Kinsey Moore |
Closed by |
Chris Johns |
Created |
2025-01-23T22:24:29.147Z |
Closed |
2025-01-24T00:10:34.134Z |
Updated |
2025-02-11T05:38:23.668Z |
Milestone |
6.2 |
Labels |
arch:arm, cpukit::dl |
Link |
|
Merges |
3 |
Summary¶
When a trampoline is not aligned on a word boundary and a ldr.w pc,[pc] instruction is generated, the address loaded is not pc+4, but instead pc+2.
Author: Kinsey Moore
2025-01-23T22:24:29.300Z
assigned to @opticron
Author: Kinsey Moore
2025-01-23T22:24:29.649Z
Author: Kinsey Moore
2025-01-23T22:26:00.055Z
mentioned in merge request !367
Author: Chris Johns
2025-01-24T00:10:28.724Z
changed title from Backpor{-r-}t libdl ARM trampoline crash fix to Backport libdl ARM trampoline crash fix
Author: Ranulfo Raphael
2025-02-11T05:38:23.161Z
mentioned in commit 84c2cf3da9983ef7eadb11d4a676449d6b3ef875
4958 - NTP broadcast client fails to open sockets on lwIP¶
Id |
4958 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Trac Migrate |
Closed by |
Kinsey Moore |
Created |
2023-10-04T19:42:57.000Z |
Closed |
2025-01-31T18:30:49.585Z |
Updated |
2025-01-31T18:30:49.660Z |
Milestone |
6.2 |
Labels |
network::lwip, priority::normal, tickettype::defect, version::6 |
Link |
|
Merges |
0 |
Reproduction: * Install lwIP on top of a compatible BSP * Modify the existing ntp01 test to use the broadcast client * Set NTP_DEBUG to 1 * Replace the first two lines of etc_ntp_conf with: * broadcastclient * disable auth * Build rtems-net-services against the installed BSP with lwIP network stack * Run the modified ntp01 test
Expected result: NTP opens broadcast listener successfully.
Actual result: NTP fails to open broadcast listener with error message: bind(37) AF_INET 0.0.0.0#123 flags 0x409 failed: Address already in use
Workaround: In open_socket() in bsd/freebsd/contrib/ntp/ntpd/ntp_io.c, there is a test for wildcard addresses inside a OS_NEEDS_REUSEADDR_FOR_IFADDRBIND conditional. If the set_wildcard_reuse() call is made unconditional, the socket creation succeeds.
The root cause is that behavior differs between LibBSD and lwIP. On lwIP, early-bound wildcard and non-wildcard address bindings succeed, but late-bound wildcard address bindings fail. Once any any address is bound, lwIP will fail to bind any further wildcard sockets. Either we can change lwIP’s behavior to be closer to LibBSD or we can alter the NTP client to check for lwIP or blindly apply the address reuse flags.
Author: Kinsey Moore
2023-10-04T19:44:27.000Z
Description changed
Reproduction: * Install lwIP on top of a compatible BSP * Modify the existing ntp01 test to use the broadcast client - ** Set NTP_DEBUG to 1 ? - + * Set NTP_DEBUG to 1 ? + - ** Replace the first two lines of etc_ntp_conf with: ? - + * Replace the first two lines of etc_ntp_conf with: ? + - *** broadcastclient ? -- + * broadcastclient ? ++ - *** disable auth ? -- + * disable auth ? ++ * Build rtems-net-services against the installed BSP with lwIP network stack * Run the modified ntp01 test Expected result: NTP opens broadcast listener successfully. Actual result: NTP fails to open broadcast listener with error message: bind(37) AF_INET 0.0.0.0#123 flags 0x409 failed: Address already in use Workaround: In open_socket() in bsd/freebsd/contrib/ntp/ntpd/ntp_io.c, there is a test for wildcard addresses inside a OS_NEEDS_REUSEADDR_FOR_IFADDRBIND conditional. If the set_wildcard_reuse() call is made unconditional, the socket creation succeeds. The root cause is that behavior differs between LibBSD and lwIP. On lwIP, early-bound wildcard and non-wildcard address bindings succeed, but late-bound wildcard address bindings fail. Once any any address is bound, lwIP will fail to bind any further wildcard sockets. Either we can change lwIP's behavior to be closer to LibBSD or we can alter the NTP client to check for lwIP or blindly apply the address reuse flags.
Author: Chris Johns
2023-10-04T21:30:43.000Z
I think NTP is using _normal_ behavior so lwIP is not compliant in this case. Adding a work around to NTP solves this problem but leaves the issue present other packages may trip over.
Have you asked lwIP about this?
Author: Kinsey Moore
2023-10-05T17:08:40.000Z
I haven’t. This was an issue I noticed and wanted to document that it existed with current thoughts, but I hadn’t moved beyond that yet since the broadcast client isn’t on my priority list at the moment. I’ll agree with you that fixing lwIP to be more “normal” is probably the right solution. I’ll get more context from lwIP.
Author: Gedare Bloom
2024-12-04T21:40:36.490Z
changed the description
Author: Gedare Bloom
2024-12-04T21:40:37.588Z
Author: Kinsey Moore
2025-01-31T18:30:49.722Z
moved to rtems/pkg/rtems-net-services#10
5146 - Follow-up from “Draft: timespec.h, etc.: Eliminate use of 32-bit for time_t”¶
Id |
5146 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Joel Sherrill |
Closed by |
Kinsey Moore |
Created |
2024-11-08T00:37:24.402Z |
Closed |
2025-01-24T01:08:51.602Z |
Updated |
2025-01-24T01:08:52.058Z |
Milestone |
6.2 |
Labels |
rtems::score |
Link |
|
Merges |
1 |
The following discussion from !175 should be addressed:
[] @sebhub started a discussion: (+2 comments)
Add test case to sptchimespec01 which uses a > 32-bit time?
Author: Chris Johns
2024-11-08T00:37:24.525Z
assigned to @joel
Author: zack liang
2024-11-09T22:19:35.699Z
hey @joel would like to work on this just tell me where the tests file is
Author: zack liang
2024-11-15T01:43:13.170Z
mentioned in merge request !314
Author: Joel Sherrill
2024-12-04T00:56:31.646Z
Author: Gedare Bloom
2024-12-04T21:40:37.917Z
5107 - timespecaddto.c: Use of 32-bit time_t¶
Id |
5107 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Joel Sherrill |
Closed by |
Chris Johns |
Created |
2024-08-07T21:57:13.967Z |
Closed |
2024-11-08T00:40:35.581Z |
Updated |
2024-11-08T00:40:35.686Z |
Milestone |
6.2 |
Labels |
rtems::score, scan::coverity |
Link |
|
Merges |
1 |
Summary¶
Coverity CID 1512527
Coverity spotted this where time_t variables/structure elements are assigned to uint32_t. Notice that the return type is uint32_t which propagates to callers of this such as rtems_timespec_add_to().
46 uint32_t _Timespec_Add_to(
47 struct timespec *time,
48 const struct timespec *add
49)
50{
CID 1512527: (#1 of 1): Use of 32-bit time_t (Y2K38_SAFETY)
1. store_truncates_time_t: A time_t value is stored in an integer with too few bits to accommodate it. The expression add->tv_sec is cast to uint32_t.
51 uint32_t seconds = add->tv_sec;
Steps to reproduce¶
Author: Joel Sherrill
2024-08-07T21:57:14.149Z
assigned to @joel
Author: Joel Sherrill
2024-08-07T22:01:06.155Z
mentioned in merge request !175
4964 - rtems-test can hang indefinitely¶
Id |
4964 |
State |
closed |
Type |
ISSUE |
Author |
Kinsey Moore |
Assignee(s) |
Trac Migrate |
Created |
2023-11-07T15:20:21.000Z |
Updated |
2023-11-07T21:06:51.000Z |
Milestone |
6.2 |
Labels |
priority::low, resolution::duplicate, tickettype::defect, tool::test, version::6 |
Link |
|
Merges |
0 |
When using the RTEMS automated tester configured with TFTP, there is a state that can occur in which the tester never times out a test. This was discovered when testing with the AArch64 Xilinx ZynqMP BSP where the board did not actually power on even though it was instructed to do so. This left the tester running the TFTP server waiting more than 4 full days (left to run over a long weekend) for the target to start without progressing to the next test.
The failure to start on the target side was due to a missing minimum settling time between off and on states that is apparently influenced by the environment.
Author: Chris Johns
2023-11-07T20:52:08.000Z
Can you please try https://lists.rtems.org/pipermail/devel/2023-October/076519.html ?
Looks like I forgot to push it.
Author: Chris Johns
2023-11-07T21:06:51.000Z
Resolution set to ~”duplicate”
Status changed from new to closed
This is a duplicate of #4959
5236 - Runtime symbols loading is broken (opened)¶
Id |
5236 |
State |
opened |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2025-04-01T00:58:33.568Z |
Updated |
2025-04-01T13:51:00.306Z |
Milestone |
6.2 |
Labels |
cpukit::dl, tool::rtems-tools |
Link |
|
Merges |
0 |
Summary¶
Run time symbol loading from an object file is broken. The change to track dependencies added support to check the origin of a symbol to track dependencies. Runtime loading of symbols requires the symbol rtems_rtl_base_sym_global_add be in the symbol table. Loading an symbol object file causes a constrictor attribute function to be run and that calls rtems_rtl_base_sym_global_add adding the base image global symbols. Currently attempting to load a symbol object file results in an unresolved external to rtems_rtl_base_sym_global_add because the symbols is inserted into the global symbol table and not added to the base image’s global symbols.
Also rtems-syms does not correctly export the needed TLS data.
Author: Chris Johns
2025-04-01T00:58:33.714Z
cloned from #5234
Author: Chris Johns
2025-04-01T00:58:33.637Z
assigned to @chris
Author: Chris Johns
2025-04-01T01:34:24.159Z
mentioned in merge request !461
Author: Kinsey Moore
2025-04-01T13:51:00.525Z
Merge Requests¶
775 - cpukit/close.c: Fix reference counting under concurrent access.¶
Id |
775 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-10-09T22:43:21.889Z |
Created |
2025-10-09T22:41:58.587Z |
Updated |
2025-10-09T22:43:21.879Z |
Milestone |
6.2 |
Labels |
cpukit |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/775 |
Commit |
Summary¶
cpukit/close.c: Fix reference counting under concurrent access.
Fixes issue with IOP being freed during close call. Updates #5311
Author: Kinsey Moore
2025-10-09T22:42:20.704Z
approved this merge request
Author: Kinsey Moore
2025-10-09T22:42:22.492Z
enabled an automatic merge when all merge checks for f4328001c71f32cd8500d67afea5f1969e3f36aa pass
Author: Joel Sherrill
2025-10-09T22:42:55.413Z
approved this merge request
Author: Kinsey Moore
2025-10-10T00:02:38.555Z
mentioned in issue #5311
762 - Backport: cpukit: Raise internal error if we cannot open stdin with fileno 0¶
Id |
762 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-10-09T22:20:12.419Z |
Created |
2025-10-03T03:52:06.475Z |
Updated |
2025-10-09T22:20:12.128Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/762 |
Commit |
Summary¶
cpukit: Raise internal error if we cannot open stdin with fileno 0
If someone manages to open a file before rtems_libio_post_driver is run, open() may allocate a file number other than 0 for stdin. This leads to a silent failure of the logic in rtems_libio_post_driver, and confusing behavior because your BSP behaves as if it doesn’t have a console.
Instead of failing silently, raise an internal error if open() succeeds but gives us an unexpected file number for stdin.
Updates #5284
Closes #5284
Author: Jeremy Lorelli
2025-10-03T04:01:33.932Z
mentioned in issue #5284
Author: Gedare Bloom
2025-10-09T22:19:57.555Z
Can you please add
Updates #5284andCloses #5284to the commit messages?
Author: Gedare Bloom
2025-10-09T22:19:57.555Z
Sorry for being unclear, but we also want these in the commit messages. Please edit the commit messages and then force push. The first commit should update, the second should close.
Author: Kinsey Moore
2025-10-09T22:19:57.555Z
Fixed
Author: Jeremy Lorelli
2025-10-06T17:51:22.932Z
changed the description
Author: Kinsey Moore
2025-10-09T22:19:37.104Z
added 6 commits
abaec266…cdcc886d - 4 commits from branch
rtems/rtos:67d44e6de - cpukit: Raise internal error if we cannot open stdin with fileno 0
074cb8f3 - libchip/ds1375: Refactor to use i2c-rtc driver
Author: Kinsey Moore
2025-10-09T22:19:57.583Z
resolved all threads
Author: Kinsey Moore
2025-10-09T22:20:02.010Z
enabled an automatic merge when all merge checks for 074cb8f33735e4383992542a17b8d8725214114c pass
Author: Kinsey Moore
2025-10-09T22:20:03.104Z
approved this merge request
Author: Chris Johns
2025-10-09T22:20:05.940Z
approved this merge request
772 - bsps/dev/spi/xqspipsu_flash_config.h: Make flash config table static¶
Id |
772 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-10-09T15:02:25.983Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-10-08T20:37:13.509Z |
Updated |
2025-10-09T15:02:25.975Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/772 |
Commit |
Summary¶
bsps/dev/spi/xqspipsu_flash_config.h: Make flash config table static
This is now used by multiple files and can cause a multiple definitions error when linking. Make the structure static to avoid this problem.
Closes #5372
Author: Kinsey Moore
2025-10-08T20:37:13.675Z
assigned to @opticron
Author: Kinsey Moore
2025-10-08T20:38:34.897Z
enabled an automatic merge when all merge checks for cdcc886ddc7c0672756e258f043b7c3fe4b4ad57 pass
Author: Chris Johns
2025-10-09T06:19:25.186Z
approved this merge request
Author: Amar Takhar
2025-10-09T14:50:09.359Z
approved this merge request
767 - spec/bsps/aarch64/xilinx-zynqmp: Add XQspiPsu flashdev backend¶
Id |
767 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2025-10-08T16:45:47.943Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-10-03T14:46:57.726Z |
Updated |
2025-10-08T16:45:47.934Z |
Milestone |
6.2 |
Labels |
device::flash |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/767 |
Commit |
Summary¶
spec/bsps/aarch64/xilinx-zynqmp: Add XQspiPsu flashdev backend
Closes #5371
Author: Kinsey Moore
2025-10-03T14:46:57.886Z
assigned to @opticron
Author: Joel Sherrill
2025-10-03T20:03:47.785Z
approved this merge request
Author: Gedare Bloom
2025-10-08T16:45:33.922Z
added 3 commits
f4d80b47…32e76ed9 - 2 commits from branch
rtems/rtos:6b1911921 - spec/bsps/aarch64/xilinx-zynqmp: Add XQspiPsu flashdev backend
Author: Gedare Bloom
2025-10-08T16:45:39.138Z
enabled an automatic merge when all merge checks for b19119212da0f3036153334713258b9342fbc6d5 pass
Author: Gedare Bloom
2025-10-08T16:45:41.429Z
approved this merge request
758 - cpukit/jffs2/gc.c: Prevent live lock for split reads¶
Id |
758 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-10-03T00:16:10.537Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-09-29T16:44:51.381Z |
Updated |
2025-10-03T00:16:10.435Z |
Milestone |
6.2 |
Labels |
filesystem::jffs2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/758 |
Commit |
Summary¶
cpukit/jffs2/gc.c: Prevent live lock for split reads
In some cases a file read is not completed in a single call into the JFFS2 layer and the inode is left in the READING state. When this happens, it’s possible for a garbage collection pass to be initiated before completion of the read. In some such cases, the garbage collection pass is executed in a tight loop that expects granular locking to allow forward progress of the read between collection passes. With RTEMS monolithic locking of the JFFS2 layer, forward progress is not possible in this situation since the monolithic lock is never released inside the loop.
The solution is to have the garbage collection pass return failure when no progress is possible due to a bad inode state. This allows the read to complete and the collection pass can be attempted at a later time.
Closes #5365
Author: Kinsey Moore
2025-09-29T16:44:51.526Z
assigned to @opticron
Author: Kinsey Moore
2025-09-29T16:45:32.028Z
changed title from
cpukit/jffs2/
rtime: Fix off-by-one error in decompression check
to
cpukit/jffs2/
gc.c: Prevent live lock for split reads
Author: Kinsey Moore
2025-09-29T16:45:32.053Z
changed the description
Author: Kinsey Moore
2025-09-29T16:45:32.086Z
changed target branch from
mainto6
Author: Kinsey Moore
2025-09-29T16:45:51.078Z
changed the description
Author: Kinsey Moore
2025-09-29T16:46:56.242Z
enabled an automatic merge when all merge checks for 3dd8fa79e905686301962a26a8c3035a60889ee6 pass
Author: Kinsey Moore
2025-09-29T17:39:15.016Z
added 1 commit
6b98c717 - cpukit/jffs2/gc.c: Prevent live lock for split reads
Author: Kinsey Moore
2025-09-29T17:39:24.970Z
enabled an automatic merge when all merge checks for 6b98c71755867df648275b78bfe21b5961f7e263 pass
Author: Chris Johns
2025-10-02T23:42:29.833Z
approved this merge request
Author: Kinsey Moore
2025-10-02T23:45:55.290Z
aborted the automatic merge because target branch was updated
Author: Amar Takhar
2025-10-03T00:14:00.669Z
approved this merge request
Author: Kinsey Moore
2025-10-03T00:15:15.737Z
added 3 commits
6b98c717…1c3cd25e - 2 commits from branch
rtems/rtos:6df40ffa9 - cpukit/jffs2/gc.c: Prevent live lock for split reads
Author: Kinsey Moore
2025-10-03T00:15:25.751Z
enabled an automatic merge when all merge checks for df40ffa9dcb21dba1e81403b2eb33ae83c98814e pass
743 - cpukit/flashdev: Add full support for NAND devices¶
Id |
743 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2025-10-03T00:13:51.425Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-09-23T19:37:24.824Z |
Updated |
2025-10-03T00:13:51.417Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/743 |
Commit |
Summary¶
This extends the flashdev API to support the additional calls required by NAND device backends. This also adds region-relative IOCTLs to prevent reimplementation of offset logic in top-end flashdev/filesystem adapters.
Closes #5350
Author: Kinsey Moore
2025-09-23T19:37:25.131Z
assigned to @opticron
Author: Kinsey Moore
2025-09-23T19:37:38.187Z
changed target branch from
mainto6
Author: Kinsey Moore
2025-09-23T19:38:17.117Z
changed title from
cpukit/
jffs2/rtime: Fix off-by-one error in decompression check
to
cpukit/
flashdev: Add full support for NAND devices
Author: Kinsey Moore
2025-09-23T19:38:17.141Z
changed the description
Author: Kinsey Moore
2025-09-23T19:38:36.930Z
changed the description
Author: Kinsey Moore
2025-09-23T19:39:10.357Z
enabled an automatic merge when all merge checks for 8b49c7ec2f03fbb4bf68e08e2819ba5903aea3e2 pass
Author: Chris Johns
2025-09-24T13:56:59.751Z
aborted the automatic merge because target branch was updated
Author: Kinsey Moore
2025-09-29T16:39:16.609Z
added 3 commits
8b49c7ec…d45d353a - 2 commits from branch
rtems/rtos:67b3808f2 - cpukit/flashdev: Add full support for NAND devices
Author: Kinsey Moore
2025-09-29T16:39:23.201Z
enabled an automatic merge when all merge checks for 7b3808f28239f147baa382ec2310e6e303388eb5 pass
Author: Chris Johns
2025-10-02T23:43:41.466Z
approved this merge request
Author: Kinsey Moore
2025-10-02T23:45:55.587Z
aborted the automatic merge because target branch was updated
Author: Amar Takhar
2025-10-03T00:12:32.784Z
approved this merge request
Author: Amar Takhar
2025-10-03T00:13:33.832Z
added 2 commits
f42ad920 - 1 commit from branch
rtems/rtos:61c3cd25e - cpukit/flashdev: Add full support for NAND devices
Author: Amar Takhar
2025-10-03T00:13:40.429Z
enabled an automatic merge when all merge checks for 1c3cd25ebd1458cb4e81e67adf0684b237501e53 pass
721 - validation: Move storage class qualifier¶
Id |
721 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-10-02T23:45:52.526Z |
Assignee(s) |
Sebastian Huber |
Created |
2025-09-12T01:30:42.791Z |
Updated |
2025-10-02T23:45:52.513Z |
Milestone |
6.2 |
Labels |
backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/721 |
Commit |
Summary¶
validation: Move storage class qualifier
Backport storage class qualifier rearrangment required by more recent C language standard revisions.
Close #5337.
Author: Sebastian Huber
2025-09-12T01:30:42.937Z
assigned to @sebhub
Author: Sebastian Huber
2025-09-12T01:31:05.006Z
enabled an automatic merge when all merge checks for 4b7498ac0e4b03bebcacb40104dea5f62280427b pass
Author: Gedare Bloom
2025-09-15T16:23:28.758Z
approved this merge request
Author: Amar Takhar
2025-09-15T17:27:29.335Z
aborted the automatic merge because target branch was updated
Author: Chris Johns
2025-10-02T23:45:27.539Z
approved this merge request
Author: Chris Johns
2025-10-02T23:45:35.399Z
added 6 commits
4b7498ac…d45d353a - 5 commits from branch
rtems/rtos:6f42ad920 - validation: Move storage class qualifier
Author: Kinsey Moore
2025-10-02T23:45:36.838Z
approved this merge request
Author: Kinsey Moore
2025-10-02T23:45:40.620Z
enabled an automatic merge when all merge checks for f42ad92071d3111bf9edc8715fad37ca387b4b0e pass
748 - libdebugger: Add SMP support for ARM¶
Id |
748 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2025-09-26T00:20:25.481Z |
Assignee(s) |
Chris Johns |
Created |
2025-09-25T04:26:20.023Z |
Updated |
2025-09-26T00:20:25.473Z |
Milestone |
6.2 |
Labels |
cpukit::debugger |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/748 |
Commit |
Add SMP support for ARM
Make the aarch64 SMP support a separate file and share it between aarch64 and arm.
Closes #5348
Author: Chris Johns
2025-09-25T04:26:20.180Z
assigned to @chris
Author: Kinsey Moore
2025-09-25T12:29:49.711Z
approved this merge request
Author: Kinsey Moore
2025-09-25T12:29:56.912Z
added 2 commits
b05ae8a6 - 1 commit from branch
rtems/rtos:6d45d353a - libdebugger: Add SMP support for ARM
Author: Gedare Bloom
2025-09-26T00:20:22.125Z
approved this merge request
741 - cpukit/flashdev: Add unregister call and private data destructor¶
Id |
741 |
State |
merged |
Merged by |
Joel Sherrill |
Merged at |
2025-09-23T00:06:39.419Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-09-23T00:01:25.972Z |
Updated |
2025-09-23T00:06:39.410Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/741 |
Commit |
Summary¶
cpukit/flashdev: Add unregister call and private data destructor
This adds an API call allowing for unregistration to include destruction of private data that is not managed by the flashdev framework. This also updates the existing consumers of flashdev to use the new private data destructor callback.
Closes #5346
Author: Kinsey Moore
2025-09-23T00:01:26.113Z
assigned to @opticron
Author: Chris Johns
2025-09-23T00:02:49.434Z
approved this merge request
Author: Joel Sherrill
2025-09-23T00:06:33.937Z
approved this merge request
720 - rtems: Add rtems_barrier_get_number_waiting()¶
Id |
720 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2025-09-19T22:06:38.366Z |
Assignee(s) |
Sebastian Huber |
Created |
2025-09-12T01:12:41.205Z |
Updated |
2025-09-19T22:06:40.572Z |
Milestone |
6.2 |
Labels |
backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/720 |
Commit |
Summary¶
rtems: Add rtems_barrier_get_number_waiting()
Backport commit 528095cd24afeef648ea0e70694aa3755a7c0edf.
Close #5336.
Author: Sebastian Huber
2025-09-12T01:12:41.353Z
assigned to @sebhub
Author: Sebastian Huber
2025-09-12T01:12:55.926Z
enabled an automatic merge when all merge checks for 14b23c1d56adff6ade331ad6dea0720c259daced pass
Author: Gedare Bloom
2025-09-15T16:23:01.551Z
approved this merge request
Author: Amar Takhar
2025-09-15T17:27:29.750Z
aborted the automatic merge because target branch was updated
Author: Chris Johns
2025-09-19T22:06:03.462Z
approved this merge request
Author: Chris Johns
2025-09-19T22:06:21.077Z
added 2 commits
d27c444b - 1 commit from branch
rtems/rtos:6a79d702b - rtems: Add rtems_barrier_get_number_waiting()
222 - posix/aio_misc.c/aio_init(): lock before accessing data¶
Id |
222 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-09-25T17:48:35.955Z |
Created |
2024-09-17T09:16:40.178Z |
Updated |
2025-09-19T00:52:57.680Z |
Milestone |
6.2 |
Labels |
api::posix |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/222 |
Commit |
Summary¶
posix/aio_misc.c/aio_init(): lock before accessing data
Added lock before accessing data to address coverity issue.
CID 1592924: Data race condition (MISSING_LOCK)
/cpukit/posix/src/aio_misc.c: 146 in rtems_aio_init()
143 rtems_chain_initialize_empty( &aio_request_queue.work_req );
144 rtems_chain_initialize_empty( &aio_request_queue.idle_req );
145
CID 1592924: Data race condition (MISSING_LOCK)
Accessing aio_request_queue.active_threads without holding lock rtems_aio_queue.mutex.
146 aio_request_queue.active_threads = 0;
147 aio_request_queue.idle_threads = 0;
148 atomic_init( &aio_request_queue.queued_requests, 0 );
Closes `#5129 <https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5129>`_.
Author: Joel Sherrill
2024-09-18T07:04:12.949Z
Please add the annotated analysis from Coverity in the description.
Author: Alessandro Nardin
2024-09-18T07:04:12.949Z
added
Author: Alessandro Nardin
2024-09-18T06:55:52.891Z
changed the description
Author: Alessandro Nardin
2024-09-18T07:02:31.632Z
added 10 commits
7a464d0a…d304a817 - 9 commits from branch
rtems/rtos:main344caffe - posix/aio_misc.c/aio_init(): lock before accessing data
Author: Alessandro Nardin
2024-09-18T07:04:12.966Z
resolved all threads
Author: Alessandro Nardin
2024-09-24T15:55:22.469Z
added 12 commits
344caffe…6003ea9d - 11 commits from branch
rtems/rtos:main2c802636 - posix/aio_misc.c/aio_init(): lock before accessing data
Author: Joel Sherrill
2024-09-25T15:03:59.061Z
approved this merge request
Author: Amar Takhar
2024-09-25T17:47:37.733Z
approved this merge request
Author: Amar Takhar
2024-09-25T17:47:50.240Z
added 6 commits
2c802636…9eb23924 - 5 commits from branch
rtems/rtos:main280846e5 - posix/aio_misc.c/aio_init(): lock before accessing data
Author: Amar Takhar
2024-09-25T17:48:20.829Z
added 2 commits
de196e05 - 1 commit from branch
rtems/rtos:main617808b9 - posix/aio_misc.c/aio_init(): lock before accessing data
722 - rtems: Backport Doxygen changes¶
Id |
722 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2025-09-15T17:27:26.686Z |
Assignee(s) |
Sebastian Huber |
Created |
2025-09-12T01:32:06.980Z |
Updated |
2025-09-15T17:27:26.674Z |
Milestone |
6.2 |
Labels |
backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/722 |
Commit |
Summary¶
rtems: Backport Doxygen changes
The conversion to Markdown for the documentation sources resulted in changes of Doxygen comments of generated sources. Backport these changes.
Close #5338.
Author: Sebastian Huber
2025-09-12T01:32:07.140Z
assigned to @sebhub
Author: Sebastian Huber
2025-09-12T01:32:16.377Z
enabled an automatic merge when all merge checks for c0d4a7022a49a7f739366524f3c46479bd968fb9 pass
Author: Sebastian Huber
2025-09-12T02:43:27.770Z
added 1 commit
d27c444b - rtems: Backport Doxygen changes
Author: Gedare Bloom
2025-09-15T16:26:57.611Z
approved this merge request
Author: Amar Takhar
2025-09-15T17:27:23.119Z
enabled an automatic merge when all merge checks for d27c444b8dd5caa8416fd1b0d040d4009641169e pass
Author: Amar Takhar
2025-09-15T17:27:23.787Z
approved this merge request
637 - cpukit/libdebugger/server: Use generic TLS accessor¶
Id |
637 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2025-07-31T01:11:16.233Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-07-27T22:46:42.779Z |
Updated |
2025-07-31T01:11:16.219Z |
Milestone |
6.2 |
Labels |
cpukit::debugger |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/637 |
Commit |
Summary¶
cpukit/libdebugger/server: Use generic TLS accessor
This updates the libdebugger server to use a generic TLS area access mechanism so that it works across all supported architectures.
Closes #5313
Author: Kinsey Moore
2025-07-27T22:46:42.910Z
assigned to @opticron
Author: Kinsey Moore
2025-07-29T12:33:37.222Z
added 1 commit
7fe22dd7 - cpukit/libdebugger/server: Use generic TLS accessor
Author: Joel Sherrill
2025-07-29T12:45:44.428Z
approved this merge request
Author: Chris Johns
2025-07-31T01:10:51.396Z
approved this merge request
Author: Chris Johns
2025-07-31T01:11:00.111Z
added 2 commits
0cf6de01 - 1 commit from branch
rtems/rtos:6a79813c9 - cpukit/libdebugger/server: Use generic TLS accessor
Author: Chris Johns
2025-07-31T01:11:04.184Z
enabled an automatic merge when all merge checks for a79813c96e76bc0e7c71ffce675374b520129d24 pass
635 - cpukit/libio: Support close with IOP references held¶
Id |
635 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-07-28T15:48:17.842Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-07-27T02:26:15.605Z |
Updated |
2025-07-28T15:48:17.826Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/635 |
Commit |
Summary¶
cpukit/libio: Support close with IOP references held
Provide an option for a file system to support close wtih
references held. This can happen in more complex file systems and file descriptor handling with more complete reference handling implementations where an fd can hold other fds and close can be call on any fd and succeed.
Fix open IOP leaks in the error paths.
Provide better definition of the IOP flags to help clarify
the code.
Fixes #5201
Closes #5311
Author: Kinsey Moore
2025-07-27T02:26:15.925Z
assigned to @opticron
Author: Kinsey Moore
2025-07-28T14:40:32.587Z
changed the description
Author: Joel Sherrill
2025-07-28T15:33:45.080Z
approved this merge request
Author: Kinsey Moore
2025-07-28T15:45:22.096Z
enabled an automatic merge when all merge checks for 0cf6de01df734c11212e63134551ee344a10ecec pass
Author: Amar Takhar
2025-07-28T15:48:05.408Z
This is a really nice change
Author: Amar Takhar
2025-07-28T15:48:08.501Z
approved this merge request
518 - cpukit/libdebugger: Add support for TLS variables¶
Id |
518 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2025-07-25T01:33:07.623Z |
Assignee(s) |
Kinsey Moore |
Reviewer(s) |
Chris Johns |
Created |
2025-06-17T19:19:24.345Z |
Updated |
2025-07-25T01:33:10.653Z |
Milestone |
6.2 |
Labels |
backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/518 |
Commit |
Summary¶
cpukit/libdebugger: Add support for TLS variables
This adds support for the “vGetTLSAddr” GDB query which retrieves the address of a TLS variable by offset from the beginning of the TLS memory space for the given thread. This offset does not include the size of the thread control block which is at the beginning of every TLS area as used by RTEMS. Notably, the returned address is big-endian rather than the little-endian typical with other responses.
This functionality does not include retrieval of addresses for TLS variables hosted in loadable modules, only TLS variables in the host binary.
Author: Kinsey Moore
2025-06-17T19:19:24.986Z
requested review from @chris
Author: Kinsey Moore
2025-06-17T19:19:25.012Z
assigned to @opticron
Author: Kinsey Moore
2025-06-18T18:59:43.036Z
changed the description
Author: Kinsey Moore
2025-06-18T19:01:15.967Z
mentioned in issue #4883
Author: Kinsey Moore
2025-06-25T11:42:20.014Z
added 1 commit
14329bc2 - cpukit/libdebugger: Add support for TLS variables
Author: Gedare Bloom
2025-06-25T16:35:42.812Z
approved this merge request
Author: Kinsey Moore
2025-06-26T00:48:21.060Z
added 1 commit
4f819d02 - cpukit/libdebugger: Add support for TLS variables
Author: Kinsey Moore
2025-07-25T00:18:50.538Z
added 1 commit
c276be7e - cpukit/libdebugger: Add support for TLS variables
Author: Kinsey Moore
2025-07-25T00:19:02.905Z
reset approvals from @gedare by pushing to the branch
Author: Chris Johns
2025-07-25T00:19:58.757Z
approved this merge request
Author: Chris Johns
2025-07-25T00:20:19.659Z
added 5 commits
c276be7e…e7fa90ab - 4 commits from branch
rtems/rtos:67061ab5b - cpukit/libdebugger: Add support for TLS variables
Author: Chris Johns
2025-07-25T00:20:53.415Z
enabled an automatic merge when all merge checks for 7061ab5bd67c1b30283910a82c28d00baf2c7dd4 pass
Author: Kinsey Moore
2025-07-25T01:11:54.548Z
aborted the automatic merge because target branch was updated
Author: Kinsey Moore
2025-07-25T01:31:48.988Z
added 3 commits
7061ab5b…b1dbd9ee - 2 commits from branch
rtems/rtos:61240e8f8 - cpukit/libdebugger: Add support for TLS variables
Author: Joel Sherrill
2025-07-25T01:32:56.791Z
approved this merge request
Author: Amar Takhar
2025-07-25T01:32:58.337Z
approved this merge request
626 - bsps/include/dev/spi: Add missing extern and guard¶
Id |
626 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-07-25T01:11:51.663Z |
Assignee(s) |
Kinsey Moore |
Created |
2025-07-23T20:19:01.389Z |
Updated |
2025-07-25T01:11:51.652Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/626 |
Commit |
Summary¶
bsps/include/dev/spi: Add missing extern and guard
This adds missing extern “C” declarations and a missing header guard.
Updates #5309
Author: Kinsey Moore
2025-07-23T20:19:01.576Z
assigned to @opticron
Author: Kinsey Moore
2025-07-24T22:33:22.448Z
enabled an automatic merge when all merge checks for b1dbd9eeae9ad1c1dbc1b9593039e41e1101a4ce pass
Author: Joel Sherrill
2025-07-24T22:33:26.979Z
approved this merge request
Author: Chris Johns
2025-07-25T01:11:47.559Z
approved this merge request
548 - cpu/riscv: Add Smdbltrp extension compatibility to 6 branch¶
Id |
548 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-07-03T13:20:06.894Z |
Created |
2025-07-03T08:10:40.579Z |
Updated |
2025-07-03T13:20:06.437Z |
Milestone |
6.2 |
Labels |
arch:riscv |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/548 |
Commit |
Summary¶
cpu/riscv: Add Smdbltrp extension compatibility
If the Double Trap Extension is implemented, the MDT bit of the mstatus (or mstatush in RV32) register will be set when a trap is to be taken.
The MIE (Machine Interrupt Enable) bit can only be set to 1 if the MDT bit is zero.
Thus, we need to clear MDT first if we want to enable interrupts when dispatching a thread.
MDT is also cleared in register a1 before restoring the interrupt frame as writing 1 to MDT will cause MIE to be set to 0. In RV64 this happens regardless of the value written to MIE in the same write.
In RV32, MDT is in the mstatush so we do not need to clear during restore as this register is not restored.
With this change all 60 SMP tests pass (compared to 20/60 before the fix). The tests have been run on hardware using two RV64 CPUs that implement the double trap extension.
Close #5288
(cherry picked from commit 19f12d2dca02da3072c0c31e2da281f6a447699e)
Author: Kinsey Moore
2025-07-03T13:11:23.395Z
approved this merge request
Author: Kinsey Moore
2025-07-03T13:11:30.083Z
enabled an automatic merge when all merge checks for e7fa90ab0ccd0566dd0b136c62aa729515c3b011 pass
Author: Joel Sherrill
2025-07-03T13:20:01.821Z
approved this merge request
537 - bsps/noelv: Backport polled mode console to 6¶
Id |
537 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2025-06-28T15:35:41.336Z |
Created |
2025-06-26T07:02:00.422Z |
Updated |
2025-06-28T15:36:37.701Z |
Milestone |
6.2 |
Labels |
arch:riscv, backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/537 |
Commit |
Summary¶
bsps/noelv: Fix using console in polled mode
Before, the console driver needed BSP_CONSOLE_USE_INTERRUPTS to be defined or it would not build. The intent was to use polled mode if the macro was equal to zero.
This change makes it so interrupt mode is used if the macro is defined and polled mode is used if the macro is not defined.
(cherry picked from commit 5e0a68d3ab6bedb16e465267310c59c25803b783)
Close #5283
Author: Joel Sherrill
2025-06-27T13:32:10.089Z
This needs an issue for the backport and the issue needs to be associated with the 6.2 release epic.
If that needs clarification, this is documented somewhere. Ask on Discord and hopefully someone can give you a pointer.
If you need help, ask on Discord.
Author: Matteo Concas
2025-06-27T13:32:10.089Z
I created issue #5283, but I can’t seem to add it to the 6.2 release epic or add labels to it. I guess only maintainers have these rights.
Author: Matteo Concas
2025-06-27T07:42:39.176Z
added 1 commit
dd490c5c - bsps/noelv: Fix using console in polled mode
Author: Matteo Concas
2025-06-27T07:43:20.752Z
changed the description
Author: Kinsey Moore
2025-06-27T13:32:10.120Z
resolved all threads
Author: Kinsey Moore
2025-06-27T13:32:14.452Z
approved this merge request
Author: Gedare Bloom
2025-06-28T14:53:54.575Z
approved this merge request
532 - bsps/sparc/leon3: Backport GPTIMER timer index logic fix to 6¶
Id |
532 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-06-26T02:36:21.764Z |
Assignee(s) |
Matteo Concas |
Created |
2025-06-23T07:28:42.604Z |
Updated |
2025-06-26T02:36:21.748Z |
Milestone |
6.2 |
Labels |
backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/532 |
Commit |
Summary¶
bsps/sparc/leon3: Fix GPTIMER timer index logic
The old logic would lead to an error when multiprocessing was enabled and LEON3_GPTIMER_BASE was defined due to leon3_timer_core_index being undefined.
The new logic fixes this and keeps the same intent:
If multiprocessing is not enabled, the timer index is 0
If multiprocessing is enabled and
LEON3_GPTIMER_BASEis defined, the timer index is twice the CPU boot indexIf multiprocessing is enabled and
LEON3_GPTIMER_BASEis not defined, we fallback to the old logic using the GPTIMER core index.
Author: Matteo Concas
2025-06-23T07:29:20.225Z
changed title from bsps/sparc/leon3: {-Fix-} GPTIMER timer index logic to bsps/sparc/leon3: {+Backport+} GPTIMER timer index logic{+ fix to 6+}
Author: Matteo Concas
2025-06-23T07:30:22.977Z
mentioned in merge request !514
Author: Gedare Bloom
2025-06-25T16:24:56.538Z
@matteo.concas please add closes #5281 to the commit message someone will have to manually close it also, after the backport
Author: Matteo Concas
2025-06-25T16:24:56.538Z
I have added “Close #5281” to the commit message.
Author: Gedare Bloom
2025-06-24T20:31:45.106Z
assigned to @matteo.concas
Author: Matteo Concas
2025-06-25T06:23:00.842Z
added 1 commit
d010f6ae - bsps/sparc/leon3: Fix GPTIMER timer index logic
Author: Gedare Bloom
2025-06-25T16:24:56.595Z
resolved all threads
Author: Gedare Bloom
2025-06-25T16:26:16.722Z
approved this merge request
Author: Joel Sherrill
2025-06-25T22:20:48.635Z
approved this merge request
Author: Kinsey Moore
2025-06-26T02:36:07.135Z
enabled an automatic merge when the pipeline for d010f6ae8bc4e2ccfcc162b256e18ed61b71820d succeeds
524 - cpukit/libdebugger: Prevent hang on memory access¶
Id |
524 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-06-19T22:52:50.613Z |
Assignee(s) |
Kinsey Moore |
Reviewer(s) |
Chris Johns |
Created |
2025-06-18T18:55:15.610Z |
Updated |
2025-06-19T22:52:53.452Z |
Milestone |
6.2 |
Labels |
arch:aarch64, cpukit::debugger |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/524 |
Commit |
Summary¶
cpukit/libdebugger: Prevent hang on memory access
When memory is accessed by the remote debugging client, the access is sandboxed with setjmp/longjmp and appropriate exception handlers to prevent the attempted access from causing a failure of the debugger or otherwise altering execution. The existing implementation works as expected when the context executing the memory access and the exception context resulting from a failed access do not share a stack.
In the case of AArch64, a failed access when the debugger is already in exception context causes a re-entry into exception context where the machine state is pushed onto the same stack that was in use where the exception occurred. When setjmp is called inside a stack frame and the exception occurs outside that stack frame, the stack frame is unwound before the exception occurs and the exception entry overwrites the area previously occupied by the stack frame housing the setjmp and corrupting the link register that is stored there. After restoration of state using longjmp(), this corrupted link register information is loaded from the stack frame and undesired behavior occurs.
In the instance of this bug that was encountered, the corrupted link register contained an unaligned pointer which caused an unending cascade of prefetch abort exceptions presenting as a hard hang.
Closes #5273
Author: Kinsey Moore
2025-06-18T18:55:16.294Z
requested review from @chris
Author: Kinsey Moore
2025-06-18T18:55:16.326Z
assigned to @opticron
Author: Chris Johns
2025-06-19T22:36:09.770Z
approved this merge request
Author: Joel Sherrill
2025-06-19T22:48:37.839Z
approved this merge request
354 - score: Fix RTEMS_DEBUG build¶
Id |
354 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-01-08T13:31:58.965Z |
Assignee(s) |
Sebastian Huber |
Created |
2025-01-08T05:42:37.595Z |
Updated |
2025-05-09T00:10:25.214Z |
Milestone |
6.2 |
Labels |
rtems::score |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/354 |
Commit |
Summary¶
score: Fix RTEMS_DEBUG build
Close #5159.
Author: Sebastian Huber
2025-01-08T05:42:37.873Z
assigned to @sebhub
Author: Chris Johns
2025-01-08T05:43:50.581Z
approved this merge request
Author: Kinsey Moore
2025-01-08T13:31:38.056Z
approved this merge request
416 - machine/timecounters: Add _Timecounter_Getboottime, _Timecounter_Getboottimebin decls¶
Id |
416 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-05-08T22:38:11.262Z |
Assignee(s) |
Chris Johns |
Created |
2025-02-11T22:27:17.904Z |
Updated |
2025-05-08T22:38:15.309Z |
Milestone |
6.2 |
Labels |
rtems::kernel |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/416 |
Commit |
Summary¶
Add _Timecounter_Getboottime, _Timecounter_Getboottimebin decls
Closes #5212
Author: Chris Johns
2025-02-11T22:27:18.157Z
assigned to @chris
Author: Kinsey Moore
2025-05-08T22:36:28.879Z
This fails the commit message line length checks.
Author: Chris Johns
2025-05-08T22:36:01.285Z
added 1 commit
993962be - machine/timecounters: Add missing _Timecounter_ decls
Author: Joel Sherrill
2025-05-08T22:36:28.914Z
resolved all threads
Author: Joel Sherrill
2025-05-08T22:36:37.023Z
approved this merge request
Author: Kinsey Moore
2025-05-08T22:36:54.367Z
approved this merge request
Author: Kinsey Moore
2025-05-08T22:37:04.928Z
added 4 commits
993962be…f769b20c - 3 commits from branch
rtems/rtos:6328e83ec - machine/timecounters: Add missing _Timecounter_ decls
Author: Chris Johns
2025-05-08T22:37:32.553Z
added 1 commit
6335d7e4 - machine/timecounters: Add missing _Timecounter_ decls
461 - cpukit/libdl: Fix loading symbols from an object file at runtime¶
Id |
461 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2025-04-04T00:06:34.500Z |
Assignee(s) |
Chris Johns |
Created |
2025-04-01T01:34:14.150Z |
Updated |
2025-04-04T00:06:36.822Z |
Milestone |
6.2 |
Labels |
cpukit::dl, tool::rtems-tools |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/461 |
Commit |
Summary¶
cpukit/libdl: Fix loading symbols from an object file at runtime
Assume a relocation record with a symbol name with a length of 0 is resolved. ARM seems to create a symbol with no name for R_ARM_V4BX relocation records.
Move the addition of the rtems_rtl_base_sym_global_add symbol to the global symbol table to the weak rtems_rtl_base_global_syms_init call. If symbols are embedded the support for runtime loading symbols is over loaded. This change is required so the base object has a valid global symbol table attached to track dependencies.
Fixes #5236
Author: Chris Johns
2025-04-01T01:34:14.397Z
assigned to @chris
Author: Kinsey Moore
2025-04-03T23:01:59.004Z
approved this merge request
Author: Amar Takhar
2025-04-04T00:06:28.081Z
approved this merge request
459 - Backport “spec: Install missing header files for GRLIB and SPARC” to 6 branch¶
Id |
459 |
State |
merged |
Merged by |
Joel Sherrill |
Merged at |
2025-03-26T16:50:31.035Z |
Created |
2025-03-26T16:48:45.767Z |
Updated |
2025-03-26T16:50:33.271Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/459 |
Commit |
Backport commit spec: Install missing header files for GRLIB and SPARC on main to 6 branch.
Closes issue #5232
Author: Kinsey Moore
2025-03-26T16:49:31.177Z
approved this merge request
Author: Joel Sherrill
2025-03-26T16:50:20.843Z
approved this merge request
418 - gitlab: Add link to CI¶
Id |
418 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2025-02-13T03:24:20.100Z |
Assignee(s) |
Amar Takhar |
Created |
2025-02-12T13:40:24.076Z |
Updated |
2025-03-13T22:44:56.007Z |
Milestone |
6.2 |
Labels |
ci |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/418 |
Commit |
Summary¶
gitlab: Add link to CI
This runs only the commit message and merge request checker.
Required so we can have ‘all pipelines must pass’ enabled due to a bug in Gitlab
Author: Amar Takhar
2025-02-12T13:40:24.364Z
assigned to @amar
Author: Amar Takhar
2025-02-12T14:04:32.289Z
Once this is merged I can enable enforcing pipelines must pass.
Author: Kinsey Moore
2025-02-12T14:46:29.753Z
approved this merge request
Author: Chris Johns
2025-02-13T03:18:41.727Z
changed the description
Author: Chris Johns
2025-02-13T03:24:10.796Z
Commit message as “ue” instead of “due”
Author: Amar Takhar
2025-02-13T03:22:35.416Z
added 1 commit
b4149b22 - gitlab: Add link to CI
Author: Chris Johns
2025-02-13T03:24:10.814Z
resolved all threads
Author: Chris Johns
2025-02-13T03:24:15.303Z
approved this merge request
413 - Revert “build: Provide LDFLAGS for pkg-config”¶
Id |
413 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-02-11T13:51:35.086Z |
Assignee(s) |
Chris Johns |
Created |
2025-02-11T05:43:37.231Z |
Updated |
2025-02-11T13:51:37.304Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/413 |
Commit |
Summary¶
Revert “build: Provide LDFLAGS for pkg-config”
This reverts commit e36ba91110724b5cc8a9e07659d98d0bcb96e4d4
Updates #5165
See https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/issues/38
Author: Chris Johns
2025-02-11T05:50:43.847Z
changed the description
Author: Chris Johns
2025-02-11T05:50:43.893Z
assigned to @chris
Author: Chris Johns
2025-02-11T05:52:05.406Z
changed the description
Author: Amar Takhar
2025-02-11T05:55:01.814Z
approved this merge request
Author: Kinsey Moore
2025-02-11T13:51:20.391Z
approved this merge request
345 - bsp/qoriq: Ignore spurious interrupts¶
Id |
345 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-02-07T23:20:29.334Z |
Assignee(s) |
Sebastian Huber |
Created |
2024-12-06T10:22:28.402Z |
Updated |
2025-02-07T23:20:33.215Z |
Milestone |
6.2 |
Labels |
arch:powerpc, backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/345 |
Commit |
Summary¶
bsp/qoriq: Ignore spurious interrupts
For example, with edge triggered external interrupts we may see spurious interrupts. Ignore them instead of issuing a fatal error.
Use eieio to synchronize access to the IACK and EOI registers.
Use a loop to immediately services the next pending interrupt without having to go through the exception epiloge and prologue.
Close #5173.
Author: Sebastian Huber
2024-12-06T10:22:28.560Z
assigned to @sebhub
Author: Gedare Bloom
2024-12-06T16:10:09.706Z
approved this merge request
Author: Kinsey Moore
2024-12-06T16:19:36.472Z
added 2 commits
a357119b - 1 commit from branch
rtems/rtos:681ed4b2d - bsp/qoriq: Ignore spurious interrupts
Author: Kinsey Moore
2025-02-07T22:57:58.139Z
This needs the same fix as the other MR.
Author: Gedare Bloom
2025-02-07T23:17:29.509Z
changed this line in version 6 of the diff
Author: Kinsey Moore
2024-12-06T16:20:26.526Z
requested changes
Author: Gedare Bloom
2025-02-03T18:59:36.917Z
unapproved this merge request
Author: Kinsey Moore
2025-02-06T23:49:46.426Z
added 9 commits
81ed4b2d…9641e1e9 - 8 commits from branch
rtems/rtos:670cb4a1c - bsp/qoriq: Ignore spurious interrupts
Author: Kinsey Moore
2025-02-07T22:56:47.362Z
added 3 commits
70cb4a1c…e36ba911 - 2 commits from branch
rtems/rtos:6f1e807b2 - bsp/qoriq: Ignore spurious interrupts
Author: Kinsey Moore
2025-02-07T22:57:45.129Z
added 1 commit
18c59283 - bsp/qoriq: Ignore spurious interrupts
Author: Kinsey Moore
2025-02-07T22:57:58.154Z
resolved all threads
Author: Kinsey Moore
2025-02-07T22:58:41.186Z
approved this merge request
Author: Gedare Bloom
2025-02-07T23:17:29.818Z
added 1 commit
be39d7cc - bsp/qoriq: Ignore spurious interrupts
Author: Gedare Bloom
2025-02-07T23:17:45.099Z
reset approvals from @opticron by pushing to the branch
Author: Gedare Bloom
2025-02-07T23:18:36.678Z
added 1 commit
e421c922 - bsp/qoriq: Ignore spurious interrupts
Author: Gedare Bloom
2025-02-07T23:19:38.690Z
approved this merge request
Author: Kinsey Moore
2025-02-07T23:20:19.442Z
approved this merge request
335 - build: Provide LDFLAGS for pkg-config (6.1)¶
Id |
335 |
State |
merged |
Merged by |
Joel Sherrill |
Merged at |
2025-02-07T18:29:24.490Z |
Assignee(s) |
Sebastian Huber |
Created |
2024-11-28T14:26:56.054Z |
Updated |
2025-02-07T18:29:26.896Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/335 |
Commit |
Summary¶
build: Provide LDFLAGS for pkg-config
Some pkg-config variants perform transformations on the –libs options. This may lead to completely broken linker options. Provide the LDFLAGS as a variable. Remove “Ldflags:” since this is an unsupported field.
Update #5165.
Author: Sebastian Huber
2024-11-28T14:26:56.172Z
assigned to @sebhub
Author: Sebastian Huber
2024-11-28T14:28:45.629Z
changed title from build: Provide LDFLAGS for pkg-config to build: Provide LDFLAGS for pkg-config{+ (6.1)+}
Author: Chris Johns
2024-11-28T18:55:33.768Z
approved this merge request
Author: Chris Johns
2024-11-28T18:56:10.244Z
unapproved this merge request
Author: Kinsey Moore
2025-01-17T01:21:22.921Z
approved this merge request
Author: Kinsey Moore
2025-01-17T01:21:50.110Z
added 4 commits
0de8e928…34ba74f4 - 3 commits from branch
rtems/rtos:6b337ac32 - build: Provide LDFLAGS for pkg-config
Author: Kinsey Moore
2025-01-17T03:12:28.532Z
unapproved this merge request
Author: Kinsey Moore
2025-01-17T03:12:38.050Z
approved this merge request
Author: Sebastian Huber
2025-01-20T23:32:47.963Z
added 2 commits
f7de6d54 - 1 commit from branch
rtems/rtos:6c6242efc - build: Provide LDFLAGS for pkg-config
Author: Sebastian Huber
2025-01-20T23:33:00.694Z
reset approvals from @opticron by pushing to the branch
Author: Kinsey Moore
2025-01-24T01:06:37.734Z
added 5 commits
c6242efc…f1c201c5 - 4 commits from branch
rtems/rtos:66c845593 - build: Provide LDFLAGS for pkg-config
Author: Kinsey Moore
2025-01-24T01:06:45.116Z
approved this merge request
Author: Kinsey Moore
2025-02-06T23:48:13.858Z
added 2 commits
9641e1e9 - 1 commit from branch
rtems/rtos:67654de7c - build: Provide LDFLAGS for pkg-config
Author: Kinsey Moore
2025-02-07T18:28:08.013Z
added 2 commits
a0e4be53 - 1 commit from branch
rtems/rtos:6e36ba911 - build: Provide LDFLAGS for pkg-config
Author: Joel Sherrill
2025-02-07T18:29:12.972Z
approved this merge request
404 - grlib/occan: Fix baud rate calculation¶
Id |
404 |
State |
merged |
Merged by |
Joel Sherrill |
Merged at |
2025-02-07T18:03:48.749Z |
Assignee(s) |
Gedare Bloom |
Created |
2025-02-07T15:51:47.539Z |
Updated |
2025-02-07T18:03:50.977Z |
Milestone |
6.2 |
Labels |
backport, grlib |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/404 |
Commit |
Summary¶
grlib/occan: Fix baud rate calculation
Fixes #5205
Closes #5205
Author: Gedare Bloom
2025-02-07T15:51:47.744Z
assigned to @gedare
Author: Kinsey Moore
2025-02-07T18:01:17.302Z
approved this merge request
Author: Joel Sherrill
2025-02-07T18:03:40.618Z
approved this merge request
381 - cpukit/termios: Fix ordering of baud rate table¶
Id |
381 |
State |
merged |
Merged by |
Sebastian Huber |
Merged at |
2025-02-06T03:35:42.316Z |
Assignee(s) |
Gedare Bloom |
Created |
2025-02-03T19:05:27.637Z |
Updated |
2025-02-06T03:35:45.233Z |
Milestone |
6.2 |
Labels |
cpukit |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/381 |
Commit |
Summary¶
cpukit/termios: Fix ordering of baud rate table
rtems_termios_set_best_baud expects a sorted baud rate table.
Fixes #5202
Closes #5202
Author: Gedare Bloom
2025-02-03T19:05:27.858Z
assigned to @gedare
Author: Kinsey Moore
2025-02-03T19:10:11.840Z
approved this merge request
Author: Sebastian Huber
2025-02-06T03:35:22.184Z
approved this merge request
365 - Backport 6.2: bsps/shared: NS16550 driver updates the line control register during operation¶
Id |
365 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2025-01-24T00:09:30.843Z |
Created |
2025-01-23T14:26:20.807Z |
Updated |
2025-01-24T00:09:32.535Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/365 |
Commit |
Summary¶
bsps/shared: NS16550 driver updates the line control register during operation
Fixes: #5187
Author: Kinsey Moore
2025-01-23T14:27:47.909Z
approved this merge request
Author: Jan Sommer
2025-01-23T14:33:23.574Z
changed title from bsps/shared: NS16550 driver updates the line control register during operation to {+Backport 6.2: +}bsps/shared: NS16550 driver updates the line control register during operation
Author: Chris Johns
2025-01-24T00:08:35.222Z
added 3 commits
545f8f0f…603c168a - 2 commits from branch
rtems/rtos:6f1c201c5 - bsps/shared: NS16550 driver updates the line control register during operation
Author: Chris Johns
2025-01-24T00:09:26.181Z
approved this merge request
361 - cpukit/libmisc: fix flag in capture.c¶
Id |
361 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2025-01-23T23:49:48.189Z |
Assignee(s) |
Gedare Bloom |
Created |
2025-01-21T00:00:22.382Z |
Updated |
2025-01-23T23:49:50.563Z |
Milestone |
6.2 |
Labels |
cpukit::misc |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/361 |
Commit |
Summary¶
cpukit/libmisc: fix flag in capture.c
The RTEMS_CAPTURE_OVERFLOW is an overflow flag for each CPU, and its value is the same as RTEMS_CAPTURE_INIT. Executing rtems_capture_flush will set the RTEMS_CAPTURE_INIT flag to 0 in the global flags.
Fixes #5184.
Closes #5184
Author: Gedare Bloom
2025-01-21T00:00:24.030Z
assigned to @gedare
Author: Chris Johns
2025-01-23T23:45:11.771Z
added 3 commits
151074b3…84c2cf3d - 2 commits from branch
rtems/rtos:6603c168a - cpukit/libmisc: fix flag in capture.c
Author: Chris Johns
2025-01-23T23:45:36.805Z
approved this merge request
Author: Kinsey Moore
2025-01-23T23:49:43.026Z
approved this merge request
367 - cpukit/libdl/arm: Fix trampoline alignment¶
Id |
367 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2025-01-23T23:37:30.167Z |
Created |
2025-01-23T22:05:59.402Z |
Updated |
2025-01-23T23:37:32.473Z |
Milestone |
6.2 |
Labels |
arch:arm, cpukit::dl |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/367 |
Commit |
Summary¶
cpukit/libdl/arm: Fix trampoline alignment
This commit aligns trampolines for THUMB and ARM instructions (CALL/JUMP24 and THM_JUMP24/THM_PC22).
According to the ARM technical reference in section “Register-relative and PC-relative expressions”:
In Thumb code: * For B, BL, CBNZ, and CBZ instructions, the value of the PC is the address of the current instruction plus 4 bytes. * For all other instructions that use labels, the value of the PC is the address of the current instruction plus 4 bytes, with bit[1] of the result cleared to 0 to make it word-aligned.
Closes #5189
Author: Kinsey Moore
2025-01-23T22:49:30.326Z
I have created #5189 for this MR to reference with appropriate epic and milestone. Could you please reference it with “Closes #5189” on a new line at the end of the commit message?
Author: Ranulfo Raphael
2025-01-23T22:49:30.326Z
Done. Thanks.
Author: Ranulfo Raphael
2025-01-23T22:41:09.917Z
added 1 commit
84c2cf3d - cpukit/libdl/arm: Fix trampoline alignment
Author: Ranulfo Raphael
2025-01-23T22:47:35.033Z
changed the description
Author: Ranulfo Raphael
2025-01-23T22:49:30.342Z
resolved all threads
Author: Kinsey Moore
2025-01-23T23:03:23.524Z
approved this merge request
Author: Chris Johns
2025-01-23T23:37:24.885Z
approved this merge request
348 - libmisc/stackchk: Add stack smashing protection (closed)¶
Id |
348 |
State |
closed |
Assignee(s) |
Joel Sherrill |
Reviewer(s) |
Gedare Bloom |
Closed by |
Gedare Bloom |
Created |
2024-12-19T06:34:14.290Z |
Closed |
2025-10-03T19:14:16.933Z |
Updated |
2025-10-03T19:14:16.918Z |
Milestone |
6.2 |
Labels |
backport |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/348 |
Commit |
Summary¶
libmisc/stackchk: Add stack smashing protection
This is a backport for merge request 277! to 6 branch.
Note¶
Closes #5180
Author: Mohamed Hassan
2024-12-19T06:41:59.787Z
mentioned in issue #5180
Author: Gedare Bloom
2024-12-19T16:33:40.221Z
assigned to @joel
Author: Gedare Bloom
2024-12-19T16:35:21.370Z
requested review from @gedare
Author: Gedare Bloom
2025-10-03T19:12:52.826Z
Needs the same fixes as !277
Author: Mohamed Hassan
2025-10-03T19:12:52.826Z
Done.
Author: Gedare Bloom
2025-02-07T18:30:50.708Z
Please add Closes #5180 to the commit message and the MR description (although I don’t think Gitlab will pick it up correctly yet for a release branch)
Author: Mohamed Hassan
2025-02-07T18:30:50.708Z
Understood & done.
Author: Mohamed Hassan
2024-12-20T14:49:15.952Z
added 1 commit
066b355c - libmisc/stackchk: Add stack smashing protection
Author: Mohamed Hassan
2024-12-20T15:02:21.630Z
added 1 commit
30d7008a - libmisc/stackchk: Add stack smashing protection
Author: Mohamed Hassan
2024-12-20T15:03:35.573Z
changed the description
Author: Mohamed Hassan
2024-12-23T20:25:19.593Z
added 2 commits
d61a739e - 1 commit from branch
rtems/rtos:6b50f74c9 - libmisc/stackchk: Add stack smashing protection
Author: Kinsey Moore
2025-02-06T23:51:32.758Z
added 8 commits
b50f74c9…9641e1e9 - 7 commits from branch
rtems/rtos:69c5f1ae7 - libmisc/stackchk: Add stack smashing protection
Author: Amar Takhar
2025-07-03T01:14:00.936Z
added 13 commits
9c5f1ae7…dd490c5c - 12 commits from branch
rtems/rtos:66a6881cb - libmisc/stackchk: Add stack smashing protection
Author: Gedare Bloom
2025-10-03T19:12:48.618Z
Where does this print statement come from?
Author: Gedare Bloom
2025-10-03T19:14:16.474Z
As indicated in #5180 we won’t merge this to the released branch.
424 - build: Provide LDFLAGS for pkg-config (opened)¶
Id |
424 |
State |
opened |
Assignee(s) |
Sebastian Huber |
Reviewer(s) |
Chris Johns |
Created |
2025-02-15T05:42:39.462Z |
Updated |
2025-10-03T01:12:30.059Z |
Milestone |
6.2 |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/424 |
Commit |
Summary¶
Some pkg-config variants perform transformations on the –libs options. This may lead to completely broken linker options:
https://github.com/pkgconf/pkgconf/issues/371
Provide the LDFLAGS as a variable. Do not add the ABI_FLAGS to LDFLAGS since they are already contained in the CFLAGS. The linker command line should include the compiler flags so that link-time optimization works properly.
Update #5165.
Author: Sebastian Huber
2025-02-15T05:42:39.627Z
assigned to @sebhub
Author: Sebastian Huber
2025-02-15T05:44:12.602Z
changed title from {-cpukit/jffs2/rtime: Fix off-by-one error in decompression check-} to {+build: Provide LDFLAGS for pkg-config+}
Author: Sebastian Huber
2025-02-15T05:44:12.631Z
changed the description
Author: Sebastian Huber
2025-02-15T05:44:12.670Z
changed target branch from
mainto6
Author: Sebastian Huber
2025-02-15T05:48:57.400Z
I created the MR with the wrong target branch. Now the pipeline is confused.
Author: Amar Takhar
2025-02-15T05:59:03.534Z
Yes, we actually enacted a new policy and adding to gitlab that branches targeted towards branches need to start with
5-*or6-*gitlab will then automatically set the branch.This just happened no doc updating the old way is still fine but this way this CI issue won’t happen. Let me try and see if restarting the pipeline manually fixes it.
Author: Amar Takhar
2025-02-15T06:00:16.820Z
Nope that didn’t fix it let me see how to properly handle this situation it may be how I have the CI setup
Author: Amar Takhar
2025-02-16T09:50:17.653Z
I think we’re stuck unless you do an update the source or we have to rebase on it. GitLab will snapshot the state when an MR comes in and use that. I have seen complaints about this exact issue but no solutions anywhere so we’ll wait until there is a chance to rebase.
Author: Kinsey Moore
2025-03-04T15:20:39.238Z
approved this merge request
Author: Amar Takhar
2025-07-02T18:25:44.075Z
added 8 commits
a5e5c058…dd490c5c - 7 commits from branch
rtems/rtos:63e90c378 - build: Provide LDFLAGS for pkg-config
Author: Amar Takhar
2025-07-02T18:25:58.823Z
reset approvals from @opticron by pushing to the branch
Author: Gedare Bloom
2025-08-05T14:04:56.716Z
requested review from @chris
Author: Chris Johns
2025-10-02T23:48:33.228Z
This was reverted on
main.
Author: Sebastian Huber
2025-10-03T01:12:29.082Z
This MR doesn’t contain the reverted change. There is an associated MR for main: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/425.
725 - libio: Fix reference counting of file descriptors (opened)¶
Id |
725 |
State |
opened |
Assignee(s) |
Sebastian Huber |
Reviewer(s) |
Kinsey Moore |
Created |
2025-09-15T07:03:45.754Z |
Updated |
2025-09-15T07:05:13.750Z |
Milestone |
6.2 |
Labels |
filesystem |
Link |
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/725 |
Commit |
Summary¶
libio: Fix reference counting of file descriptors
Commit 0cf6de01df734c11212e63134551ee344a10ecec introduced a couple of issues:
ABI changes on a release branch
Redundant LIBIO_FLAGS_FREE flag: an iop is free if and only if it is
on the free list.
When the iop is freed, its reference count was set to zero. The iop
reference count must never be set to a specific value after initialization at system start. The only valid operations are increments and decrements.
In the iop free handling, there was a deadlock potential by obtaining
the libio lock while owning a file system lock.
The reference counting did not work at all under concurrent access.
This was indicated by the failing spintrcritical24 test program.
To fix this, remove the LIBIO_FLAGS_FREE and change the flag values back to the original values (restore ABI).
Actions must be performed based on state changes (flags, reference count) and not based on reading the current flags.
Remove dangerous functions rtems_libio_check_is_open(), rtems_libio_iop_flags_bad_fd(), rtems_libio_iop_is_held(), rtems_libio_iop_is_free(). The open property and references must be determined by inspecting the flags returned by rtems_libio_iop_hold() or similar.
In order to support closing a file descriptor with active references (LIBIO_FLAGS_CLOSE_BUSY), produce exactly one reference count while opening a file through the new function rtems_libio_iop_open(). An associated file node is freed when the reference count changes from one to zero.
This is an API change. Users of rtems_libio_allocate() must now call rtems_libio_iop_open() to make the iop available for use.
Author: Sebastian Huber
2025-09-15T07:03:45.916Z
requested review from @opticron
Author: Sebastian Huber
2025-09-15T07:03:45.934Z
assigned to @sebhub
Author: Sebastian Huber
2025-09-15T07:05:13.556Z
mentioned in issue #5311