After updating the dvb-kernel from yesterday, I am unable to unload the stv0299 module from my 2.6.7-bk20 kernel.
dvb_ttpci 312588 18 saa7146_vv 50432 1 dvb_ttpci video_buf 22020 1 saa7146_vv saa7146 19044 2 dvb_ttpci,saa7146_vv v4l1_compat 14404 1 saa7146_vv v4l2_common 6208 1 saa7146_vv videodev 9728 1 saa7146_vv ttpci_eeprom 2944 1 dvb_ttpci stv0299 14980 1 dvb_core 89452 20 dvb_ttpci,stv0299 crc32 4352 2 dvb_ttpci,dvb_core i2c_core 24144 3 dvb_ttpci,ttpci_eeprom,stv0299 I have a script that removes the modules from the kernel when I shutdown VDR. --snip-- rmmod dvb-ttpci \ ttpci-eeprom \ stv0299 \ saa7146_vv saa7146 \ video-buf v4l2-common v4l1-compat dvb-core videodev crc32 i2c_core --snip-- But, now when I try to unload the stv0299 driver, it says it is still in use (when it does not appear to be) I would also like to mention that the latest 2.6.7 kernel snapshot has added the following fixes which may or may not be related (although I am almost positive it is from updating the dvb-kernel yesterday because I test it on a daily basis): [EMAIL PROTECTED], 2004-07-03 10:04:12-07:00, [EMAIL PROTECTED] [PATCH] err2-25: dvb_register_i2c_bus() locking fix Found by the Stanford locking checker. Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]> [EMAIL PROTECTED], 2004-07-03 10:03:59-07:00, [EMAIL PROTECTED] [PATCH] err2-1 dvb_register_i2c_device locking fix Fix deadlock identified by the Stanford locking checker. Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>