From: Norbert Roos <n.roos@berlin.de>
To: linux-kernel@vger.kernel.org
Subject: Re: System hangs during interruptible_sleep_on_timeout() under 2.4.9
Date: Thu, 27 Sep 2001 16:58:16 +0200 [thread overview]
Message-ID: <3BB33E88.ACD1E426@berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0109261902350.6377-100000@localhost.localdomain>
Ingo Molnar wrote:
> are you sure timer interrupts are processed while you are waiting for the
> timeout to expire? I'd suggest to put a:
>
> printk("<%d>", irq);
>
> into arch/i386/kernel/irq.c:do_IRQ().
Until the call of interruptible_sleep_on_timeout(), timer interrupts
were processed. Right after the call no more output is made.
> So you can see what kind of
> interrupt traffic there is while the device initializes and you are
> waiting for it to generate an interrupt.
I use the function only for a short delay (switch on the device's reset,
wait and switch it off again), so the device even does not generate a
PCI interrupt.
In the time inbetween I have traced the problem: Inside the sleep_on()
functions there is the macro SLEEP_ON_HEAD containing the call
wq_write_lock_irqsave(), where the error happens. This is a macro, too,
which at last expands to
__asm__ __volatile__("pushfl ; popl %0":"=g" (x): /* no input */)
(x ist the variable where the IRQ flags are stored)
I'm not familiar with x86 assembler; is it possible that something can
go wrong here?
bye, Norbert
next prev parent reply other threads:[~2001-09-27 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 16:58 System hangs during interruptible_sleep_on_timeout() under 2.4.9 Norbert Roos
2001-09-26 17:05 ` Ingo Molnar
2001-09-26 18:59 ` Russell King
2001-09-26 19:27 ` Ingo Molnar
2001-09-27 14:58 ` Norbert Roos [this message]
2001-09-27 15:37 ` Richard B. Johnson
2001-10-01 16:39 ` george anzinger
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=3BB33E88.ACD1E426@berlin.de \
--to=n.roos@berlin.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.