Hello,
Yes, it is that one. There doesn't seem to be anything wrong.
Could you try running the simulation without the hack_back script and
connecting with telnet to try checkpointing there (with m5 checkpoint)? And
does it need a username and password?
Kind regards
Serhat
________________________________________
From: gem5-users [gem5-users-boun...@gem5.org] on behalf of Yunxia Zhu
[emilia...@gmail.com]
Sent: 29 August 2018 16:19
To: gem5 users mailing list
Subject: Re: [gem5-users] Create Checkpoint
Hello
I custom the kernel and image. My kernel is linux 4.8.13-64 and my image is
ubuntu-16.04.1-server-amd64. What is m5out/system.terminal? Is this one?
zhu@zhu-Vostro-3560 ~ $ telnet localhost 3456
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
==== m5 slave terminal: Terminal 0 ====
Linux version 4.8.13 (zhu@zhu-Vostro-3560) (gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.10) ) #1 SMP Mon Aug 13 11:14:06 CEST 2018
Command line: earlyprintk=ttyS0 console=ttyS0 lpj=7999923 root=/dev/hda1
CPU: vendor_id 'M5 Simulator' unknown, using generic init.
CPU: Your system may be unstable.
x86/fpu: Legacy x87 FPU detected.
x86/fpu: Using 'eager' FPU context switches.
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
BIOS-e820: [mem 0x0000000020000000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000ffff0000-0x00000000ffffffff] reserved
bootconsole [earlyser0] enabled
NX (Execute Disable) protection: active
SMBIOS 2.5 present.
AGP: No AGP bridge found
e820: last_pfn = 0x20000 max_arch_pfn = 0x400000000
MTRR: Disabled
x86/PAT: MTRRs disabled, skipping PAT initialization too.
x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC
CPU MTRRs all blank - virtualized system.
found SMP MP-table at [mem 0x000f0050-0x000f005f] mapped at [ffff8800000f0050]
ACPI: Early table checksum verification disabled
ACPI BIOS Error (bug): A valid RSDP was not found (20160422/tbxfroot-243)
Zone ranges:
DMA [mem 0x0000000000001000-0x0000000000ffffff]
DMA32 [mem 0x0000000001000000-0x000000001fffffff]
Normal empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x0000000000001000-0x000000000009efff]
node 0: [mem 0x0000000000100000-0x000000001fffffff]
Initmem setup node 0 [mem 0x0000000000001000-0x000000001fffffff]
Intel MultiProcessor Specification v1.4
MPTABLE: OEM ID:
MPTABLE: Product ID:
MPTABLE: APIC at: 0xFEE00000
Processor #0 (Bootup-CPU)
IOAPIC[0]: apic_id 1, version 20, address 0xfec00000, GSI 0-23
Processors: 1
smpboot: Allowing 1 CPUs, 0 hotplug CPUs
e820: [mem 0xc0000000-0xfffeffff] available for PCI devices
Booting paravirtualized kernel on bare hardware
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 1910969940391419 ns
setup_percpu: NR_CPUS:8192 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1
percpu: Embedded 31 pages/cpu @ffff88001fc00000 s89496 r8192 d29288 u2097152
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129161
Kernel command line: earlyprintk=ttyS0 console=ttyS0 lpj=7999923 root=/dev/hda1
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
AGP: Checking aperture...
AGP: No AGP bridge found
Memory: 505236K/523896K available (4240K kernel code, 593K rwdata, 1620K
rodata, 992K init, 636K bss, 18660K reserved, 0K cma-reserved)
Hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 64.
RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=1.
RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=1
NR_IRQS:524544 nr_irqs:256 16
Console: colour dummy device 80x25
console [ttyS0] enabled
console [ttyS0] enabled
bootconsole [earlyser0] disabled
bootconsole [earlyser0] disabled
tsc: Fast TSC calibration using PIT
tsc: Detected 1999.954 MHz processor
Calibrating delay loop (skipped) preset value.. 15999.84 BogoMIPS (lpj=7999923)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes)
CPU: CPU feature xsave disabled, no CPUID level 0xd
mce: CPU supports 4 MCE banks
mce: unknown CPU type - not enabling MCE support
Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
Freeing SMP alternatives memory: 24K (ffffffff8198e000 - ffffffff81994000)
smpboot: APIC(0) Converting physical 0 to logical package 0
smpboot: Max logical packages: 1
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
smpboot: CPU0: M5 Simulator Fake M5 x86_64 CPU (family: 0xf, model: 0x25,
stepping: 0x1)
Performance Events: no PMU driver, software events only.
x86: Booted up 1 node, 1 CPUs
smpboot: Total of 1 processors activated (15999.84 BogoMIPS)
devtmpfs: initialized
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
1911260446275000 ns
NET: Registered protocol family 16
cpuidle: using governor ladder
PCI: Using configuration type 1 for base access
HugeTLB registered 2 MB page size, pre-allocated 0 pages
ACPI: Interpreter disabled.
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
<giome...@linux.it<mailto:giome...@linux.it>>
PTP clock support registered
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffffffff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0000:00:04.0: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
pci 0000:00:04.0: legacy IDE quirk: reg 0x14: [io 0x03f6]
pci 0000:00:04.0: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
pci 0000:00:04.0: legacy IDE quirk: reg 0x1c: [io 0x0376]
clocksource: Switched to clocksource refined-jiffies
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
pnp: PnP ACPI: disabled
pci 0000:00:04.0: BAR 6: assigned [mem 0xc0000000-0xc00007ff pref]
pci 0000:00:04.0: BAR 4: assigned [io 0x1000-0x100f]
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
platform rtc_cmos: registered platform RTC device (no PNP device found)
futex hash table entries: 256 (order: 2, 16384 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(1325376000.185:1): initialized
workingset: timestamp_bits=62 max_order=17 bucket_order=0
fuse init (API version 7.25)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 8250
Linux agpgart interface v0.103
brd: module loaded
loop: module loaded
Uniform Multi-Platform E-IDE driver
piix 0000:00:04.0: IDE controller (0x8086:0x7111 rev 0x00)
pci 0000:00:04.0: enabling device (0000 -> 0001)
pci 0000:00:04.0: PCI->APIC IRQ transform: INT A -> IRQ 16
piix 0000:00:04.0: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1000-0x1007
ide1: BM-DMA at 0x1008-0x100f
hda: M5 IDE Disk, ATA DISK drive
hdb: M5 IDE Disk, ATA DISK drive
hda: UDMA/33 mode selected
hdb: UDMA/33 mode selected
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x39a805c48af,
max_idle_ns: 881590404252 ns
clocksource: Switched to clocksource tsc
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide_generic: please use "probe_mask=0x3f" module parameter for probing all
legacy ISA IDE ports
ide-gd driver 1.18
hda: max request size: 128KiB
hda: 16777216 sectors (8589 MB), CHS=16644/16/63
hda: hda1
hdb: max request size: 128KiB
hdb: 16777216 sectors (8589 MB), CHS=16644/16/63
random: fast init done
hdb: hdb1
ide-cd driver 5.00
Loading iSCSI transport class v2.0-870.
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
igb: Copyright (c) 2007-2014 Intel Corporation.
igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.0.2-k
igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.4.0-k
ixgbe: Copyright (c) 1999-2016 Intel Corporation.
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver -
version 3.2.2-k
ixgbevf: Copyright (c) 2009 - 2015 Intel Corporation.
ixgb: Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI
ixgb: Copyright (c) 1999-2008 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
uhci_hcd: USB Universal Host Controller Interface driver
i8042: PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
mce: Unable to init device /dev/mcelog (rc: -5)
microcode: no support for this CPU vendor
EXT4-fs (hda1): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (hda1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 3:1.
devtmpfs: mounted
Freeing unused kernel memory: 992K (ffffffff81896000 - ffffffff8198e000)
Write protecting the kernel read-only data: 8192k
Freeing unused kernel memory: 1888K (ffff880001428000 - ffff880001600000)
Freeing unused kernel memory: 428K (ffff880001795000 - ffff880001800000)
systemd[1]: System time before build time, advancing clock.
systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA
+APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4
+SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
systemd[1]: Detected architecture x86-64.
Welcome to Ubuntu 16.04.1 LTS!
systemd[1]: Set hostname to <zhu>.
systemd[1]: Listening on Syslog Socket.
[ OK ] Listening on Syslog Socket.
systemd[1]: Created slice System Slice.
[ OK ] Created slice System Slice.
systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password Requests to Wall Directory Watch.
systemd[1]: Listening on LVM2 poll daemon socket.
[ OK ] Listening on LVM2 poll daemon socket.
systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Listening on fsck to fsckd communication Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Slices.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ OK ] Listening on Journal Socket.
Mounting Huge Pages File System...
Starting Journal Service...
Starting Uncomplicated firewall...
Mounting POSIX Message Queue File System...
Starting Set console keymap...
Starting Nameserver information manager...
[ OK ] Reached target Swap.
[ OK ] Reached target User and Group Name Lookups.
Starting Load Kernel Modules...
[ OK ] Started Read required files in advance.
[ OK ] Listening on LVM2 metadata daemon socket.
Starting Monitoring of LVM2 mirrors... dmeventd or progress polling...
Starting Create Static Device Nodes in /dev...
[ OK ] Started Uncomplicated firewall.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
Mounting FUSE Control File System...
Starting Apply Kernel Variables...
Mounting Configuration File System...
[ OK ] Mounted Huge Pages File System.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Started LVM2 metadata daemon.
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Mounted Configuration File System.
[ OK ] Mounted FUSE Control File System.
[ OK ] Started Journal Service.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Nameserver information manager.
[ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress polling.
Starting udev Kernel Device Manager...
[ OK ] Started udev Kernel Device Manager.
Starting Remount Root and Kernel File Systems...
[ OK ] Started Remount Root and Kernel File Systems.
Starting Load/Save Random Seed...
Starting udev Coldplug all Devices...
Starting Flush Journal to Persistent Storage...
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Found device /dev/ttyS0.
[ OK ] Started udev Coldplug all Devices.
[ OK ] Started Set console keymap.
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Set console font and keymap...
Starting Tell Plymouth To Write Out Runtime Data...
Starting Create Volatile Files and Directories...
Starting LSB: AppArmor initialization...
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Create Volatile Files and Directories.
[ OK ] Started LSB: AppArmor initialization.
Starting Raise network interfaces...
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[ OK ] Started Network Time Synchronization.
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Time Synchronized.
[ OK ] Reached target System Initialization.
Starting Socket activation for snappy daemon.
[ OK ] Started ACPI Events Check.
[ OK ] Started Timer to automatically refresh installed snaps.
[ OK ] Started Daily apt activities.
Starting LXD - unix socket.
[ OK ] Started Trigger resolvconf update for networkd DNS.
[ OK ] Reached target Paths.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Listening on ACPID Listen Socket.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
[ OK ] Listening on Socket activation for snappy daemon.
[ OK ] Listening on LXD - unix socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting LSB: MD monitoring daemon...
[ OK ] Started Deferred execution scheduler.
Starting LSB: Record successful boot for GRUB...
[ OK ] Started Snappy daemon.
Starting Login Service...
[ OK ] Started FUSE filesystem for LXC.
[ OK ] Started D-Bus System Message Bus.
[ OK ] Started ACPI event daemon.
Starting System Logging Service...
Starting Accounts Service...
[ OK ] Started Regular background program processing daemon.
Starting LXD - container startup/shutdown...
[ OK ] Started LSB: MD monitoring daemon.
[ OK ] Started System Logging Service.
[FAILED] Failed to start Accounts Service.
See 'systemctl status accounts-daemon.service' for details.
[ OK ] Started Login Service.
[ OK ] Started LXD - container startup/shutdown.
[ OK ] Started LSB: Record successful boot for GRUB.
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
Starting iSCSI initiator daemon (iscsid)...
Starting /etc/rc.local Compatibility...
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started iSCSI initiator daemon (iscsid).
Starting Login to default iSCSI targets...
[ OK ] Started Login to default iSCSI targets.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Starting LSB: daemon to balance interrupts for SMP systems...
Starting Permit User Sessions...
Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
Starting LSB: automatic crash report generation...
[ OK ] Started Permit User Sessions.
Starting Terminate Plymouth Boot Screen...
Starting Hold until boot process finishes up...
[ OK ] Started Set console font and keymap.
[ OK ] Started Terminate Plymouth Boot Screen.
[ OK ] Started Hold until boot process finishes up.
[ OK ] Started Serial Getty on ttyS0.
Starting Set console scheme...
[ OK ] Created slice system-getty.slice.
[ OK ] Started Getty on tty1.
[ OK ] Reached target Login Prompts.
[ OK ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[ OK ] Started Set console scheme.
[ OK ] Started LSB: daemon to balance interrupts for SMP systems.
[ OK ] Started LSB: automatic crash report generation.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Stop ureadahead data collection 45s after completed startup.
[ OK ] Started Update UTMP about System Runlevel Changes.
Ubuntu 16.04.1 LTS zhu ttyS0
with best regards
yunxia zhu
On Wed, 29 Aug 2018 at 16:27, Serhat Gesoglu
<serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>> wrote:
Hello,
I am not really sure if it is normal for it to run that long. Are you using
custom image/kernel files or the ones dowloaded from gem5 website?
Could you also check your m5out/system.terminal to see if there is anything
useful?
Kind regards
Serhat Gesoglu
________________________________________
From: gem5-users
[gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>] on behalf of
Yunxia Zhu [emilia...@gmail.com<mailto:emilia...@gmail.com>]
Sent: 29 August 2018 07:37
To: gem5 users mailing list
Subject: Re: [gem5-users] Create Checkpoint
Hi Serhat Gesoglu
I run the gem5 for one night and the simulation still didn't end. It has the
same result which I showed before. It seems like it hung. Did you have the same
situation? Thank you.
with best regards
Yunxia Zhu
On Tue, 28 Aug 2018 at 13:53, Serhat Gesoglu
<serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>>>
wrote:
Hello,,
You should wait for the simulation to end. I am not sure which cpu type you are
using but you might want to try --cpu-type=AtomicSimpleCPU if you are not
already using it. Otherwise you should give it more time.
Kind regards
Serhat
________________________________________
From: gem5-users
[gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>>]
on behalf of Yunxia Zhu
[emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>>]
Sent: 28 August 2018 12:44
To: gem5 users mailing list
Subject: Re: [gem5-users] Create Checkpoint
Hello Serhat Gesoglu,
I didn't get any error and I didn't get "checkpoint simulation" either. My
output is as same as the output when I simulate gem5 OS without script. And it
is attached below.
gem5 Simulator System. http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.
gem5 compiled Aug 8 2018 11:04:48
gem5 started Aug 28 2018 13:21:05
gem5 executing on zhu-Vostro-3560, pid 4114
command line: build/X86/gem5.opt configs/example/fs.py
--script=configs/boot/hack_back_ckpt.rcS
Global frequency set at 1000000000000 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range
assigned (512 Mbytes)
info: kernel located at:
/home/zhu/gem5_FS_64/gem5/full_system_sample/x86-system/binaries/vmlinux
Listening for com_1 connection on port 3456
0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012
0: system.remote_gdb: listening for remote gdb on port 7000
warn: Reading current count from inactive timer.
**** REAL SIMULATION ****
info: Entering event queue @ 0. Starting simulation...
warn: x86 cpuid family 0x0000: unimplemented function 6
warn: x86 cpuid family 0x0000: unimplemented function 6
warn: x86 cpuid family 0x0000: unimplemented function 6
warn: instruction 'fninit' unimplemented
warn: Don't know what interrupt to clear for console.
warn: x86 cpuid family 0x0000: unimplemented function 6
warn: x86 cpuid family 0x0000: unimplemented function 6
warn: x86 cpuid family 0x0000: unimplemented function 6
warn: Tried to clear PCI interrupt 14
warn: Write to unknown i8042 (keyboard controller) command port.
warn: instruction 'prefetch_nta' unimplemented
warn: instruction 'fwait' unimplemented
I don't know why it happens. Is it possible that it needs a lot of time to
create checkpoint? It has already run for one hour. Could you give me some
advice? Thank you
with best regards
Yunxia Zhu
On Tue, 28 Aug 2018 at 11:53, Serhat Gesoglu
<serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>>>>
wrote:
Hello,
Do you get an error after running the first command? ($ build/X86/gem5.opt
configs/example/fs.py --script=configs/boot/hack_back_ckpt.rcS). The output
should say something like "Checkpointing simulation...". This command should
create a folder starting with "cpt" in your m5out folder. And then you should
be able to use it with "-r 1 --script=[your script]".
If you are using "hack_back_ckpt.rcS" you don't need to use "m5 checkpoint".
Otherwise you can use it in a script file (to be loaded with
--script=[path/to/file/checkpoint.rcS]) for instance:
$ cat runscripts/checkpoint.rcS
m5 checkpoint
m5 exit
This will create a checkpoint and exit. But be aware that when you use a script
like this, this same script will be loaded to your system and it will just exit
when you restore from this checkpoint (this was my mistake when I first used
checkpoints).
So you need to put the commands you want to simulate between the last two
commands:
m5 checkpoint
./test.sh
m5 exit
Kind regards
Serhat
________________________________________
From: gem5-users
[gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>>>]
on behalf of Yunxia Zhu
[emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>>>]
Sent: 28 August 2018 10:28
To: gem5 users mailing list
Subject: Re: [gem5-users] Create Checkpoint
Hello Serhat Gesoglu,
I used m5 commands but I still failed to create checkpoint.
Here it is details:
Create checkpoint:
gem5 $ build/X86/gem5.opt configs/example/fs.py
--script=configs/boot/hack_back_ckpt.rcS
Restore checkpoint:
gem5 $ build/X86/gem5.opt configs/example/fs.py -r 1
Then it shows "checkpoint 1 not found"
And I am also confused where to add "m5 checkpoint". Could you show me the
command? Thank you very much.
with best regards
Yunxia Zhu
On Tue, 21 Aug 2018 at 17:05, Serhat Gesoglu
<serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>>><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk><mailto:serhat.geso...@manchester.ac.uk<mailto:serhat.geso...@manchester.ac.uk>>>>>
wrote:
Hello,
gem5-gpu is the combination of gem5 and gpgpu-sim. You may find more
information here: https://gem5-gpu.cs.wisc.edu/wiki/
If you are not planning to simulate gpus sticking to gem5 might be a better
idea.
To create checkpoints you have two options.
One is the command line option "--checkpoint-at-end". This will create a
checkpoint when your simulation ends.
The second way is to use use m5 commands (which I think the easier way).
There is a script file: "configs/boot/hack_back_ckpt.rcS" to see more on this.
You need to run the simulation with this script first. It creates a checkpoint
and stops. The second time (when restored from a checkpoint), you use your own
script.
Kind regards
Serhat Gesoglu
________________________________________
From: gem5-users
[gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>>><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org><mailto:gem5-users-boun...@gem5.org<mailto:gem5-users-boun...@gem5.org>>>>]
on behalf of Yunxia Zhu
[emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>>><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com><mailto:emilia...@gmail.com<mailto:emilia...@gmail.com>>>>]
Sent: 21 August 2018 15:45
To: gem5 users mailing list
Subject: [gem5-users] Create Checkpoint
Hello everyone,
I want to create a checkpoint to speed up startup of the gem5 OS, but I have
some doubts.
1. When I search it online, someone use gem5.gpu to create checkpoint. What is
the difference between gem5 and gem5-gpu? In my opinion they are different
simulators.
2. After checking some document I still have no idea about the checkpoint. I
don't know how to start to create it. Could anyone give me any idea to do it?
Thanks for your time and reply.
with best regards
Yunxia Zhu
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>>><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>>>>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>>>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org><mailto:gem5-users@gem5.org<mailto:gem5-users@gem5.org>>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
