21a99af009
Turned out this scenario was happening, but due to other activity, the writable block returned by the ReadResp would get downgraded or invalidated before the "unnecessary" ReadExResp/UpgradeResp returned, thus avoiding triggering the assertion that led us to catch this. --HG-- extra : convert_revision : 19dd0dbedb0227aed29da31a868ddf5ca4c50519 |
||
---|---|---|
.. | ||
00.hello | ||
00.hello.mp | ||
01.hello-2T-smt | ||
02.insttest | ||
10.linux-boot | ||
20.eio-short | ||
50.memtest | ||
80.netperf-stream |