Skip to contentSkip to conversation

ERROR: Module dvb_usb_aaa_dvbusb_demo is in use

linux-dvb wdy9927 2 participants 2 messages Mar 5, 2009 Media (V4L/DVB)

lore
Share & tools
lore

wdy9927

author
#0 lore raw

Hi,
I had make install a module for a dvb usb box which writen by my self. But this one didn't have real frontend ops and tuner ops.These functions did nothing but return 0. Like this
static int demo_fe_init(struct dvb_frontend *fe)

{
    return 0;
}

After the usb box removed from linux, the DVB system called demo_fe_release and demo_tu_release, sofar that seems very good! But, I can't rmmod this module normally. It showed "ERROR: Module dvb_usb_dvbusb_demo is in use".This error is diffrent with "ERROR: Module dvb_usb is in use by dvb_usb_dvbusb_demo"

How can i rmmod this module with out reboot Linux.

thanks

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

[   93.895305] dvb-usb: found a 'DVB USB2.0  Demo' in warm state.
[   93.897118] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   93.897633] DVB: registering new adapter (DVB USB2.0  Demo)
[   93.899827] DVB_DEMO: demo_frontend_attach:
[   93.899829]
[   93.899842] DVB_DEMO: demo_fe_attach:
[   93.899844]
[   93.902815] DVB: registering adapter 0 frontend 0 ( Demo USB Driver)...
[   93.906273] DVB_DEMO: demo_tuner_attach:
[   93.906275]
[   93.906286] DVB_DEMO: demo_tu_attach:
[   93.906288]
[   93.909823] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   93.912149] DVB: registering new adapter (DVB USB2.0  Demo)
[   93.914388] DVB_DEMO: demo_frontend_attach:
[   93.914390]
[   93.914401] DVB_DEMO: demo_fe_attach:
[   93.914403]
[   93.917737] DVB: registering adapter 1 frontend 0 ( Demo USB Driver)...
[   93.933098] DVB_DEMO: demo_tuner_attach:
[   93.933101]
[   93.933117] DVB_DEMO: demo_tu_attach:
[   93.933119]
[   93.936762] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:02.1/usb2/2-6/input/input7
[   93.980756] dvb-usb: schedule remote query interval to 20000 msecs.
[   93.980773] dvb-usb: DVB USB2.0  Demo successfully initialized and connected.
[   93.984967] DVB_DEMO: demo_init: running
[   93.984970]
[   93.986705] usbcore: registered new interface driver dvb_usb_demo
[  119.219743] type=1503 audit(1236249152.266:5): operation="inode_permission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/5886/net/" pid=5886 profile="/usr/sbin/cupsd"
[  120.405504] type=1503 audit(1236249153.454:6): operation="inode_permission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/5891/net/" pid=5891 profile="/usr/sbin/cupsd"
[  120.405583] type=1503 audit(1236249153.454:7): operation="socket_create" family="ax25" sock_type="dgram" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405598] type=1503 audit(1236249153.454:8): operation="socket_create" family="netrom" sock_type="seqpacket" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405613] type=1503 audit(1236249153.454:9): operation="socket_create" family="rose" sock_type="dgram" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405634] type=1503 audit(1236249153.454:10): operation="socket_create" family="ipx" sock_type="dgram" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405648] type=1503 audit(1236249153.454:11): operation="socket_create" family="appletalk" sock_type="dgram" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405662] type=1503 audit(1236249153.454:12): operation="socket_create" family="econet" sock_type="dgram" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405684] type=1503 audit(1236249153.454:13): operation="socket_create" family="ash" sock_type="dgram" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  120.405697] type=1503 audit(1236249153.454:14): operation="socket_create" family="x25" sock_type="seqpacket" protocol=0 pid=5891 profile="/usr/sbin/cupsd"
[  121.103127] ppdev0: registered pardevice
[  121.152421] ppdev0: unregistered pardevice
[  121.224252] ppdev0: registered pardevice
[  121.272607] ppdev0: unregistered pardevice
[  121.333579] ppdev0: registered pardevice
[  121.384426] ppdev0: unregistered pardevice
[  170.980533] hub 2-0:1.0: port 6 disabled by hub (EMI?), re-enabling...
[  170.980552] usb 2-6: USB disconnect, address 4
[  171.009401] DVB_DEMO: demo_tu_release:
[  171.009403]
[  171.009416] DVB_DEMO: demo_fe_release:
[  171.009418]
[  171.010558] DVB_DEMO: demo_tu_release:
[  171.010560]
[  171.010571] DVB_DEMO: demo_fe_release:
[  171.010573]
[  171.013164] dvb-usb: DVB USB2.0  Demo successfully deinitialized and disconnected.
wdy@wdy:~$ sudo rmmod dvb-usb-dvbusb-demo
[sudo] password for wdy:
ERROR: Module dvb_usb_dvbusb_demo is in use

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#1 lore raw

Hi,

Quoted 8 lines · On Thu, 5 Mar 2009, wdy9927 wrote:

I had make install a module for a dvb usb box which writen by my self. But this one didn't have real frontend ops and tuner ops.These functions did nothing but return 0.
Like this
static int demo_fe_init(struct dvb_frontend *fe)
{
    return 0;
}

Quoted 5 lines

After the usb box removed from linux, the DVB system called demo_fe_release and demo_tu_release, sofar that seems very good? But, I can't rmmod this module normally. It showed "ERROR: Module dvb_usb_dvbusb_demo is in use".This error is diffrent with "ERROR: Module dvb_usb is in use by dvb_usb_dvbusb_demo"

How can i rmmod this module with out reboot Linux.

This is a known problem with every dvb-device-driver (especially the ones using dvb-usb) which are implementing the frontend-part not as an independent kernel module. When the frontend-driver is "released" the dvb-core is doing something like use-count-decrement on the module. As the use-count was never incremented (dvb_attach cannot be used on function which are not exported with EXPORT_SYMBOL) the count is now -1, which is same as 0xffffffff.

rmmod is refusing to unload a module which has a use_count != 0. This is the problem you're facing.

You could still try to use rmmod -f to force to unload. Or you make your frontend-driver a seperate kernel module.

Patrick.