public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Seifert <lathander-Mmb7MZpHnFY@public.gmane.org>
To: "Moore, Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Grover,
	Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Therien,
	Guy" <guy.therien-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: mutexes and preemption
Date: Thu, 4 Mar 2004 11:22:12 +0100	[thread overview]
Message-ID: <20040304102212.GA2303@ergo.gotdns.org> (raw)
In-Reply-To: <CFF522B18982EA4481D3A3E23B83141C01C988CE-sBd4vmA9Se6SsB6bSF6DdVDQ4js95KgL@public.gmane.org>

On Wed, Mar 03, 2004 at 05:08:53PM -0800, Moore, Robert wrote:
> 
> Looking at the timestamps in the debug output, I suspect that the real
> issue here is this line:
> 
> Mar  2 23:03:10 tenshi kernel:      osl-0909 [2049] os_wait_semaphore
> : Failed to acquire semaphore[dffd8680|1|36863], AE_TIME
> 
> Because this wait should have been for 37 seconds (36863 milliseconds),
> yet not one second has gone by on the wall clock.
> 
> A close look at the Linux implementation of os_wait_semaphore may again
> be in order.

You are right, thank you. I believe there is a  bug in
os_wait_semaphore: the return value of down_trylock isn't checked
correctly, leading to the immediate failure of an Acquire with timeout
in the case the semaphore cannot be acquired immediately . I've sent a
patch to this list. I hope someone applies it.

Sebastian

-- 
A bad analogy is like leaky screwdriver.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  parent reply	other threads:[~2004-03-04 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  1:08 mutexes and preemption Moore, Robert
     [not found] ` <CFF522B18982EA4481D3A3E23B83141C01C988CE-sBd4vmA9Se6SsB6bSF6DdVDQ4js95KgL@public.gmane.org>
2004-03-04 10:22   ` Sebastian Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-03 23:59 Moore, Robert
2004-03-03  7:05 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB713-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-03-03  7:24   ` Sebastian Seifert
2004-03-02 22:51 Sebastian Seifert
     [not found] ` <20040302225117.GA1660-nlVyBo/8EO9N0TnZuCh8vA@public.gmane.org>
2004-03-03 11:43   ` Sebastian Seifert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040304102212.GA2303@ergo.gotdns.org \
    --to=lathander-mmb7mzphnfy@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=guy.therien-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox