From: Paul Fulghum <paulkf@microgate.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Hinds <dahinds@users.sourceforge.net>
Subject: Re: PCMCIA 2.5.X sleeping from illegal context
Date: 13 May 2003 10:23:05 -0500 [thread overview]
Message-ID: <1052839384.2255.10.camel@diemos> (raw)
In-Reply-To: <20030512234828.C17227@flint.arm.linux.org.uk>
On Mon, 2003-05-12 at 17:48, Russell King wrote:
> On Mon, May 12, 2003 at 07:36:05AM -0500, Paul Fulghum wrote:
> > On Mon, 2003-05-12 at 16:07, Alan Cox wrote:
> > > On Llu, 2003-05-12 at 22:35, Paul Fulghum wrote:
> > > > The 2.5.X PCMCIA kernel support seems to have a problem
> > > > with drivers/pcmcia/rsrc_mgr.c in function undo_irq().
> > >
> > > Does this still happen with all the patches Russell King posted
> > > that everyone else is ignoring ?
> >
> > I don't know, I've been ignoring them :-)
> >
> > Seriously, are they centralized someplace or
> > should I scan back and try to extract them
> > from the lk archive? Do you know about when
> > they were posted?
>
> Try this one. Its a slightly updated version from the one I sent earlier.
I tested this patch, and it works.
But I was not seeing any problems before the patch,
other than the 'sleeping in illegal context message'
There seems to be agreement that the cause of the
message is that individual PCMCIA drivers need to be
modified to call the release function directly
instead of from a timer context.
I modified my synclink_cs driver to do this and it
works and eliminates the error message.
Which brings up a question:
The include/pcmcia/ds.h file defines the dev_link_t
structure that contains the release timer_list member.
Should I continue to initialize this member in
my driver or will this member be eliminated requiring
that all references to this member be removed from
the individual PCMCIA drivers?
--
Paul Fulghum, paulkf@microgate.com
Microgate Corporation, http://www.microgate.com
next prev parent reply other threads:[~2003-05-13 15:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 21:35 PCMCIA 2.5.X sleeping from illegal context Paul Fulghum
2003-05-12 21:07 ` Alan Cox
2003-05-12 12:36 ` Paul Fulghum
2003-05-12 22:48 ` Russell King
2003-05-13 15:23 ` Paul Fulghum [this message]
2003-05-13 16:00 ` David Hinds
2003-05-12 22:31 ` Russell King
2003-05-12 23:16 ` Felipe Alfaro Solana
2003-05-12 23:36 ` Richard B. Johnson
2003-05-12 23:52 ` Paul Fulghum
2003-05-13 13:37 ` Alan Cox
2003-05-13 23:33 ` Andrew Morton
2003-05-14 13:25 ` Henning P. Schmiedehausen
2003-05-13 2:07 ` Thomas Molina
2003-05-13 0:36 ` Felipe Alfaro Solana
2003-05-12 23:11 ` Felipe Alfaro Solana
2003-05-12 22:06 ` David Hinds
2003-05-12 12:37 ` Paul Fulghum
2003-05-12 22:44 ` Andrew Morton
2003-05-12 23:10 ` David Hinds
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=1052839384.2255.10.camel@diemos \
--to=paulkf@microgate.com \
--cc=dahinds@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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