Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Instrumented kernel (PPC E500MC) causes a SIGILL in io-pkt driver : (2 Items)
   
Instrumented kernel (PPC E500MC) causes a SIGILL in io-pkt driver  
Hi,

I am trying to do the system profiling for io-pkt driver on my P4080 E500MC platform.
When I replace my kernel image from normal to Instrumented version, I see a random SIGILL on my driver while trying to 
access cached memory regions.

Process 20488 (io-pkt-v4-hc) terminated SIGILL code=1 fltno=1 ip=fe3f9300 mapaddr=00078300. ref=00000000

Debugging further on this map address in my DLL,

   78300:	7c 8c 23 78 	mr      r12,r4

Sometimes it happens on lwz instructions.

I am not sure what kind of problems in my DLL would cause only the instrumented kernel to report SIGILL and not the 
normal kernel.

# pidin info
CPU:PPC Release:6.4.2  FreeMem:2030Mb/4096Mb BootTime:Jan 01 00:00:00 UTC 1970
Processes: 8, Threads: 31
Processor1: 80230010 E500mc Core 1500MHz FPU
Processor2: 80230010 E500mc Core 1500MHz FPU
Processor3: 80230010 E500mc Core 1500MHz FPU
Processor4: 80230010 E500mc Core 1500MHz FPU
Processor5: 80230010 E500mc Core 1500MHz FPU
Processor6: 80230010 E500mc Core 1500MHz FPU
Processor7: 80230010 E500mc Core 1500MHz FPU
Processor8: 80230010 E500mc Core 1500MHz FPU


Also sometimes the crash never happens and I am happily able to generate traces.

Any kind of help would be appreciated !

BR
Akash
Re: Instrumented kernel (PPC E500MC) causes a SIGILL in io-pkt driver  
My guess: PR 74770.

On Wed, Mar 10, 2010 at 12:49:59AM -0500, Akash Goswami wrote:
> Hi,
> 
> I am trying to do the system profiling for io-pkt driver on my P4080 E500MC platform.
> When I replace my kernel image from normal to Instrumented version, I see a random SIGILL on my driver while trying to
 access cached memory regions.
> 
> Process 20488 (io-pkt-v4-hc) terminated SIGILL code=1 fltno=1 ip=fe3f9300 mapaddr=00078300. ref=00000000
> 
> Debugging further on this map address in my DLL,
> 
>    78300:	7c 8c 23 78 	mr      r12,r4
> 
> Sometimes it happens on lwz instructions.
> 
> I am not sure what kind of problems in my DLL would cause only the instrumented kernel to report SIGILL and not the 
normal kernel.
> 
> # pidin info
> CPU:PPC Release:6.4.2  FreeMem:2030Mb/4096Mb BootTime:Jan 01 00:00:00 UTC 1970
> Processes: 8, Threads: 31
> Processor1: 80230010 E500mc Core 1500MHz FPU
> Processor2: 80230010 E500mc Core 1500MHz FPU
> Processor3: 80230010 E500mc Core 1500MHz FPU
> Processor4: 80230010 E500mc Core 1500MHz FPU
> Processor5: 80230010 E500mc Core 1500MHz FPU
> Processor6: 80230010 E500mc Core 1500MHz FPU
> Processor7: 80230010 E500mc Core 1500MHz FPU
> Processor8: 80230010 E500mc Core 1500MHz FPU
> 
> 
> Also sometimes the crash never happens and I am happily able to generate traces.
> 
> Any kind of help would be appreciated !
> 
> BR
> Akash
> 
> 
> 
> _______________________________________________
> 
> OSTech
> http://community.qnx.com/sf/go/post49142
> 

-- 
Brian Stecher (bstecher@qnx.com)        QNX Software Systems
phone: +1 (613) 591-0931 (voice)        175 Terence Matthews Cr.
       +1 (613) 591-3579 (fax)          Kanata, Ontario, Canada K2M 1W8