I've seen this bug pop up before, but it's been hard to track down. Some how a 
load ends up getting executed that is uncachable and not at the head of the 
ROB. Exactly what conditions lead to this isn't clear from the code and I 
haven't found the behavior to be particularly repeatable to be able to debug 
it. 

Ali


On May 29, 2013, at 3:06 AM, huangyongbing <huangyongb...@ncic.ac.cn> wrote:

> Hi Andreas,
>  
>          I am running map and office applications on a modified disk image. I 
> only modify the cache policy of gem5. The version of Linux kernel is 2.6.35 
> and I just modify the size of vncview.
>  
>          It is difficult to reproduce the panic. The panic may no longer 
> exist when I rerun the simulator using the same configuration.
>  
>          Thanks.
>  
> Best regards,
> Yongbing Huang
>  
>  
> From: gem5-users-boun...@gem5.org [mailto:gem5-users-boun...@gem5.org] On 
> Behalf Of Andreas Hansson
> Sent: Wednesday, May 29, 2013 3:28 PM
> To: gem5 users mailing list
> Subject: Re: [gem5-users] panic: Uncachable load
>  
> Hi Yongbing,
>  
> Could you elaborate a bit on what you are running? For example, is this on an 
> unmodified trunk? If so, how to reproduce it?
>  
> Thanks,
>  
> Andreas
>  
> From: huangyongbing <huangyongb...@ncic.ac.cn>
> Reply-To: gem5 users mailing list <gem5-users@gem5.org>
> Date: Wednesday, 29 May 2013 07:48
> To: "gem5-users@gem5.org" <gem5-users@gem5.org>
> Subject: [gem5-users] panic: Uncachable load
>  
> Hi all,
>  
>          I run the simulator using the arm_detailed CPU model while 
> simulating the ARM platform. However, the bellowing panic will occur 
> sometimes:
>  
> panic: Uncachable load [sn:4af0382b] PC (0xc016b5c0=>0xc016b5c4).(0=>1)       
>    (PC is different for different times, but PCs are often like 0xc016b5xx)
> @ cycle 611133741299620
> [invoke:build/ARM/arch/generic/debugfaults.hh, line 94]
>  
>          The source codes of above panic are contained in the file 
> cpu/o3/lsq_unit.hh:
>                    LSQUnit::read()
>                    {
>              if (req->isUncacheable() && (load_idx != loadHead || 
> !load_inst->isAtCommit())) {
>                                      …
>                                      Panic(…);
>                    }
>          }
>  
> The pc shows this is the instruction of Linux kernel. So are they any ideas 
> about the reason?
>  
> Thanks.
>  
> Best regards,
>  
> Yongbing Huang
>  
> 
> -- 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-users mailing list
> 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

Reply via email to