Hi Bhargavi, This error means that there may be a deadlock in the coherence protocol. As Michael said in reply to your other email, using the ProtocolTrace debug flag is a good place to start. I would start the trace around the time the request that detects the deadlock is issued (--debug-start=16000000), if it is taking too long to get to the deadlock condition with debug flags enabled. With this output, you can trace the faulting address (0x7a8000) and try to find *why* it is deadlocking. It's possible that this is a bug in the coherence protocol.
For your other email, I would take the same steps to track down the problem. Jason On Sat, Oct 29, 2016 at 3:14 AM bhargavi upadhyay < [email protected]> wrote: > Hi , > I am trying to run PARSEC benchmark on X86 > But i am getting following error . > > panic: Possible Deadlock detected. Aborting! > version: 0 request.paddr: 0x[0x7a8010, line 0x7a8000] m_writeRequestTable: > 1 current time: 500000000 issue_time: 16023500 difference: 483976500 > @ tick 500000000 > > can anyone guide regarding this? > > -- > Thanks, > bhargavi > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
