This problem may be related to my earlier post i sent today about "Debugging Ruby Deadlocks", but when adding the "RubyQueue" traceflag for 32 cores you get this error: "build/ALPHA_FS_MOESI_CMP_directory/m5.opt -d ruby_opt/ --trace-flags=RubyQueue configs/example/ruby_fs.py -b fft_64t_base -n 1 ... panic: Invalid range for type MachineType @ cycle 793500 [MachineType_to_string:build/ALPHA_FS_MOESI_CMP_directory/mem/protocol/MachineType.cc, line 42] Memory Usage: 2312860 KBytes For more information see: http://www.m5sim.org/panic/f419fb7 Program aborted at cycle 793500 Aborted "
I thought this was solved a while ago by a previous patch but it seems to be an issue again. Is it something in the SLICC that isnt being defined properly when the core count is large? If anybody has any thoughts , please let me know so we can patch it and push the changeset in the tree. Note: I dont get this problem when running for just 1 core. -- - Korey _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
