From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4402 invoked by alias); 7 Sep 2009 16:10:02 -0000 Received: (qmail 4344 invoked by uid 22791); 7 Sep 2009 16:10:01 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from n26.bullet.mail.ukl.yahoo.com (HELO n26.bullet.mail.ukl.yahoo.com) (87.248.110.143) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Mon, 07 Sep 2009 16:09:51 +0000 Received: from [217.146.182.179] by n26.bullet.mail.ukl.yahoo.com with NNFMP; 07 Sep 2009 16:09:47 -0000 Received: from [87.248.110.117] by t5.bullet.ukl.yahoo.com with NNFMP; 07 Sep 2009 16:09:48 -0000 Received: from [127.0.0.1] by omp222.mail.ukl.yahoo.com with NNFMP; 07 Sep 2009 16:09:48 -0000 Received: (qmail 50208 invoked by uid 60001); 7 Sep 2009 16:02:25 -0000 Message-ID: <110701.39566.qm@web87005.mail.ird.yahoo.com> Received: from [217.33.179.85] by web87005.mail.ird.yahoo.com via HTTP; Mon, 07 Sep 2009 16:02:25 GMT References: <3100D422DF3A4D7B9D337FD86D646F40@masahiro> <4A65D8D3.9060400@dallaway.org.uk> <3F8ED0BDC83C43259ADD0DDE963395DF@masahiro> <4A671AEE.2000101@dallaway.org.uk> <407D126036C3460AB7AA0264475F04E0@masahiro> <4A6971F2.1030100@dallaway.org.uk> <095F57A600314F7E86F6731FCC889A3D@masahiro> <87D23C72FA344A339A61EA9D3E333467@masahiro> <4AA0DFEB.2020800@dallaway.org.uk> <5D7EE4D955F443C7946FC40DB7EE93C1@masahiro> <4AA4EE58.2050100@dallaway.org.uk> Date: Mon, 07 Sep 2009 16:10:00 -0000 From: Jim Bradleigh To: ecos-discuss@ecos.sourceware.org In-Reply-To: <4AA4EE58.2050100@dallaway.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] cyg_scheduler_lock and DSR's X-SW-Source: 2009-09/txt/msg00070.txt.bz2 Hi, Is the cyg_scheduler_lock() call not supposed to prevent DSR's from running? I have a alarm, attached to the realtime clock which when activated posts a= message to a custom queue system. This queue is also posted to by user lan= d code.. Pushes to the queue are protected by a mutex. Additionally around the mutex= I have the cyg_scheduler_lock() and cyg_scheduler_unlock() to prevent the = DSR posting a message whilst inside the mutex operation. However I`m seeing asserts stating the mutex is already locked. A quick bre= akpoint and I can see that the DSR is still being called even after the loc= k() function.. Any thoughts? James -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss