Re: Kernel freezing with RTL2832U+R820T
Hi Gianluca, the crash / freezing occurs before disconnect in normal operation. So the patch will not solve this problem. Regards Karsten Am 17.05.2013 22:16, schrieb Gianluca Gennari: The driver is working but after some time the system crashes and does not react any more. Just doing the simple test rtl_test -s 3.2e6. Hi Karsten, this patch should fix the system crash after disconnecting the USB stick: https://patchwork.kernel.org/patch/2524651/ Regards, Gianluca Here is what the syslog shows: May 17 18:15:57 PC10 anacron[4446]: Updated timestamp for job `cron.daily' to 2013-05-17 May 17 18:17:01 PC10 /USR/SBIN/CRON[4537]: (root) CMD ( cd / run-parts --report /etc/cron.hourly) May 17 18:25:34 PC10 kernel: [ 890.646246] usb 1-2.1.1: USB disconnect, device number 5 May 17 18:25:34 PC10 kernel: [ 890.646997] usb 1-2.1.1: dvb_usb_v2: 'MSI Mega Sky 55801 DVB-T USB2.0' successfully deinitialized and disconnected May 17 18:25:35 PC10 acpid: input device has been disconnected, fd 18 May 17 18:26:00 PC10 kernel: [ 916.432558] usb 1-2.1.1: new high-speed USB device number 6 using ehci_hcd May 17 18:26:00 PC10 kernel: [ 916.536923] usb 1-2.1.1: New USB device found, idVendor=0bda, idProduct=2838 May 17 18:26:00 PC10 kernel: [ 916.536934] usb 1-2.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 17 18:26:00 PC10 kernel: [ 916.536941] usb 1-2.1.1: Product: RTL2838UHIDIR May 17 18:26:00 PC10 kernel: [ 916.536946] usb 1-2.1.1: Manufacturer: Realtek May 17 18:26:00 PC10 kernel: [ 916.536951] usb 1-2.1.1: SerialNumber: 0001 May 17 18:26:00 PC10 udevd[4852]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci:00/:00:12.2/usb1/1-2/1-2.1/1-2.1.1 1 6': No such file or directory May 17 18:26:00 PC10 kernel: [ 916.609927] usb 1-2.1.1: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state May 17 18:26:00 PC10 kernel: [ 916.610029] usbcore: registered new interface driver dvb_usb_rtl28xxu May 17 18:26:01 PC10 kernel: [ 916.677157] usb 1-2.1.1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer May 17 18:26:01 PC10 kernel: [ 916.677193] DVB: registering new adapter (Realtek RTL2832U reference design) May 17 18:26:01 PC10 kernel: [ 916.700879] usb 1-2.1.1: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))... May 17 18:26:01 PC10 kernel: [ 916.794880] dvb_usb_rtl2832u: disagrees about version of symbol dvb_usb_device_init May 17 18:26:01 PC10 kernel: [ 916.794892] dvb_usb_rtl2832u: Unknown symbol dvb_usb_device_init (err -22) May 17 18:26:01 PC10 kernel: [ 916.794902] dvb_usb_rtl2832u: disagrees about version of symbol dvb_usb_device_init May 17 18:26:01 PC10 kernel: [ 916.794915] dvb_usb_rtl2832u: Unknown symbol dvb_usb_device_init (err -22) May 17 18:26:01 PC10 kernel: [ 916.808351] r820t 3-001a: creating new instance May 17 18:26:01 PC10 kernel: [ 916.820371] r820t 3-001a: Rafael Micro r820t successfully identified May 17 18:26:01 PC10 kernel: [ 916.827020] Registered IR keymap rc-empty May 17 18:26:01 PC10 kernel: [ 916.827277] input: Realtek RTL2832U reference design as /devices/pci:00/:00:12.2/usb1/1-2/1-2.1/1-2.1.1/rc/rc0/input12 May 17 18:26:01 PC10 kernel: [ 916.827531] rc0: Realtek RTL2832U reference design as /devices/pci:00/:00:12.2/usb1/1-2/1-2.1/1-2.1.1/rc/rc0 May 17 18:26:01 PC10 kernel: [ 916.827544] usb 1-2.1.1: dvb_usb_v2: schedule remote query interval to 400 msecs May 17 18:26:01 PC10 kernel: [ 916.840839] usb 1-2.1.1: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected May 17 18:26:14 PC10 acpid: input device has been disconnected, fd 18 May 17 18:26:14 PC10 kernel: [ 930.576375] r820t 3-001a: destroying instance May 17 18:26:14 PC10 kernel: [ 930.578921] usb 1-2.1.1: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully deinitialized and disconnected May 17 18:26:15 PC10 kernel: [ 931.048882] usb 1-2.1.1: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state May 17 18:26:15 PC10 kernel: [ 931.117410] usb 1-2.1.1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer May 17 18:26:15 PC10 kernel: [ 931.117446] DVB: registering new adapter (Realtek RTL2832U reference design) May 17 18:26:15 PC10 kernel: [ 931.123284] usb 1-2.1.1: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))... May 17 18:26:15 PC10 kernel: [ 931.123451] r820t 3-001a: creating new instance May 17 18:26:15 PC10 kernel: [ 931.135279] r820t 3-001a: Rafael Micro r820t successfully identified May 17 18:26:15 PC10 kernel: [ 931.143162] Registered IR keymap rc-empty May 17 18:26:15 PC10 kernel: [ 931.143422] input: Realtek RTL2832U reference design as /devices/pci:00/:00:12.2/usb1/1-2/1-2.1/1-2.1.1/rc/rc1/input13 May 17 18:26:15 PC10 kernel: [ 931.143658] rc1: Realtek RTL2832U reference design as /devices/pci:00/:00:12.2/usb1/1-2/1-2.1/1-2.1.1/rc/rc1 May 17 18:26:15 PC10
[no subject]
Hi All, I have a query regarding Demux driver. I am seeing the Linux dvb and V4L2. Where exactly this driver should go V4L2 or dvb -- 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
3.9.2 kernel - IR / em28xx_rc broken?
Hi, I have a PCTV 290e DVB2 adapter (em28xx, em28xx_dvb, em28xx_rc, cxd2820r), and I have just discovered that the IR remote control has stopped working with VDR when using a vanilla 3.9.2 kernel. Downgrading the kernel to 3.8.12 fixes things again. (Switching to my old DVB NOVA-T2 device fixes things too, although it cannot receive HDTV channels, of course). Has anyone else noticed problems like this, please? Thanks, Chris -- 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
[3.9.2] Broken IR with em28xx?
Hi, Further to my original email, here is the dmesg log from 3.9.2 when inserting my 290e adapter: [ 1273.581835] usb 10-4: new high-speed USB device number 6 using ehci-pci [ 1273.704508] em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0) [ 1273.712167] em28xx: DVB interface 0 found: isoc [ 1273.715540] em28xx: chip ID is em28174 [ 1274.011883] em28174 #0: Identified as PCTV nanoStick T2 290e (card=78) [ 1274.017111] em28174 #0: v4l2 driver version 0.1.3 [ 1274.025554] em28174 #0: V4L2 video device registered as video0 [ 1274.030093] em28174 #0: dvb set to isoc mode. [ 1274.037116] tda18271 6-0060: creating new instance [ 1274.045237] TDA18271HD/C2 detected @ 6-0060 [ 1274.216011] DVB: registering new adapter (em28174 #0) [ 1274.219769] usb 10-4: DVB: registering adapter 0 frontend 0 (Sony CXD2820R)... [ 1274.226240] em28174 #0: Successfully loaded em28xx-dvb [ 1274.230632] Registered IR keymap rc-pinnacle-pctv-hd [ 1274.234529] input: em28xx IR (em28174 #0) as /devices/pci:00/:00:1d.7/usb10/10-4/rc/rc1/input18 [ 1274.235704] ir-keytable[4661]: segfault at 0 ip 00401cc0 sp 7fff26dae550 error 4 in ir-keytable[40+8000] [ 1274.252304] rc1: em28xx IR (em28174 #0) as /devices/pci:00/:00:1d.7/usb10/10-4/rc/rc1 [ 1334.876948] tda18271: performing RF tracking filter calibration [ 1337.231439] tda18271: RF tracking filter calibration complete The ir-keytable segfault is a userspace error that predates the 3.9.x kernel. Reloading the IR keys manually seems OK: # ir-keytable --auto-load /etc/rc_maps.cfg --sysdev=rc1 Old keytable cleared Wrote 45 keycode(s) to driver Protocols changed to other VDR behaves as if it's just not receiving any events, although as I said, the 3.8.x kernels are OK. Cheers, Chris -- 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: 3.9.2 kernel - IR / em28xx_rc broken?
Am 18.05.2013 15:57, schrieb Chris Rankin: I have a PCTV 290e DVB2 adapter (em28xx, em28xx_dvb, em28xx_rc, cxd2820r), and I have just discovered that the IR remote control has stopped working with VDR when using a vanilla 3.9.2 kernel. Downgrading the kernel to 3.8.12 fixes things again. (Switching to my old DVB NOVA-T2 device fixes things too, although it cannot receive HDTV channels, of course). Great. :( :( :( There have been several changes in the em28xx and core RC code between 3.8 and 3.9... I can't see anything obvious, the RC device seems to be registered correctly. Could you please bisect ? Regards, Frank -- 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: 3.9.2 kernel - IR / em28xx_rc broken?
- Original Message - Am 18.05.2013 15:57, schrieb Chris Rankin: I have a PCTV 290e DVB2 adapter (em28xx, em28xx_dvb, em28xx_rc, cxd2820r), and I have just discovered that the IR remote control has stopped working with VDR when using a vanilla 3.9.2 kernel. Downgrading the kernel to 3.8.12 fixes things again. (Switching to my old DVB NOVA-T2 device fixes things too, although it cannot receive HDTV channels, of course). Great. :( :( :( There have been several changes in the em28xx and core RC code between 3.8 and 3.9... I can't see anything obvious, the RC device seems to be registered correctly. Could you please bisect ? Unfortunately, no I can't. (No git tree here - just a tarball downloaded via FTP). However, maybe I could out some printk() statements into the code if you could point out where the hot-spots might be, please? Cheers, Chris -- 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: 3.9.2 kernel - IR / em28xx_rc broken?
Am 18.05.2013 17:17, schrieb Chris Rankin: - Original Message - Am 18.05.2013 15:57, schrieb Chris Rankin: I have a PCTV 290e DVB2 adapter (em28xx, em28xx_dvb, em28xx_rc, cxd2820r), and I have just discovered that the IR remote control has stopped working with VDR when using a vanilla 3.9.2 kernel. Downgrading the kernel to 3.8.12 fixes things again. (Switching to my old DVB NOVA-T2 device fixes things too, although it cannot receive HDTV channels, of course). Great. :( :( :( There have been several changes in the em28xx and core RC code between 3.8 and 3.9... I can't see anything obvious, the RC device seems to be registered correctly. Could you please bisect ? Unfortunately, no I can't. (No git tree here - just a tarball downloaded via FTP). However, maybe I could out some printk() statements into the code if you could point out where the hot-spots might be, please? For the em28xx driver: em28xx-input.c: em28xx_ir_work() is called every 100ms calls em28xx_ir_handle_key() - calls ir-get_key() which is em2874_polling_getkey() in case of your device - reports the detected key via rc_keydown() through the RC core HTH, Frank -- 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
cron job: media_tree daily build: ERRORS
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Sat May 18 19:00:19 CEST 2013 git branch: test git hash: 4237c09a63906b980741725da63f85e454caec02 gcc version:i686-linux-gcc (GCC) 4.8.0 host hardware: x86_64 host os:3.8-3.slh.2-amd64 linux-git-arm-davinci: OK linux-git-arm-exynos: WARNINGS linux-git-arm-omap: WARNINGS linux-git-blackfin: WARNINGS linux-git-i686: OK linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-sh: OK linux-git-x86_64: OK linux-2.6.31.14-i686: WARNINGS linux-2.6.32.27-i686: WARNINGS linux-2.6.33.7-i686: WARNINGS linux-2.6.34.7-i686: WARNINGS linux-2.6.35.9-i686: WARNINGS linux-2.6.36.4-i686: WARNINGS linux-2.6.37.6-i686: WARNINGS linux-2.6.38.8-i686: WARNINGS linux-2.6.39.4-i686: WARNINGS linux-3.0.60-i686: WARNINGS linux-3.10-rc1-i686: WARNINGS linux-3.1.10-i686: WARNINGS linux-3.2.37-i686: WARNINGS linux-3.3.8-i686: WARNINGS linux-3.4.27-i686: WARNINGS linux-3.5.7-i686: WARNINGS linux-3.6.11-i686: WARNINGS linux-3.7.4-i686: WARNINGS linux-3.8-i686: OK linux-3.9.2-i686: OK linux-2.6.31.14-x86_64: WARNINGS linux-2.6.32.27-x86_64: WARNINGS linux-2.6.33.7-x86_64: WARNINGS linux-2.6.34.7-x86_64: WARNINGS linux-2.6.35.9-x86_64: WARNINGS linux-2.6.36.4-x86_64: WARNINGS linux-2.6.37.6-x86_64: WARNINGS linux-2.6.38.8-x86_64: WARNINGS linux-2.6.39.4-x86_64: WARNINGS linux-3.0.60-x86_64: WARNINGS linux-3.10-rc1-x86_64: WARNINGS linux-3.1.10-x86_64: WARNINGS linux-3.2.37-x86_64: WARNINGS linux-3.3.8-x86_64: WARNINGS linux-3.4.27-x86_64: WARNINGS linux-3.5.7-x86_64: WARNINGS linux-3.6.11-x86_64: WARNINGS linux-3.7.4-x86_64: WARNINGS linux-3.8-x86_64: OK linux-3.9.2-x86_64: OK apps: ERRORS spec-git: OK sparse: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Saturday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Saturday.tar.bz2 The Media Infrastructure API from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.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: 3.9.2 kernel - IR / em28xx_rc broken?
- Original Message - For the em28xx driver: em28xx-input.c: em28xx_ir_work() is called every 100ms calls em28xx_ir_handle_key() - calls ir-get_key() which is em2874_polling_getkey() in case of your device - reports the detected key via rc_keydown() through the RC core By the looks of things, it's not recognising the protocol: em2874_ir_change_protocol() is setting ir-rc_type to RC_BIT_UNKNOWN. Shouldn't it be using RC5 instead? Cheers, Chris -- 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: 3.9.2 kernel - IR / em28xx_rc broken?
- Original Message - For the em28xx driver: em28xx-input.c: em28xx_ir_work() is called every 100ms calls em28xx_ir_handle_key() - calls ir-get_key() which is em2874_polling_getkey() in case of your device - reports the detected key via rc_keydown() through the RC core Confirmed: em28xx is failing to set the protocol to RC5, which means that em2874_polling_getkey() is using the default (UNKNOWN) case to interpret the scan codes. Forcing em2874_polling_getkey() to use RC5 fixes the remote control for this device. Cheers, Chris -- 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
