rr-debugger / rr-debugger/rr

exit_test fails on ryzen 9 3900x (+ zen kernel module)

Open
#3,025 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

Using rr 5.5.0 from Fedora 35.
Some of these failures seem to be related to the testsuite itself (e.g. it tries to break on a symbol that doesn't exist):
https://gist.github.com/edwintorok/452bf733ee9f03a87cb2649813cc5188

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 43 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 9 3900X 12-Core Processor
CPU family: 23
Model: 113
Thread(s) per core: 2
Core(s) per socket: 12
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU max MHz: 4672.0698
CPU min MHz: 2200.0000
BogoMIPS: 7600.14
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fx
sr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor s
sse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a mi
salignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l
3 hw_pstate ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsa
veopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd ara
t npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload
vgif v_spec_ctrl umip rdpid overflow_recov succor smca sme sev sev_es
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 384 KiB (12 instances)
L1i: 384 KiB (12 instances)
L2: 6 MiB (12 instances)
L3: 64 MiB (4 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-23
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Full AMD retpoline, IBPB conditional, STIBP conditional, RSB filling
Srbds: Not affected
Tsx async abort: Not affected

I have the kernel module for Zen installed:

dmesg|grep MSR
[  197.049667] MSR_AMD64_LS_CFG for cpu 23 was 0x6404000000000, setting to 0x46404000000000
[  197.049670] MSR_AMD64_LS_CFG for cpu 19 was 0x46404000000000, setting to 0x46404000000000
[  197.049670] MSR_AMD64_LS_CFG for cpu 7 was 0x6404000000000, setting to 0x46404000000000
[  197.049671] MSR_AMD64_LS_CFG for cpu 6 was 0x6404000000000, setting to 0x46404000000000
[  197.049672] MSR_AMD64_LS_CFG for cpu 18 was 0x46404000000000, setting to 0x46404000000000
[  197.049681] MSR_AMD64_LS_CFG for cpu 3 was 0x6404000000000, setting to 0x46404000000000
[  197.049682] MSR_AMD64_LS_CFG for cpu 15 was 0x46404000000000, setting to 0x46404000000000
[  197.049682] MSR_AMD64_LS_CFG for cpu 4 was 0x6404000000000, setting to 0x46404000000000
[  197.049683] MSR_AMD64_LS_CFG for cpu 16 was 0x46404000000000, setting to 0x46404000000000
[  197.049684] MSR_AMD64_LS_CFG for cpu 0 was 0x46404000000000, setting to 0x46404000000000
[  197.049683] MSR_AMD64_LS_CFG for cpu 12 was 0x6404000000000, setting to 0x46404000000000
[  197.049684] MSR_AMD64_LS_CFG for cpu 17 was 0x6404000000000, setting to 0x46404000000000
[  197.049685] MSR_AMD64_LS_CFG for cpu 5 was 0x46404000000000, setting to 0x46404000000000
[  197.049686] MSR_AMD64_LS_CFG for cpu 22 was 0x6404000000000, setting to 0x46404000000000
[  197.049687] MSR_AMD64_LS_CFG for cpu 10 was 0x46404000000000, setting to 0x46404000000000
[  197.049687] MSR_AMD64_LS_CFG for cpu 1 was 0x6404000000000, setting to 0x46404000000000
[  197.049688] MSR_AMD64_LS_CFG for cpu 13 was 0x46404000000000, setting to 0x46404000000000
[  197.049688] MSR_AMD64_LS_CFG for cpu 2 was 0x6404000000000, setting to 0x46404000000000
[  197.049689] MSR_AMD64_LS_CFG for cpu 14 was 0x46404000000000, setting to 0x46404000000000
[  197.049691] MSR_AMD64_LS_CFG for cpu 9 was 0x46404000000000, setting to 0x46404000000000
[  197.049690] MSR_AMD64_LS_CFG for cpu 21 was 0x6404000000000, setting to 0x46404000000000
[  197.049691] MSR_AMD64_LS_CFG for cpu 8 was 0x6404000000000, setting to 0x46404000000000
[  197.049693] MSR_AMD64_LS_CFG for cpu 20 was 0x46404000000000, setting to 0x46404000000000
[  197.049698] MSR_AMD64_LS_CFG for cpu 11 was 0x46404000000000, setting to 0x46404000000000

Is this a bug in how the rr-testsuite package was built (e.g. did it strip some symbols it shouldn't), i.e. should I open a Fedora bug too?

(I've now installed sudo dnf debuginfo-install rr-testsuite and rerunning the failed tests,will report back)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the exit_test failures and the linked gist, then rerun the failed rr-testsuite tests after installing rr-testsuite debuginfo as described. Compare whether the missing-symbol failures persist; done means determining whether the cause is Fedora packaging or rr's testsuite and reporting the result.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools, operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.