[RTEMS Project] #4722: Odd IDLE thread ID printing from various BSPs in minimum.exe

[RTEMS trac]

#4722: Odd IDLE thread ID printing from various BSPs in minimum.exe
----------------------------+---------------------
 Reporter:  Mohd Noor Aman  |       Owner:  joel@…
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  test            |     Version:  6
 Severity:  normal          |  Resolution:
 Keywords:                  |  Blocked By:
 Blocking:                  |
----------------------------+---------------------
Description changed by Joel Sherrill:

Old description:

> I have built a new aarch64 raspberry pi 4 BSP and while trying out the
> minimum.exe on the target and the IDLE thread ID printing was
> 0x089010001. As per Joel, This is not limited to aarch64 BSPs but to
> sparc/leon3 too. Here's my output from Raspberry pi 4B aarch64
> minimum.exe
>
> {{{
> *** FATAL ***
> fatal source: 0 (INTERNAL_ERROR_CORE)
> fatal code: 5 (INTERNAL_ERROR_THREAD_EXITTED)
> RTEMS version: 6.0.0.ee92899632c823e19aa4f2e7048af3d910f59be2
> RTEMS tools: 12.1.1 20220622 (RTEMS 6, RSB
> eea379370116628dbe91f19e61ad6129aa1951ac, Newlib ea99f21)
> executing thread ID: 0x089010001
> executing thread name: IDLE
> }}}

New description:

 I have built a new aarch64 raspberry pi 4 BSP and while trying out the
 minimum.exe on the target and the IDLE thread ID printing was 0x089010001.
 As per Joel, This is not limited to aarch64 BSPs but to sparc/leon3 too.
 Here's my output from Raspberry pi 4B aarch64 minimum.exe

 {{{
 *** FATAL ***
 fatal source: 0 (INTERNAL_ERROR_CORE)
 fatal code: 5 (INTERNAL_ERROR_THREAD_EXITTED)
 RTEMS version: 6.0.0.ee92899632c823e19aa4f2e7048af3d910f59be2
 RTEMS tools: 12.1.1 20220622 (RTEMS 6, RSB
 eea379370116628dbe91f19e61ad6129aa1951ac, Newlib ea99f21)
 executing thread ID: 0x089010001
 executing thread name: IDLE
 }}}

 From the cpuuse command, this is the IDLE thread ID:

 {{{


  0x09010001 | IDLE                                   |     20.301428 |
 96.344
 Looks like a bug somewhere not related to the Pi4
 }}}

 For some reason, the MSB is set. Doesn't look like sign-extension. But
 could be a bug in printk() versus printf().

--

--
Ticket URL: <http://devel.rtems.org/ticket/4722#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project