From: Derrick J Brashear <shadow@DEMENTIA.ORG>
To: ultralinux@vger.kernel.org
Subject: Re: sparc32 2.1.121 problems
Date: Sun, 18 Oct 1998 04:47:55 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90870069522231@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90682217607462@msgid-missing>
On Sat, 26 Sep 1998, Derrick J Brashear wrote:
> also, i saw someone complaining of it about their PC on linux-kernel, so
> this may not be any of us, but Brent complained when he was testing that
> the dbri module usage went negative, and that it appeared the release
> function was called a few times when it shouldn't have been, apparently
> when the fd referring to the audio device was dup'd and then the parent
> closed it's copy. i've observed that, but haven't yet been able to come up
Now, I can reproduce the negative module use count.
[root@panaphonics ~]# lsmod
Module Size Used by
amd7930 7872 0 (unused)
audio 9252 1 [amd7930]
autofs 9432 1 (autoclean)
[root@panaphonics ~]# cat /usr/tmp/eclipse.au > /dev/audio
[root@panaphonics ~]# lsmod
Module Size Used by
amd7930 7872 -2
audio 9252 -1 [amd7930]
autofs 9432 1 (autoclean)
I had instrumented the audio module, and I see:
Oct 18 00:41:54 panaphonics kernel: increasing module use in register
Oct 18 00:41:54 panaphonics kernel: amd7930 at 0xfd017000 irq 61
Oct 18 00:42:39 panaphonics kernel: increasing module use in open for 4
Oct 18 00:42:39 panaphonics kernel: decreasing module use in release
Oct 18 00:42:45 panaphonics last message repeated 2 times
So release is apparently being called too often. Am I supposed to be doing
something in release to make sure it's not being called bogusly, or is
something else broken?
(Of course, now I can't unload the damn module either)
-D
prev parent reply other threads:[~1998-10-18 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-26 15:05 sparc32 2.1.121 problems Derrick J Brashear
1998-09-27 5:24 ` Derrick J Brashear
1998-10-18 4:47 ` Derrick J Brashear [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=marc-linux-ultrasparc-90870069522231@msgid-missing \
--to=shadow@dementia.org \
--cc=ultralinux@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.