Bug 1918888 - coresight backtraces when booting ThunderX2
Summary: coresight backtraces when booting ThunderX2
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: aarch64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2021-01-21 16:31 UTC by Paul Whalen
Modified: 2021-11-30 19:15 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 19:15:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg.txt (449.77 KB, text/plain)
2021-01-21 16:33 UTC, Paul Whalen
no flags Details
Slightly stale TX2/A70 firmware coresight workaround (2.02 KB, text/plain)
2021-10-26 03:11 UTC, Jeremy Linton
no flags Details

Description Paul Whalen 2021-01-21 16:31:07 UTC
1. Please describe the problem:

Coresight backtraces when booting ThunderX2

2. What is the Version-Release number of the kernel:

Seeing this in Rawhide and F33

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

5.10.0-98.fc33

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Boot on ThunderX2

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes. 

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Paul Whalen 2021-01-21 16:33:52 UTC
Created attachment 1749451 [details]
dmesg.txt

Comment 2 Jeremy Linton 2021-01-21 18:28:30 UTC
Per Suzuki Poulose:

The bindings clearly show that the funnel descriptions are messed up. For e.g,

_SB.NOD1.CP00.THD0.ETM0
_SB.NOD1.CP08.THD0.ETM0
_SB.NOD1.CP08.THD1.ETM0
_SB.NOD1.CP08.THD2.ETM0
_SB.NOD1.CP08.THD3.ETM0
_SB_.NOD1.CP09.THD1.ETM0

They all "connect" to port 0 of the _SB.NOD1.FUN0. But if you look at the Node for NOD1.FUN0, it lists _SB.NOD1.CP00.THD0.ETM0 as the other end. It looks like a copy-paste error and has forgot to update the FUN for each of the items.

Comment 3 Jeremy Linton 2021-10-26 03:06:08 UTC
I guess i need to validate this for F35, I have a TX2 quirk in a MR somewhere that I can't locate at the moment and it doesn't appear to have been merged.

Comment 4 Jeremy Linton 2021-10-26 03:11:03 UTC
Created attachment 1837079 [details]
Slightly stale TX2/A70 firmware coresight workaround

This is an unmerged patch which disables foresight on A70 machines since the firmware is buggy.

Comment 5 Ben Cotton 2021-11-04 13:38:41 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-11-04 14:08:17 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2021-11-04 15:05:14 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2021-11-30 19:15:34 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.