Hi Nilay,

You're right. It's sorted now. Thanks for pointing it out.

Andreas

On 07/03/2013 07:12, "Nilay" <[email protected]> wrote:

>Hi Andreas
>
>I just ran gem5's latest edition and it generates the following error
>message. Can you look in to this? It seems to be related to the recent
>changes you made to the classic memory system.
>
>[nilay@ribera] (80)$ ./build/X86/gem5.debug ./configs/example/fs.py
>--kernel x86_64-vmlinux-2.6.22.9  --cpu-type=timing
>gem5 Simulator System.  http://gem5.org
>gem5 is copyrighted software; use the --copyright option for details.
>
>gem5 compiled Mar  7 2013 00:55:51
>gem5 started Mar  7 2013 00:58:39
>gem5 executing on ribera.cs.wisc.edu
>command line: ./build/X86/gem5.debug ./configs/example/fs.py --kernel
>x86_64-vmlinux-2.6.22.9 --cpu-type=timing
>warn: add_child('terminal'): child 'terminal' already has parent
>Global frequency set at 1000000000000 ticks per second
>info: kernel located at:
>/scratch/nilay/GEM5/system/binaries/x86_64-vmlinux-2.6.22.9
>      0: rtc: Real-time clock set to Sun Jan  1 00:00:00 2012
>Listening for com_1 connection on port 3457
>warn: Reading current count from inactive timer.
>0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
>**** REAL SIMULATION ****
>info: Entering event queue @ 0.  Starting simulation...
>panic: Packet WriteReq already has bus delay (2749, 2749) that should be
>accounted for.
> @ cycle 48000
>[calcPacketTiming:build/X86/mem/bus.cc, line 148]
>Memory Usage: 338404 KBytes
>Program aborted at cycle 48000
>Aborted (core dumped)
>
>
>--
>Nilay
>
>


-- IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium.  Thank you.

_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to