From: Matthieu Herrb <matthieu.herrb@laas.fr>
To: linux-kernel@vger.kernel.org
Subject: rocketport driver problems in 2.6.10
Date: Mon, 21 Feb 2005 17:42:08 +0100 [thread overview]
Message-ID: <421A0F60.60005@laas.fr> (raw)
Hi,
I'm experimenting problems with the rocket driver with a Comtrol
Rocketprot ISA board, under Fedora Core 3 with a 2.6.10 kernel.
(Linux dala 2.6.10-1.766_FC3 #1 Wed Feb 9 23:06:42 EST 2005 i686 i686
i386 GNU/Linux)
I have a multi-threaded application that opens 2 ports on the rocketport
card, and happily talks to both devices connected to these ports.
But when I quit the application, the close on the last port leaves the
thread that called close() and the rocket kernel module in a strange
state: the thread changes between 'D' state with a wait channel of
'release_dev' and running. It can't be killed. Lsof doesn't show the
device as open anymore. Any try to open the device again fails with
errno == EIO.
lsmod shows the kernel module used by 1 client, and I can't rmmod it.
Only a reboot can free the device and let me work further.
When I only use one device on the rocketport per process, everything is
ok (or seems ok).
Any idea(s) on how to debug/fix that ?
--
Matthieu Herrb
reply other threads:[~2005-02-21 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=421A0F60.60005@laas.fr \
--to=matthieu.herrb@laas.fr \
--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.