Hi there, I'm running GEM5 stable (9073:f75ee4849c40) in FS mode and 2 "detailed" cores with classic (i.e., non-Ruby) memory system, running linux version 2.6.27.62 compiled for x86-64.
When mounting a disk in the simulated machine, it gets all stuck in a spinlock (_spin_lock_irq for core 0 and _spin_lock_irqsave for core 1). Just before the busy-waiting, each routine performs an atomic operation (lock xadd), which I'm assuming is the root of the problem. Does switching to Ruby have any chance of fixing the problem? Last time I tried with the default scripts and activating Ruby, it was producing an assertion error when instantiating the simulator. If not, could anyone tell me if it's worth forward-porting my private GEM5 changes to the latest development version of GEM5 in the hopes that such an issue will be fixed there? I'm asking because the status matrix page still says locked accesses are not supported in my aforementioned configuration. Thanks a lot, Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
