[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#812593: marked as done (linux-base: saa7134_alsa won't unload, reported in use by kernel)

Your message dated Mon, 25 Jan 2016 14:52:10 +0000
with message-id <1453733530.3734.208.camel@decadent.org.uk>
and subject line Re: Bug#812593: linux-base: saa7134_alsa won't unload, reported in use by kernel
has caused the Debian Bug report #812593,
regarding linux-base: saa7134_alsa won't unload, reported in use by kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
812593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812593
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-base
Version: 3.5
Severity: normal
Tags: newcomer

Dear Maintainer,

Here is the summary:

   * What led up to the situation?
         I don't know when this problem first appeared as I was upgrading
regularly and did not need to remove the module. Recently I was forced to do a
fresh install and I needed to find out the card and tuner for the saa7134
module because the i2c system would not detect the correct card. To try
different settings I needed to unload and reload the saa7134 module multiple
times. But failed at the first attempt due to saa7134_alsa module being
reported as in use. Although lsmod says:
Module                  Size  Used by
saa7134_alsa           17686  0

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
        rmmod -f saa7134_alsa
        modprobe -vfr saa7134_alsa

   * What was the outcome of this action?
        modprobe reported this error:
            modprobe: FATAL: Module saa7134_alsa is in use.
            modprobe: ERROR: ../libkmod/libkmod-module.c:777
kmod_module_remove_module() could not remove 'saa7134_alsa': Device or resource
busy

   * What outcome did you expect instead?
        removal of the module even without the "force" option, as was the case
in prior kernels.



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libuuid-perl           0.05-1+b1
ii  udev                   215-17+deb8u2
ii  util-linux             2.25.2-6

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
  linux-base/disk-id-convert-plan-no-relabel: true
  linux-base/disk-id-manual-boot-loader:
  linux-base/disk-id-update-failed:
  linux-base/do-bootloader-default-changed:
  linux-base/disk-id-convert-auto: true

--- End Message ---
--- Begin Message --- 
On Mon, 2016-01-25 at 14:56 +0200, John Smith wrote:
> Package: linux-base
> Version: 3.5
> Severity: normal
> Tags: newcomer
> 
> Dear Maintainer,
> 
> Here is the summary:
> 
>    * What led up to the situation?
>          I don't know when this problem first appeared as I was upgrading
> regularly and did not need to remove the module. Recently I was forced to do a
> fresh install and I needed to find out the card and tuner for the saa7134
> module because the i2c system would not detect the correct card. To try
> different settings I needed to unload and reload the saa7134 module multiple
> times. But failed at the first attempt due to saa7134_alsa module being
> reported as in use. Although lsmod says:
> Module                  Size  Used by
> saa7134_alsa           17686  0

This only lists other modules that use it, not any other objects that
have references to the module.

>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>         rmmod -f saa7134_alsa
>         modprobe -vfr saa7134_alsa
> 
>    * What was the outcome of this action?
>         modprobe reported this error:
>             modprobe: FATAL: Module saa7134_alsa is in use.
>             modprobe: ERROR: ../libkmod/libkmod-module.c:777
> kmod_module_remove_module() could not remove 'saa7134_alsa': Device or resource
> busy

Most likely some process still had the sound device open.

>    * What outcome did you expect instead?
>         removal of the module even without the "force" option, as was the case
> in prior kernels.

Module removal is not generally supported, so closing this.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
                                    A fail-safe circuit will destroy others.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: