Hi all,
I am posting as a follow up of this thread 
(http://www.mail-archive.com/gem5-users%40gem5.org/msg10489.html). I was having 
a bad page error when running X86 FS with more than one O3 cpu. I switched to 
Ruby memory model (with MOESI_hammer protocol), successfully created a 
checkpoint and restored from the checkpoint and switched to detailed cpu 
afterwards. I use the linux version linux-2.6.22.9-smp. However, I realized 
that the bad page error still continues for the detailed cpu as posted below:
….
[HOOKS] Entering ROI
Bad page state in process 'blackscholes'
page:ffffffff80721d68 flags:0x0000000000000000 mapping:000000baffffffff 
mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Unable to handle kernel paging request at 0000000000100100 RIP: 
 [<ffffffff8025d9f9>] get_page_from_freelist+0x139/0x430
PGD 3f5a2067 PUD 3f5ee067 PMD 0 
Oops: 0000 [1] SMP 
CPU 0 
Modules linked in:
Pid: 809, comm: blackscholes Not tainted 2.6.22 #1
RIP: 0010:[<ffffffff8025d9f9>]  [<ffffffff8025d9f9>] 
get_page_from_freelist+0x139/0x430
RSP: 0000:ffff81003e991c58  EFLAGS: 0000003c
RAX: 0000000000000080 RBX: ffffffff80721d00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff80721d00
RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000003ca7c
R10: 0000000000000001 R11: 00002b7b5e738100 R12: 00000000001000d8
R13: 0000000000000000 R14: 0000000000000010 R15: ffffffff80726450
FS:  00002b7b5f87b710(0000) GS:ffffffff80793000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000100100 CR3: 000000003f5b3000 CR4: 00000000000006e0
Process blackscholes (pid: 809, threadinfo ffff81003e990000, task 
ffff81003fdea9a0)
Stack:  0000000000000000 0000000000000000 000000000000026c 0000000000000000
 ffffffff80845420 00000000000280d2 0000000000000001 ffffffff80723d80
 ffffffff80726458 0000000100000000 0000000000000044 0000000000000001
Call Trace:
 [<ffffffff8025dd81>] __alloc_pages+0x91/0x350
 [<ffffffff80270884>] anon_vma_prepare+0x24/0x110
 [<ffffffff80268003>] __handle_mm_fault+0x9d3/0xcd0
 [<ffffffff805be58f>] do_page_fault+0x1af/0x900
 [<ffffffff805bc8bd>] error_exit+0x0/0x84
…..

Does this mean that it is not possible to run PARSEC on gem5 with X86 FS with 
multiple O3 cpus? I am looking forward to any feedback on this. Thanks.
Best,
Fulya

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

Reply via email to