It looks like it's resuming from the checkpoint but then something is
going wrong after that. If you don't use checkpointing and run
straight through does it work? If it does, then I suspect some
interrupt related state isn't being checkpointed or drained properly.
Otherwise something could be wrong with interrupt handling in the
simulated hardware, or configuration info injected into the simulated
memory. Please try running without checkpointing, and then if possible
put your configs, disk image, kernel, and command line where I can get
at them so I can try to reproduce the problem.
Gabe
Quoting Feng Lu <[email protected]>:
Hi,
I'm running m5.fast for X86_FS and couldn't resume a checkpoint. The linux
kernel is 2.6.30.5.
The command I used was "build/X86_FS/m5.fast configs/example/fs.py -r 1".
The checkpoint was dumped from a previous run, after the system just boot.
The simulator side goes like:
===============================================================
M5 Simulator System
Copyright (c) 2001-2008
The Regents of The University of Michigan
All Rights Reserved
M5 compiled Apr 11 2011 17:49:05
M5 revision Unknown
M5 started Apr 12 2011 15:16:06
M5 executing on MACHINENAME
command line: build/X86_FS/m5.fast configs/example/fs.py -r 2
Global frequency set at 1000000000000 ticks per second
info: kernel located at: MACHINEPATH/binaries/vmlinux-2.6.30-x86_64
Listening for pc connection on port 3456
warn: Reading current count from inactive timer.
For more information see: http://www.m5sim.org/warn/1ea2be46
0: system.remote_gdb.listener: listening for remote gdb on port 7000
warn: Interrupts::unserialize unimplemented!
For more information see: http://www.m5sim.org/warn/1bc5b71f
warn: Interrupts::unserialize unimplemented!
For more information see: http://www.m5sim.org/warn/1bc5b71f
**** REAL SIMULATION ****
info: Entering event queue @ 35307763854000. Starting simulation...
warn: Don't know what interrupt to clear for console.
For more information see: http://www.m5sim.org/warn/7fe1004f
===============================================================
and the console side prints:
===============================================================
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
do_IRQ: 0.36 No irq handler for vector (irq -1)
===============================================================
then everything stays still for a very long time and exits.
I'm thinking whether this has anything to do with the linux kernel.
Does anyone have similar experience and possibly a solution? I'm digging
into it but it would be nice if someone have solved this before.
Thanks,
Feng
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
