[okl4-developer] My arm926ejs port of l4test: L4_Lock() fails

Geoffrey Lee glee at ok-labs.com
Wed Jul 30 13:27:07 EST 2008


On Wed, Jul 30, 2008 at 11:16:38AM +0800, Charles Chiou wrote:
> Hi Geoffrey,
> 
> I'm not pasing mutex_type to command line.


Could you please set mutex_type to "user" and retry.

	-gl

> 
> Charles
> 
> 
> 
> On 7/30/08 11:14 AM, "Geoffrey Lee" <glee at ok-labs.com> wrote:
> 
> > On Wed, Jul 30, 2008 at 11:10:05AM +0800, Charles Chiou wrote:
> >> Hi,
> >> 
> >> I'm failing on mostly the L4_Lock() calls with my port of pistachio running
> >> l4test. I couldn't find similar cases in mail list archive. Can someone
> >> point out where I might have done wrong? Thank you.
> > 
> > 
> > Which mutex_type are you passing into the command line (feel free
> > to say none if you are not doing that.)?
> > 
> > -gl
> > 
> >> 
> >> --
> >> Initializing interrupts...
> >> System running with alignment exceptions enabled
> >> Processor Id => 41069265: v5TEJ, ARM926, rev 5
> >> Initializing timer...
> >> TLB lock: vectors @ ffff0000
> >> TLB lock: utcb @ ff000000
> >> TLB lock: kernel @ f0000000
> >> Locked kernel into TLB
> >> Init mutexids for 256 mutexs
> >> Init clistids for 16 clists
> >> domain pairs: (0, 1)
> >> Initialising scheduler...
> >> Switching to idle thread
> >> Initializing root servers
> >> root-servers: utcb_area: dff00100 (64KB)
> >> creating root server (00000001)
> >> bootinfo: max space = 256, max mutex = 256, phys [0xc0700000, 0xc0ffffff)
> >> Running suite(s): L4 Test suite
> >> KDB0100         
> >> ...
> >> MUTEX0400       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0401       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0402       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0403       
> >> MUTEX0405       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0406       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0407       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0500       
> >> MUTEX0501       
> >> *** Failure: Wrong error code
> >> MUTEX0600       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0700       
> >> *** Failure: L4_Lock() failed
> >> MUTEX0705       
> >> ...
> >> MUTEXSI0100     
> >> *** Failure: L4_Lock() failed
> >> MUTEXSI0200     
> >> *** Failure: L4_CreateMutex() failed
> >> MUTEXSI0201     
> >> *** Failure: L4_CreateMutex() failed
> >> MUTEXSI0300     
> >> *** Failure: L4_CreateMutex() failed
> >> MUTEXSI0301     
> >> *** Failure: L4_CreateMutex() failed
> >> MUTEXSI0400     
> >> *** Failure: Failed to create mutexes.
> >> SIGRAPH0100     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0200     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0201     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0202     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0203     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0204     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0205     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0206     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0207     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0208     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0300     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0301     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0302     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0303     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0304     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0305     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0306     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0400     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0401     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0500     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0501     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0502     
> >> *** Failure: L4_Lock() failed
> >> SIGRAPH0503     
> >> *** Failure: L4_Lock() failed
> >> ...
> >> l4test/src/remotememcpy.c:473:P:Remote Memory Copy:RMC0500: Passed
> >> 90%: Checks: 408, Failures: 40, Errors: 0
> >> --- KD# User: L4Test Done ---
> >> 
> >> Charles
> >> 
> >> 
> >> _______________________________________________
> >> Developer mailing list
> >> Developer at okl4.org
> >> https://lists.okl4.org/mailman/listinfo/developer
> >> 
> 
> 

-- 




More information about the Developer mailing list