oxidecomputer / oxidecomputer/dendrite
Moving to Multicast: Look into Warnings found in Tofinio Simulator
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
We're seeing warnings about Inconsistent data wrt SRAM type in the simulator log. We need to explore this, as it came about when doing PRE in https://github.com/oxidecomputer/dendrite/pull/14.
Here's an example from a packet-test test job:
160 :04-22 12:26:28.351808: <0,3,4,7,4> WARN MauSramReg::is_match_sram() Inconsistent data wrt SRAM type
161 :04-22 12:26:28.351812: <0,3,4,7,5> WARN MauSramReg::is_match_sram() Inconsistent data wrt SRAM type
162 :04-22 12:26:28.351815: <0,3,4,7,5> WARN MauSramReg::is_match_sram() Inconsistent data wrt SRAM type
163 :04-22 12:27:52.172975: :-:-:<0,-,0>:Begin packet processing
164 :04-22 12:27:52.173073: :0x1:-:<0,1,0>:========== Ingress Pkt from port 144 (64 bytes) ==========
165 :04-22 12:27:52.173081: :0x1:-:<0,1,0>:Packet :
166 :04-22 12:27:52.173087: :0x1:-:<0,1,0>:e0 d5 5e 67 89 ac e0 d5 5e 67 89 ab 08 00 45 00
167 :04-22 12:27:52.173093: :0x1:-:<0,1,0>:00 1c 00 00 40 00 ff 11 54 a8 0a 0a 09 0a 0a 0a
168 :04-22 12:27:52.173098: :0x1:-:<0,1,0>:0a 0b 0d 05 11 5c 00 08 ba 54 00 00 00 00 00 00
169 :04-22 12:27:52.173103: :0x1:-:<0,1,0>:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170 :04-22 12:27:52.173114: :0x1:-:<0,1,->:========== Packet to input parser: from port 144 (96 bytes) ==========
171 :04-22 12:27:52.173119: :0x1:-:<0,1,->:Packet :
172 :04-22 12:27:52.173124: :0x1:-:<0,1,->:00 90 00 14 98 ce 41 c0 00 00 00 00 00 00 00 00
173 :04-22 12:27:52.173129: :0x1:-:<0,1,->:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
174 :04-22 12:27:52.173134: :0x1:-:<0,1,->:e0 d5 5e 67 89 ac e0 d5 5e 67 89 ab 08 00 45 00
175 :04-22 12:27:52.173139: :0x1:-:<0,1,->:00 1c 00 00 40 00 ff 11 54 a8 0a 0a 09 0a 0a 0a
Contributor guide
No contributing guide indexed for this repository
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
Start with the linked simulator log and the packet-test example, focusing on the repeated MauSramReg::is_match_sram() warnings. Compare the behavior introduced around PRE in dendrite/pull/14 and determine the source of the SRAM-type inconsistency; done means the warning is explained and any required simulator or test change is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100