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
14 lines
471 B
Plaintext
14 lines
471 B
Plaintext
M5 Simulator System
|
|
|
|
Copyright (c) 2001-2006
|
|
The Regents of The University of Michigan
|
|
All Rights Reserved
|
|
|
|
|
|
M5 compiled Nov 13 2007 20:22:15
|
|
M5 started Tue Nov 13 20:22:26 2007
|
|
M5 executing on vm1
|
|
command line: build/ALPHA_SE/m5.fast -d build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest tests/run.py quick/50.memtest/alpha/linux/memtest
|
|
Global frequency set at 1000000000000 ticks per second
|
|
Exiting @ tick 162969030 because maximum number of loads reached
|