From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28898 invoked by alias); 16 May 2005 06:21:08 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 28876 invoked from network); 16 May 2005 06:21:05 -0000 Received: from unknown (HELO ns1.nec.com.au) (147.76.180.1) by sourceware.org with SMTP; 16 May 2005 06:21:05 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by ns1.nec.com.au (Postfix) with ESMTP id 8A6103785F for ; Mon, 16 May 2005 16:21:03 +1000 (EST) Received: from ns1.nec.com.au ([127.0.0.1]) by localhost (ns1.nec.com.au [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 15979-01-56 for ; Mon, 16 May 2005 16:21:03 +1000 (EST) Received: from smtp2.nec.com.au (smtp2.internal.nec.com.au [172.31.8.19]) by ns1.nec.com.au (Postfix) with ESMTP id 71F7A377A1 for ; Mon, 16 May 2005 16:21:03 +1000 (EST) Received: from deer.dd.nec.com.au (localhost.localdomain [127.0.0.1]) by smtp2.nec.com.au (8.12.8/8.12.8) with ESMTP id j4G6L3I2021892 for ; Mon, 16 May 2005 16:21:03 +1000 Received: from dvalin.dd.nec.com.au ([172.31.20.70]) by deer.dd.nec.com.au (8.12.5/8.12.5/Debian-1) with ESMTP id j4G6L2l0011853 for ; Mon, 16 May 2005 16:21:03 +1000 Received: from dvalin.dd.nec.com.au (localhost [127.0.0.1]) by dvalin.dd.nec.com.au (8.12.3/8.12.3/Debian-5) with ESMTP id j4G6K1di004121 for ; Mon, 16 May 2005 16:20:01 +1000 Received: (from erik@localhost) by dvalin.dd.nec.com.au (8.12.3/8.12.3/Debian-5) id j4G6K0Rq004100 for ecos-discuss@ecos.sourceware.org; Mon, 16 May 2005 16:20:00 +1000 From: Erik Christiansen Date: Mon, 16 May 2005 10:09:00 -0000 To: ecos-discuss@ecos.sourceware.org Message-ID: <20050516062000.GA868@dd.nec.com.au> References: <42882BFB.3020909@elands.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42882BFB.3020909@elands.co.nz> User-Agent: Mutt/1.5.6+20040722i Subject: [ECOS] "!!!-- Configuration broken - no scheduler selected --!!!" X-SW-Source: 2005-05/txt/msg00203.txt.bz2 That straighforward error message occurs several times, deep in my ecos.ecc, but is CYGSEM_KERNEL_SCHED_MLQUEUE not enabled here?: cdl_component CYGSEM_KERNEL_SCHED_MLQUEUE { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: 1 # The following properties are affected by this value # option CYGPRI_KERNEL_SCHED_IMPL_HXX # Calculated: CYGSEM_KERNEL_SCHED_BITMAP ? "" : CYGSEM_KERNEL_SCHED_MLQUEUE ? "" : CYGSEM_KERNEL_SCHED_LOTTERY ? "" : "!!!-- Configuration broken - no scheduler selected --!!!" # component CYGSEM_KERNEL_SYNCH_MUTEX_PRIORITY_INVERSION_PROTOCOL # ActiveIf: CYGSEM_KERNEL_SCHED_MLQUEUE # option CYGIMP_UITRON_STRICT_CONFORMANCE # Requires: CYGSEM_KERNEL_SCHED_MLQUEUE }; cdl_option CYGSEM_KERNEL_SCHED_BITMAP { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 0 # value_source default # Default value: 0 # Requires: !CYGPKG_KERNEL_SMP_SUPPORT # CYGPKG_KERNEL_SMP_SUPPORT == 0 # --> 1 # The following properties are affected by this value # option CYGPRI_KERNEL_SCHED_IMPL_HXX # Calculated: CYGSEM_KERNEL_SCHED_BITMAP ? "" : CYGSEM_KERNEL_SCHED_MLQUEUE ? "" : CYGSEM_KERNEL_SCHED_LOTTERY ? "" : "!!!-- Configuration broken - no scheduler selected --!!!" # component CYGSEM_KERNEL_SCHED_TIMESLICE # Requires: !CYGSEM_KERNEL_SCHED_BITMAP }; Since ecosconfig thinks that the configuration is OK; $ ecosconfig check Adder Template: kernel Added: CYGPKG_UITRON Removed: CYGPKG_IO_SERIAL CYGPKG_HAL_QUICC CYGPKG_IO_SERIAL_POWERPC_QUICC_SMC No conflicts and the code built from this does schedule threads, I'm led to infer that CYGSEM_KERNEL_SCHED_MLQUEUE is active by default. But then the configuration is not broken!? No benefit is obtained from trying: a) Uncommenting the "# user_value 1" in CYGSEM_KERNEL_SCHED_MLQUEUE b) ecosconfig add CYGSEM_KERNEL_SCHED_MLQUEUE c) ecosconfig remove CYGPKG_UITRON Is there some other measure that can make this situation less scary? Erik -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss