[okl4-developer] Problem with running 'l4test'

[Geoffrey Lee]

On Wed, Dec 03, 2008 at 07:09:49PM -0800, Yeonju wrote:
> 

Yeonju - you will need to apply some workarounds when running
on armv4.

Please see this:
http://wiki.ok-labs.com/forum#nabble-td1125668%7Ca1125856

and this:

http://wiki.ok-labs.com/forum#nabble-td10886%7Ca10886

	-gl

> Hi-.
> 
> I misunderstand your message.
> I think that you suggest me to repost dumped physical memory using KDB.
> 
> This is my build command line,
> 
> [root at localhost okl4_2.1]# ./tools/build.py machine=gta01 project=l4test
> 
> and I also used command option "mutex_type=user".
> 
> [root at localhost okl4_2.1]# ./tools/build.py machine=gta01 project=l4test
> mutex_type=user
> 
> I use okl4 2.1 (not fixed.7) and Fedora6.
> My target board is MBA2440 based on s3C2440.
> 
> I wonder I understand your message correctly.
> 
> Regards,
> 
> 
> 
> 
> Geoffrey Lee wrote:
> > 
> > On Tue, Dec 02, 2008 at 07:50:20PM -0800, Yeonju wrote:
> >> 
> >> Hi-.
> >> 
> >> I'm sorry to confuse you. And thank you for your help.
> >> I'm not so good at English....T-T
> >> 
> >> I built without "mutex_type=user" at first, but it didn't work. So I
> >> searched this forum for clue. 
> >> And I found a topic "S3C2440A and okl4". In that topic, you advised to
> >> buid
> >> with "mutex_type=user".
> >> After I read that, I built with "muetex_type=user". But it also didn't
> >> work.
> >> 
> >> I still find a soultion. Please help me.
> > 
> > 
> > Just so that I understand your problem correctly, could you please
> > re-post the exact build command line that you used to build your
> > image, as well as the resulting output?  In addition, are you 
> > running this on hardware or simulator?
> > 
> > 
> >> 
> >> Regards,
> >> 
> > 
> > 	-gl
> > 
> >> 
> >> 
> >> Geoffrey Lee wrote:
> >> > 
> >> > On Tue, Dec 02, 2008 at 05:34:35PM -0800, Yeonju wrote:
> >> >> 
> >> >> Hi~.
> >> > 
> >> > 
> >> > Hi - to make sure I understand correctly, do you mean that
> >> > if you build with mutex_type=user, then l4test will run
> >> > successfully to completion?  Please note that l4test
> >> > must be run with mutex_type=user, if you run it under
> >> > a different configuration it may not work.
> >> > 
> >> > 	-gl
> >> > 
> >> >> 
> >> >> I have a question about 'l4test'.
> >> >> I succeeded to run example in okl4_2.1/iguana on s3c2440 (ARM920T). 
> >> >> So, I've tried running 'l4test'(in okl4_2.1/l4test), but I failed.
> >> >> 
> >> >> I buit 'l4test' like this.
> >> >> 
> >> >> >./tools/build.py machine=gta01 project=l4test
> >> >> Binary image was made successful. 
> >> >> But, after load that image on board, I  saw  fourth case.
> >> >> Fisrt case is "Nothing happen".
> >> >> There is only one message.
> >> >> 
> >> >> OKL4 - (provider: Open Kernel Labs) built on Dec 4 2008 07:55:18 using
> >> >> gcc
> >> >> ver.
> >> >> Second case is "L4_Rootserver abort".
> >> >> 
> >> >> OKL4 - (provider: Open Kernel Labs) built on Dec 4 2008 07:55:18 using
> >> >> gcc
> >> >> ver.
> >> >> bootinfo: max space = 256, mac mutex = 256, phys [0x30700000,
> >> 0x33ffffff)
> >> >> Thread Delete failed, ErrorCode = 2
> >> >> Assertion failed: r ==1, function deleteThread, file
> >> >> l4test/src/utility.c,
> >> >> lin.
> >> >> -KD# User: L4_Rootserver abort()ed-
> >> >> >
> >> >> Third case is "Roottask pagefault"
> >> >> 
> >> >> OKL4 - (provider: Open Kernel Labs) built on Dec 4 2008 07:55:18 using
> >> >> gcc
> >> >> ver.
> >> >> bootinfo: max space = 256, mac mutex = 256, phys [0x30700000,
> >> 0x33ffffff)
> >> >> roottask read pagefault at 00bae664, ip=0012a5a0 - deny
> >> >> -KD# roottask pagefault-
> >> >> >
> >> >> Fourth case is "success".
> >> >> All l4test suite was success. 
> >> >> I fixed console.cc(in platform/s3c2410/pistachip/kdb), traps.spp(in
> >> >> /arch/arm/pistachio/v5/src) and machine.py(in /arch/arm/tools) for
> >> >> s3c2440.
> >> >> And also I tried to build 'l4test' like this.
> >> >> 
> >> >> >./tools/build.py machine=gta01 project=l4test mutex_type=user
> >> >> How can I run 'l4test' successful? 
> >> >> Regards,
> >> >> -- 
> >> >> View this message in context:
> >> >>
> >> http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1607028.html
> >> >> Sent from the OKL4 Community Forum mailing list archive at Nabble.com.
> >> > 
> >> >> _______________________________________________
> >> >> Developer mailing list
> >> >> Developer at okl4.org
> >> >> https://lists.okl4.org/mailman/listinfo/developer
> >> > 
> >> > 
> >> > -- 
> >> > 
> >> > 
> >> > _______________________________________________
> >> > Developer mailing list
> >> > Developer at okl4.org
> >> > https://lists.okl4.org/mailman/listinfo/developer
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context:
> >> http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1607438.html
> >> Sent from the OKL4 Community Forum mailing list archive at Nabble.com.
> >> 
> >> 
> >> _______________________________________________
> >> Developer mailing list
> >> Developer at okl4.org
> >> https://lists.okl4.org/mailman/listinfo/developer
> >> 
> > 
> > -- 
> > 
> > 
> > _______________________________________________
> > Developer mailing list
> > Developer at okl4.org
> > https://lists.okl4.org/mailman/listinfo/developer
> > 
> > 
> 
> -- 
> View this message in context: http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1611958.html
> Sent from the OKL4 Community Forum mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 

--