From: "Adrian McMenamin" <lkmladrian@gmail.com>
To: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
Cc: linux-kernel@vger.kernel.org, linuxsh-dev@lists.sourceforge.net
Subject: Re: Race in setup_irq?
Date: Sun, 11 Nov 2007 21:21:01 +0000 [thread overview]
Message-ID: <8b67d60711111321j293a0a81r41cf4c604f47932c@mail.gmail.com> (raw)
In-Reply-To: <b647ffbd0711111311x4e35f854g3ecfb8f07748d934@mail.gmail.com>
On 11/11/2007, Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> On 11/11/2007, Adrian McMenamin <lkmladrian@gmail.com> wrote
> > I am writing a device driver for the Dreamcast CD Drive (the "GD Rom")
> > and I am hitting what looks like some sort of race in
> > kernel/irq/manage.c. Can anybody point me in the right direction or is
> > there a bug here?
> >
> > This never seems to return in setup_irq:
> >
> > spin_unlock_irqrestore(&desc->lock, flags);
> >
> > (line 597)
>
> I guess, you are referring to setup_irq() (the line without a
> particular kernel version doesn't make much sense).
>
Sorry, it was in the config: 2.6.24-rc2
> What do you mean by "never seems to return"? Does your machine hang?
>
> If so, the reason might be some kind of (logical) error in your ISR.
> spin_unlock_irqrestore() unmasks the interrupts and your target device
> might have already generated an interrupt by this moment (sure, it
> depends on the initialization logic of your code and device spec.)...
> --> ISR runs and due to some error e.g. loops endlessly/deadlocks/etc.
>
> Tried placing printk() at the beginning of ISR?
>
You are absolutely right. Sorry for wasting evetybody's time and
thanks for the tip!
prev parent reply other threads:[~2007-11-11 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 19:52 Adrian McMenamin
2007-11-11 21:11 ` Dmitry Adamushko
2007-11-11 21:21 ` Adrian McMenamin [this message]
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=8b67d60711111321j293a0a81r41cf4c604f47932c@mail.gmail.com \
--to=lkmladrian@gmail.com \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®