On 24.04.2013 09:07, huangyongbing wrote:
> Hi all, > > I want to save the changing of disk image. According to the introduction in http://gem5.org/Bbench-gem5 [2], I boot the simulation using the raw idle disk, and execute "busybox sync" and "busybox halt -f". Then, the system is pending there for several hours. I just modify the image by creating a file immediately after the gem5 terminal shell is available. The following is the output. So what may be the problem? > > root@android:/data # busybox sync > > busybox sync > > root@android:/data # > > root@android:/data # busybox halt -f > > busybox halt -f > > <5>sd 0:0:1:0: [sdb] Stopping disk > > [ 3.369288] sd 0:0:1:0: [sdb] Stopping disk > > <5>sd 0:0:0:0: [sda] Stopping disk > > [ 3.369372] sd 0:0:0:0: [sda] Stopping disk > > <0>System halted. > > [ 3.369491] System halted. > > Thanks! > > Best regards, > > Yongbing Huang > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users [1] Hi, I'm not sure that we correctly notice the signals that correspond to the system being powered down, as it's remarkably platform specific. You can certainly just terminate gem5 with control-c at this point and it should be fine. Ali Links: ------ [1] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users [2] http://gem5.org/Bbench-gem5
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
