lowRISC / lowRISC/opentitan

[test-triage,earlgrey] chip_sw_ast_clk_rst_inputs

Open
#26,900 0 comments 0 reactions 0 assignees View on GitHub

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_ERROR @ 19266.254833 us: (sw_logger_if.sv:526) [ast_clk_rst_inputs_sim_dv(sw/device/tests/sim_dv/ast_clk_rst_inputs.c:128)] CHECK-fail: Recov alert not correctly observed in alert handler

### Steps to Reproduce

- GitHub Revision: 950d8cda3209783a1abab34cf3444d686866a1f6
- 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 chip_sw_ast_clk_rst_inputs --fixed-seed 1

### Tests with similar or related failures

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

Reproduce the regression with ./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_ast_clk_rst_inputs --fixed-seed 1 at revision 950d8cda3209783a1abab34cf3444d686866a1f6. Start with sw/device/tests/sim_dv/ast_clk_rst_inputs.c:128 and the sw_logger_if.sv:526 failure, then determine why the recovery alert is not observed correctly; done means the check passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.