af9015: Second Tuner hangs after a while
Hello there, I got a MSI DigiVox Duo stick identifying as: Bus 001 Device 005: ID 1462:8801 Micro Star International Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1462 Micro Star International idProduct 0x8801 bcdDevice2.00 iManufacturer 1 Afatech iProduct2 DVB-T 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) Until some time ago, there was not even a remote chance getting this Dual-Tuner Stick to work. When trying to tune in a second transponder, the log got spammed with these: [ 835.412375] af9015: command failed:1 [ 835.412383] mxl5005s I2C write failed However, I applied the patches ba730b56cc9afbcb10f329c17320c9e535c43526 and 61875c55170f2cf275263b4ba77e6cc787596d9f from Antti Palosaari. For the first time I got able to receive two Transponders at once. Sadly after a while the second adapter stops working, showing the I2C erros above. The first adapter keeps working. Also attaching and removing the stick does not work out very well. First plugin attempt: [ 78.552597] dvb-usb: found a 'MSI DIGIVOX Duo' in cold state, will try to load a firmware [ 78.592456] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' [ 78.662114] dvb-usb: found a 'MSI DIGIVOX Duo' in warm state. [ 78.662251] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 78.663514] DVB: registering new adapter (MSI DIGIVOX Duo) [ 78.709768] af9013: firmware version 0.0.0.0 [ 78.711858] DVB: registering adapter 0 frontend 0 (Afatech AF9013)... [ 78.745265] MXL5005S: Attached at address 0xc6 [ 78.745278] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 78.746513] DVB: registering new adapter (MSI DIGIVOX Duo) [ 79.361106] af9015: firmware did not run [ 79.361117] af9015: firmware copy to 2nd frontend failed, will disable it [ 79.361127] dvb-usb: no frontend was attached by 'MSI DIGIVOX Duo' [ 79.361136] dvb-usb: MSI DIGIVOX Duo successfully initialized and connected. [ 79.368407] usbcore: registered new interface driver dvb_usb_af9015 removing and inserting again [ 160.290935] dvb-usb: MSI DIGIVOX Duo successfully deinitialized and disconnected. [ 197.576325] af9015: recv bulk message failed:-110 [ 197.576338] af9015: eeprom
Re: af9015: Second Tuner hangs after a while
I managed to get the Oops when disconnecting: Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.144450] Oops: [#1] SMP Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.147537] Process kworker/0:4 (pid: 1912, ti=f2f94000 task=f44d6180 task.ti=f2f94000) Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.147682] Stack: Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.148008] Call Trace: Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.148008] Code: f8 75 09 83 ea 28 74 04 89 d0 eb e7 83 c0 10 e9 ba 73 d9 c8 55 89 cd 57 56 89 c6 53 bb a1 ff ff ff 83 ec 08 89 54 24 04 8b 40 08 Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.148008] EIP: [f850c92e] i2c_transfer+0x17/0xb7 [i2c_core] SS:ESP 0068:f2f95eec Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.148008] CR2: 0002 Message from syslogd@xbmc at Dec 27 17:53:32 ... kernel:[ 493.164072] Oops: [#2] SMP Antti Palosaari wrote: On 12/27/2011 06:44 PM, Thomas Holzeisen wrote: Until some time ago, there was not even a remote chance getting this Dual-Tuner Stick to work. When trying to tune in a second transponder, the log got spammed with these: [ 835.412375] af9015: command failed:1 [ 835.412383] mxl5005s I2C write failed However, I applied the patches ba730b56cc9afbcb10f329c17320c9e535c43526 and 61875c55170f2cf275263b4ba77e6cc787596d9f from Antti Palosaari. For the first time I got able to receive two Transponders at once. Sadly after a while the second adapter stops working, showing the I2C erros above. The first adapter keeps working. Also attaching and removing the stick does not work out very well. this is repeatable to me every time. Removing the stick when in warm state, leads to kernel oops every time. Kernel Version is 3.1.2. Rather interesting problems. As I understand there is two success reports and of course tests I have done. This is first report having problems. I have PULL requested those changes about one month ago and hope those will committed soon in order to get more testers... It is big change, basically whole driver is rewritten and as it is one of the most popular devices it will be big chaos after Kernel merge if there will be problems like you have. For now I will still be and wait more reports. regards Antti -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U wont compile against 2.6.38
I already resolved the symbol thing. Your lsusb explains a lot, you have a RTl2832, while I have the RTL2831 which seem to be Revision 4 of the RTL2830. However, there seem to be big similarities between all those chips. It might be not that hard for the contributors of this driver to add support for the early chips as well. Maybe Jan can shade some light on it, since he wrote the initial RTL2831 driver. In any case I may help with testing it. Sascha Wüstemann wrote: Thomas Holzeisen wrote: Unknown symbol means, there is unresolved dependencies at your kernel or false dependencies in the module. My stick works with those google hosted new driver sources and I have no use for lirc, so nothing about it at the following lines, they are stripped, too: ~ # lsusb -v Bus 001 Device 021: ID 1d19:1101 Dexatek Technology Ltd. DK DVB-T Dongle Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1d19 Dexatek Technology Ltd. idProduct 0x1101 DK DVB-T Dongle bcdDevice1.00 iManufacturer 1 Realtek iProduct2 Rtl2832UDVB iSerial 3 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 USB2.0-BulkIso bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 2 Device Status: 0x (Bus Powered) ~ # lsmod | grep dvb dvb_usb_rtl2832u 190302 0 dvb_usb17272 1 dvb_usb_rtl2832u dvb_core 69295 1 dvb_usb rc_core15790 2 dvb_usb ~ # dmesg usb 1-6: new high speed USB device number 20 using ehci_hcd hub 1-6:1.0: USB hub found hub 1-6:1.0: 4 ports detected usb 1-6.3: new high speed USB device number 21 using ehci_hcd dvb-usb: found a 'DK DVBT DONGLE' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DK DVBT DONGLE) DVB: registering adapter 0 frontend 0 (Realtek DVB-T RTL2832)... dvb-usb: DK DVBT DONGLE successfully initialized and connected. dvb-usb: found a 'DK DVBT DONGLE' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DK DVBT DONGLE) DVB: registering adapter 1 frontend 0 (Realtek DVB-T RTL2832)... dvb-usb: DK DVBT DONGLE successfully initialized and connected. Yes, works at no powered four port USB-2.0 mini hub without problems. ~ # uname -a Linux killerghost 2.6.39-gentoo-r1 #1 SMP Fri Jun 10 12:16:38 CEST 2011 x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel GNU/Linux Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U wont compile against 2.6.38
0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 6 Iso-In, Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x03ac 1x 940 bytes bInterval 1 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 2 Device Status: 0x (Bus Powered) Finally the kernel version (the only one installed): # uname -a Linux xbmc 2.6.38-bpo.2-686 #1 SMP Tue Jun 14 11:43:18 UTC 2011 i686 GNU/Linux Greetings, from Germany as well ;-) Thomas Sascha Wüstemann wrote: Thomas Holzeisen wrote: Hi there, I tried to get an RTL2831U dvb-t usb-stick running with a more recent kernel (2.6.38) and failed. The hg respository ~jhoogenraad/rtl2831-r2 aborts on countless drivers, the rc coding seem have to changed a lot since it got touched the last time. The hg respository ~anttip/rtl2831u wont compile as well, since its even older. The recent git respositories for media_tree and anttip dont contain drivers for the rtl2831u. Has this device been abandoned, or is anyone working on it? greetings, Thomas There are still people working on it and there is new sources, e.g. look at http://www.spinics.net/lists/linux-media/msg24890.html at the very bottom. Worked like a charm at my system with kernel 2.6.39. I think, there will be announcements later at http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U driver updates
Hi again, i managed to merge the driver with a media_build snapshot by hand, and managed to get it loaded without errors. But now where I looked more closely to the files, I noticed something. The driver refered mentions RTL2832u and some following versions, but it _dont_ mention RTL2831u at all. Also the card I got contains the tuners mxl5005, mt2060 and qt1010, while this driver contains files for mxl5007 and mt2063. Teach me wrong, but it looks like the RTL2381u had been forgotten when this driver got made ;-) Greeting, Thomas Sascha Wüstemann wrote: Jan Hoogenraad wrote: Sascha: Thanks for the links Would you know how to contact poma ? http://www.spinics.net/lists/linux-media/msg24890.html I will be getting more info from Realtek soon. I did not realize that they were putting out updated drivers. Once the status becomes more clear, I'll update http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U The mailinglist archive where poma had written is new to me, no sorry. Zdenek Stybla hosts the website he advised to me. When I contacted Zdenek he made contact to a guy from realtek which in return sent us their (?) new drivers - you should contact Zdenek. I don't work on the rtl2831 sources I'd like to use them :-) I am looking forward to have current sources at v4l or at least updated information at the info page at linuxtv.org. Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RTL2831U wont compile against 2.6.38
Hi there, I tried to get an RTL2831U dvb-t usb-stick running with a more recent kernel (2.6.38) and failed. The hg respository ~jhoogenraad/rtl2831-r2 aborts on countless drivers, the rc coding seem have to changed a lot since it got touched the last time. The hg respository ~anttip/rtl2831u wont compile as well, since its even older. The recent git respositories for media_tree and anttip dont contain drivers for the rtl2831u. Has this device been abandoned, or is anyone working on it? greetings, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dvb_usb_rtl2831u module cause oops on kernel 2.6.32 when loading
] ? driver_register+0x87/0xe0 [ 67.813129] [f80b3aa6] ? usb_register_driver+0x5d/0xb4 [usbcore] [ 67.813129] [f9e61000] ? rtd2831u_usb_module_init+0x0/0x2c [dvb_usb_rtl2831u] [ 67.813129] [f9e61015] ? rtd2831u_usb_module_init+0x15/0x2c [dvb_usb_rtl2831u] [ 67.813129] [c100113e] ? do_one_initcall+0x55/0x155 [ 67.813129] [c1057dd7] ? sys_init_module+0xa7/0x1d7 [ 67.813129] [c10030fb] ? sysenter_do_call+0x12/0x28 [ 67.813129] Code: be e1 f9 20 74 18 8b 86 a0 00 00 00 55 ff 74 38 04 68 59 b8 e1 f9 e8 1b 21 45 c7 83 c4 0c 8b 86 a0 00 00 00 8b 14 24 8b 44 38 04 f0 0f ab 02 45 83 c7 08 3b ae a4 00 00 00 7c c2 83 be ac 00 00 [ 67.813129] EIP: [f9e1a3ba] dvb_usb_remote_init+0x12e/0x209 [dvb_usb] SS:ESP 0068:f6363e88 [ 67.813129] CR2: 02f77c40 [ 68.235926] ---[ end trace b14c844e3eed98d4 ]--- Can you test the current version ? Thomas Holzeisen wrote: Hi, i am using a DVB-T USB-Stick with Realtek RTL2831 chip (14aa:0160) on Debian Lenny having the lastest Backport kernel 2.6.32. $ uname -a Linux xbmc 2.6.32-bpo.5-686 #1 SMP Fri Jun 11 22:20:29 UTC 2010 i686 GNU/Linux For v4l I took the drivers from here: http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/ The checked out source compile and installs fine. I compiled them starting with make distclean. But when plugging the DVB-Stick this happens: [ 229.524028] usb 4-2: new high speed USB device using ehci_hcd and address 3 [ 229.658591] usb 4-2: New USB device found, idVendor=14aa, idProduct=0160 [ 229.661204] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 229.663841] usb 4-2: Product: DTV Receiver [ 229.666308] usb 4-2: Manufacturer: DTV Receiver [ 229.668826] usb 4-2: SerialNumber: 00067936 [ 229.671609] usb 4-2: configuration #1 chosen from 1 choice [ 230.266960] dvb-usb: found a 'Freecom USB 2.0 DVB-T Device' in warm state. [ 230.270314] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 230.273641] DVB: registering new adapter (Freecom USB 2.0 DVB-T Device) [ 230.277461] DVB: registering adapter 0 frontend 0 (Realtek RTL2831 DVB-T)... [ 230.282081] BUG: unable to handle kernel paging request at 02b65c40 [ 230.285794] IP: [f7c623ba] dvb_usb_remote_init+0x12e/0x209 [dvb_usb] [ 230.291463] *pde = [ 230.293969] Oops: 0002 [#1] SMP [ 230.293969] last sysfs file: /sys/devices/pci:00/:00:06.1/usb4/4-2/bmAttributes [ 230.293969] Modules linked in: dvb_usb_rtl2831u(+) dvb_usb_dibusb_common dvb_usb dib3000mc dibx000_common dvb_ttpci dvb_core saa7146_vv videodev v4l1_compat saa7146 videobuf_dma_sg videobuf_core ttpci_eeprom iscsi_trgt crc32c loop snd_hda_codec_nvhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device snd tpm_tis soundcore tpm shpchp psmouse wmi serio_raw tpm_bios snd_page_alloc pcspkr pci_hotplug processor evdev button ir_core nvidia(P) lirc_imon i2c_nforce2 i2c_core lirc_dev ext3 jbd mbcache raid1 md_mod usbhid hid sg sr_mod cdrom sd_mod crc_t10dif usb_storage ahci ata_generic libata ehci_hcd ohci_hcd scsi_mod usbcore nls_base forcedeth thermal fan thermal_sys [last unloaded: scsi_wait_scan] [ 230.293969] [ 230.293969] Pid: 3279, comm: modprobe Tainted: P (2.6.32-bpo.5-686 #1) Point of View [ 230.293969] EIP: 0060:[f7c623ba] EFLAGS: 00010246 CPU: 0 [ 230.293969] EIP is at dvb_usb_remote_init+0x12e/0x209 [dvb_usb] [ 230.293969] EAX: 69656148 EBX: f589b000 ECX: c14c18e4 EDX: f589b018 [ 230.293969] ESI: f5904000 EDI: 03b8 EBP: 0077 ESP: f5851e88 [ 230.293969] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 230.293969] Process modprobe (pid: 3279, ti=f585 task=f5cd4400 task.ti=f585) [ 230.293969] Stack: [ 230.293969] f589b018 f5904000 f5904000 f5904864 0001 f7c61945 f5904418 f80bb8d0 [ 230.293969] 0 f5912000 f5b8f800 f80bad88 f80bad88 f5912000 [ 230.293969] 0 f80bb894 f80ba970 f80b886d f80ba960 f5912000 f80c8c98 f591201c [ 230.293969] Call Trace: [ 230.293969] [f7c61945] ? dvb_usb_device_init+0x515/0x51c [dvb_usb] [ 230.293969] [f80b886d] ? rtd2831u_usb_probe+0x19/0x48 [dvb_usb_rtl2831u] [ 230.293969] [f80c8c98] ? usb_probe_interface+0xe7/0x130 [usbcore] [ 230.293969] [c11b2c22] ? driver_probe_device+0x8a/0x11e [ 230.293969] [c11b2cf6] ? __driver_attach+0x40/0x5b [ 230.293969] [c11b2667] ? bus_for_each_dev+0x37/0x5f [ 230.293969] [c11b2af5] ? driver_attach+0x11/0x13 [ 230.293969] [c11b2cb6] ? __driver_attach+0x0/0x5b [ 230.293969] [c11b2135] ? bus_add_driver+0x99/0x1c2 [ 230.293969] [c11b2f2b] ? driver_register+0x87/0xe0 [ 230.293969] [f80c8aa6] ? usb_register_driver+0x5d/0xb4 [usbcore] [ 230.293969] [f80f6000] ? rtd2831u_usb_module_init+0x0/0x2c [dvb_usb_rtl2831u] [ 230.293969] [f80f6015] ? rtd2831u_usb_module_init+0x15/0x2c [dvb_usb_rtl2831u] [ 230.293969] [c100113e] ? do_one_initcall+0x55/0x155 [ 230.293969] [c1057dd7] ? sys_init_module+0xa7/0x1d7 [ 230.293969] [c10030fb] ? sysenter_do_call+0x12/0x28 [ 230.293969] Code: 3e c6 f7 20 74 18 8b 86 a0 00 00 00 55 ff 74
dvb_usb_rtl2831u module cause oops on kernel 2.6.32 when loading
Hi, i am using a DVB-T USB-Stick with Realtek RTL2831 chip (14aa:0160) on Debian Lenny having the lastest Backport kernel 2.6.32. $ uname -a Linux xbmc 2.6.32-bpo.5-686 #1 SMP Fri Jun 11 22:20:29 UTC 2010 i686 GNU/Linux For v4l I took the drivers from here: http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/ The checked out source compile and installs fine. I compiled them starting with make distclean. But when plugging the DVB-Stick this happens: [ 229.524028] usb 4-2: new high speed USB device using ehci_hcd and address 3 [ 229.658591] usb 4-2: New USB device found, idVendor=14aa, idProduct=0160 [ 229.661204] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 229.663841] usb 4-2: Product: DTV Receiver [ 229.666308] usb 4-2: Manufacturer: DTV Receiver [ 229.668826] usb 4-2: SerialNumber: 00067936 [ 229.671609] usb 4-2: configuration #1 chosen from 1 choice [ 230.266960] dvb-usb: found a 'Freecom USB 2.0 DVB-T Device' in warm state. [ 230.270314] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 230.273641] DVB: registering new adapter (Freecom USB 2.0 DVB-T Device) [ 230.277461] DVB: registering adapter 0 frontend 0 (Realtek RTL2831 DVB-T)... [ 230.282081] BUG: unable to handle kernel paging request at 02b65c40 [ 230.285794] IP: [f7c623ba] dvb_usb_remote_init+0x12e/0x209 [dvb_usb] [ 230.291463] *pde = [ 230.293969] Oops: 0002 [#1] SMP [ 230.293969] last sysfs file: /sys/devices/pci:00/:00:06.1/usb4/4-2/bmAttributes [ 230.293969] Modules linked in: dvb_usb_rtl2831u(+) dvb_usb_dibusb_common dvb_usb dib3000mc dibx000_common dvb_ttpci dvb_core saa7146_vv videodev v4l1_compat saa7146 videobuf_dma_sg videobuf_core ttpci_eeprom iscsi_trgt crc32c loop snd_hda_codec_nvhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device snd tpm_tis soundcore tpm shpchp psmouse wmi serio_raw tpm_bios snd_page_alloc pcspkr pci_hotplug processor evdev button ir_core nvidia(P) lirc_imon i2c_nforce2 i2c_core lirc_dev ext3 jbd mbcache raid1 md_mod usbhid hid sg sr_mod cdrom sd_mod crc_t10dif usb_storage ahci ata_generic libata ehci_hcd ohci_hcd scsi_mod usbcore nls_base forcedeth thermal fan thermal_sys [last unloaded: scsi_wait_scan] [ 230.293969] [ 230.293969] Pid: 3279, comm: modprobe Tainted: P (2.6.32-bpo.5-686 #1) Point of View [ 230.293969] EIP: 0060:[f7c623ba] EFLAGS: 00010246 CPU: 0 [ 230.293969] EIP is at dvb_usb_remote_init+0x12e/0x209 [dvb_usb] [ 230.293969] EAX: 69656148 EBX: f589b000 ECX: c14c18e4 EDX: f589b018 [ 230.293969] ESI: f5904000 EDI: 03b8 EBP: 0077 ESP: f5851e88 [ 230.293969] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 230.293969] Process modprobe (pid: 3279, ti=f585 task=f5cd4400 task.ti=f585) [ 230.293969] Stack: [ 230.293969] f589b018 f5904000 f5904000 f5904864 0001 f7c61945 f5904418 f80bb8d0 [ 230.293969] 0 f5912000 f5b8f800 f80bad88 f80bad88 f5912000 [ 230.293969] 0 f80bb894 f80ba970 f80b886d f80ba960 f5912000 f80c8c98 f591201c [ 230.293969] Call Trace: [ 230.293969] [f7c61945] ? dvb_usb_device_init+0x515/0x51c [dvb_usb] [ 230.293969] [f80b886d] ? rtd2831u_usb_probe+0x19/0x48 [dvb_usb_rtl2831u] [ 230.293969] [f80c8c98] ? usb_probe_interface+0xe7/0x130 [usbcore] [ 230.293969] [c11b2c22] ? driver_probe_device+0x8a/0x11e [ 230.293969] [c11b2cf6] ? __driver_attach+0x40/0x5b [ 230.293969] [c11b2667] ? bus_for_each_dev+0x37/0x5f [ 230.293969] [c11b2af5] ? driver_attach+0x11/0x13 [ 230.293969] [c11b2cb6] ? __driver_attach+0x0/0x5b [ 230.293969] [c11b2135] ? bus_add_driver+0x99/0x1c2 [ 230.293969] [c11b2f2b] ? driver_register+0x87/0xe0 [ 230.293969] [f80c8aa6] ? usb_register_driver+0x5d/0xb4 [usbcore] [ 230.293969] [f80f6000] ? rtd2831u_usb_module_init+0x0/0x2c [dvb_usb_rtl2831u] [ 230.293969] [f80f6015] ? rtd2831u_usb_module_init+0x15/0x2c [dvb_usb_rtl2831u] [ 230.293969] [c100113e] ? do_one_initcall+0x55/0x155 [ 230.293969] [c1057dd7] ? sys_init_module+0xa7/0x1d7 [ 230.293969] [c10030fb] ? sysenter_do_call+0x12/0x28 [ 230.293969] Code: 3e c6 f7 20 74 18 8b 86 a0 00 00 00 55 ff 74 38 04 68 59 38 c6 f7 e8 1b a1 60 c9 83 c4 0c 8b 86 a0 00 00 00 8b 14 24 8b 44 38 04 f0 0f ab 02 45 83 c7 08 3b ae a4 00 00 00 7c c2 83 be ac 00 00 [ 230.293969] EIP: [f7c623ba] dvb_usb_remote_init+0x12e/0x209 [dvb_usb] SS:ESP 0068:f5851e88 [ 230.293969] CR2: 02b65c40 [ 230.663846] ---[ end trace e2ebfa1976bffdae ]--- Mostly interesting, the modules are still getting loaded: $ lsmod | grep dvb dvb_usb_rtl2831u 89189 15 dvb_usb_dibusb_common 4578 1 dvb_usb_rtl2831u dvb_usb13320 2 dvb_usb_rtl2831u,dvb_usb_dibusb_common dib3000mc 8544 1 dvb_usb_dibusb_common dvb_ttpci 70046 0 dvb_core 63034 2 dvb_usb,dvb_ttpci saa7146_vv 31312 1 dvb_ttpci saa7146
