From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Juan Quintela <quintela@mandrakesoft.com>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Andrew Morton <akpm@zip.com.au>,
kernel <kernel@linux-mandrake.com>,
linux-kernel@vger.kernel.org, dhinds@sonic.net
Subject: Re: pcmcia oops (with ksymoops output this time)
Date: Thu, 14 Mar 2002 17:51:35 -0500 [thread overview]
Message-ID: <3C912977.2030604@mandrakesoft.com> (raw)
In-Reply-To: <m2henircqz.fsf@trasno.mitica>
With oops tracing in IRC, we narrowed the problem in 2.4.x down to,
serial_cs and ide_cs drivers, and other 16-bit pcmcia drivers possibly,
call their release functions from a timer when ejected. The
per-subsystem release functions then proceed to do all manner of
in-process-context type work, including calling devfs_unregister, whose
call path can eventually cause a schedule()
Suggested fix, call schedule_task() in each timer-based release
function, to queue a task in process context to do the actual work.
This is how 32-bit cardbus gets such things done...
Jeff
parent reply other threads:[~2002-03-14 22:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m2henircqz.fsf@trasno.mitica>]
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=3C912977.2030604@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=akpm@zip.com.au \
--cc=dhinds@sonic.net \
--cc=kernel@linux-mandrake.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.com \
--cc=rgooch@ras.ucalgary.ca \
/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.