From: James Hansen <linux-kernel-list@f0rmula.com>
To: linux-kernel-list <linux-kernel@vger.kernel.org>
Subject: Trouble unloading a module..
Date: Mon, 31 Oct 2005 16:49:53 +0000 [thread overview]
Message-ID: <43664B31.3000305@f0rmula.com> (raw)
I've having trouble unloading a kernel module for a PCI card that I'm
porting to 64bit linux. It doesn't seem to be unloading correctly.
It's tested, stable and unloads perfectly on a 32bit machine, running
2.6.10 (and all other 32bit kernels I've tried).
However, on a 64bit machine (unofficial amd/emt64 debian with 2.6.8),
even though it seems to unload corrrectly, I get a kernel oops if an
application that uses the driver attempts to connect to the device after
it's been unloaded.
Being relatively inexperienced at kernel programming, does this point to
anything that might be obvious to any of you, yet not to me? :) Or are
there any common stumbling blocks in terms of unloading modules on 64bit
linux.
Thanks for any suggestions.
James
next reply other threads:[~2005-10-31 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 16:49 James Hansen [this message]
2005-11-02 8:11 ` Trouble unloading a module Arjan van de Ven
2005-11-02 12:13 ` James Hansen
2005-11-02 12:39 ` Arjan van de Ven
2005-11-03 11:58 ` James Hansen
[not found] <53LbV-6pW-21@gated-at.bofh.it>
2005-11-01 3:56 ` Robert Hancock
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=43664B31.3000305@f0rmula.com \
--to=linux-kernel-list@f0rmula.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox