I was setting the cpu clock domain to a specific frequency. I did not change the ruby clock. It seems the ruby-clock was taking the default value and not the cpu-clock domain. If I set both the cpu-clock and ruby-clock to the same frequency explicitly, it seems to work now. Thank you. -Anwesha Chatterjee ________________________________ From: gem5-users <[email protected]> on behalf of Afoakwa, Richard <[email protected]> Sent: Wednesday, June 26, 2019 3:53 PM To: gem5 users mailing list Subject: Re: [gem5-users] deadlock in garnet when cpu clock is changed
How do you mean exactly when you say you provide the cpu-clock option? Are you saying you set the ruby clk_domain frequency to the cpu-clock frequency, or you mean something else entirely? ________________________________ From: gem5-users <[email protected]> on behalf of Chatterjee, Anwesha <[email protected]> Sent: Friday, June 21, 2019 2:52:30 PM To: gem5 users mailing list Subject: [gem5-users] deadlock in garnet when cpu clock is changed Hi all, I am trying to run full system simulation in gem5 enabling garnet2.0. When I am providing the cpu-clock option,it gets aborted with the following error: panic: panic condition vc_busy_counter[vnet] > m_deadlock_threshold occurred: system.ruby.network.netifs1: Possible network deadlock in vnet: 4 at time: 6217848299500 I tried changing the garnet_deadlock_threshold in the Network.py file. Still I am getting the above error. It runs fine without "cpu-clock" option. It will be helpful if anyone can provide me some insight on how to run the system at different frequency with the garnet network. Thank you, Anwesha Chatterjee EECS Washington State University
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
