[okl4-developer] [OKL2.1]spurious exception as soon as OKlinux forks init.

[Dennis Gessner]

Geoffrey Lee schrieb:
> On Mon, Sep 29, 2008 at 05:16:26AM -0700, Amit Daniel wrote:
>> Dear All,
>>
>> I have tested some test examples with okl microkernel and iguana. They works
>> fine.
>> But when i try executing OKLinux as an application, spurious exception
>> starts coming. I am building the image file as,
>> tools/build.py machine=gta01 project=iguana wombat=True
>> enable_fastpaths=False
>> This exception is coming as soon kernel tries to fork the /sbin/init
>> process. I tried to put some print in main interrupt handler but those
>> prints are not coming. so, the exception source is not clear.
>>
> 
> Hi Amit
> 
> The exception handler for Linux processes is the syscall_loop(), not
> interrupt_loop(), which I think may be what is confusing you.
> 
> Also, have you made any modifications to either the OKL4 or the OK Linux
> distribution in any way?  If so what have you changed?
> 
>         -gl
> 

Hi Geoffrey,
Hi Amit.

A few weeks ago, I also had the same problem

"unhandled user exception (0x0) @ 0 in init (1)"

with my gta01 device (enable_fastpaths=False because of the
clz-problem). I took a fresh image of "okl4 2.1.1 patch 9" with "OK
Linux 2.6.23.24" from the webpage. This version is absolutely unmodified.

Anyway I did not have time to look for a reason - right now I still work
on my vTOUCH and touchscreen-driver inside an iguana-application.
I would be very happy if you find a solution about the oklinux-problem.

Best regards
Dennis