From: Xuebing Wang <xbing6@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: "; Libin Yang" <libin.yang@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"; Takashi Iwai" <tiwai@suse.de>,
"; Mengdong Lin" <mengdong.lin@intel.com>,
Clemens Ladisch <clemens@ladisch.de>,
Anssi Hannula <anssi.hannula@iki.fi>,
"; Fengguang Wu" <fengguang.wu@intel.com>
Subject: Re: Can not rmmod snd_hda_codec_hdmi
Date: Wed, 24 Dec 2014 21:27:40 +0800 [thread overview]
Message-ID: <1419427660.2226.4.camel@gmail.com> (raw)
In-Reply-To: <549ABDC4.7010901@sakamocchi.jp>
On Wed, 2014-12-24 at 22:21 +0900, Takashi Sakamoto wrote:
> On Dec 24 2014 22:07, Xuebing Wang wrote:
> > 2) However, in Fedora, 'pulseaudio --kill' or your way can get refcount
> > of snd_hda_intel from 7 to 2 (5 decreased). Any suggestions how to
> > decrease the rest 2 refcount?
> >
> > 3) I did try to build tag 3.13 from mainline kernel (using Fedora 3.17.4
> > config file) and tried 3.13 kernel on Fedora, and got the same result
> > (refcount of snd_hda_intel is down from 7 to 2).
>
> Hm. In this case that the refcount is down to 2, how is the output of
> 'fuser' command? If any applications use these character devices, we can
> see the name of command.
Sakamoto-san, thanks for your help.
I found out that it is alsactl in Fedora. After kill alsactl, refcnt is
now down to 0, and both snd_hda_intel and snd_hda_codec_hdmi can be
rmmod'ed. 'fuser -v /dev/snd' does not reveal alsactl.
Thanks again.
> Regards
>
> Takashi Sakamoto
> o-takashi@sakamocchi.jp
>
next prev parent reply other threads:[~2014-12-24 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 11:07 Can not rmmod snd_hda_codec_hdmi Xuebing Wang
2014-12-23 16:21 ` Clemens Ladisch
2014-12-24 9:49 ` Xuebing Wang
2014-12-24 9:57 ` Anssi Hannula
2014-12-24 11:54 ` Xuebing Wang
2014-12-24 12:28 ` Takashi Sakamoto
2014-12-24 13:07 ` Xuebing Wang
2014-12-24 13:21 ` Takashi Sakamoto
2014-12-24 13:27 ` Xuebing Wang [this message]
2014-12-24 19:02 ` Jaroslav Kysela
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=1419427660.2226.4.camel@gmail.com \
--to=xbing6@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=anssi.hannula@iki.fi \
--cc=clemens@ladisch.de \
--cc=fengguang.wu@intel.com \
--cc=libin.yang@intel.com \
--cc=mengdong.lin@intel.com \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.de \
/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