[test-triage] `pendingReqPerSrc_M` fails in `tlul_assert.sv` during `rom_e2e_shutdown_output` chip-level test
Open
Nobody has claimed this yet.
Component:TestTriage
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Hierarchy of regression failure
Chip Level
Failure Description
UVM_INFO @ 20792.572969 us: (chip_sw_rom_e2e_base_vseq.sv:19) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_rom_e2e_shutdown_output_vseq] Disconnecting UART agent from UART 0 ...
UVM_INFO @ 20792.572969 us: (chip_sw_rom_e2e_shutdown_output_vseq.sv:14) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_rom_e2e_shutdown_output_vseq] Backdoor overwriting the lifecycle state and applying POR ...
UVM_INFO @ 20792.572969 us: (chip_base_vseq.sv:49) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_rom_e2e_shutdown_output_vseq] Asserting POR_N
UVM_INFO @ 20802.572969 us: (chip_base_vseq.sv:53) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_rom_e2e_shutdown_output_vseq] POR_N complete
"../src/lowrisc_tlul_common_0.1/rtl/tlul_assert.sv", 268: tb.dut.top_earlgrey.u_rstmgr_aon.tlul_assert_device.gen_device.pendingReqPerSrc_M: started at 22712150664ps failed at 22712150664ps
Offending '(pend_req[h2d.a_source].pend == 0)'
UVM_ERROR @ 22712.150664 us: (tlul_assert.sv:268) [ASSERT FAILED] pendingReqPerSrc_M
Steps to Reproduce
- GitHub Revision: af2d1709f9
- dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i rom_e2e_shutdown_output --build-seed 13980492992314588037778262839223440914483141513139750793389284041724730149540 --seed 24635030167594819145773685420472791935838066513677808134159163261625674501968
Tests with similar or related failures
Same assert, different chip-level test: chip_sw_pwrmgr_random_sleep_all_reset_reqs https://github.com/lowRISC/opentitan/issues/24349
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the rom_e2e_shutdown_output failure with the provided dvsim command and revision af2d1709f9. Inspect tlul_assert.sv around line 268 and compare the related failure in issue 24349; done means identifying and resolving the pendingReqPerSrc_M failure, then confirming the chip-level test passes.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100