Bug 667157
| Summary: | 2.6.35.10 version of kernel killed functionality of remote controller (kernel module dvb_usb_dib0700) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tommi R. <tra> |
| Component: | kernel | Assignee: | Jarod Wilson <jarodwilson> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | gansalmon, itamar, jarod, jonathan, kernel-maint, madhu.chinakonda, mchehab, mcree |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-2.6.35.11-83.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-11 02:48:16 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Tommi R.
2011-01-04 16:54:21 UTC
Created attachment 471707 [details]
output of modinfo dvb_usb_dib0700 when IR is not working
Note that there are no dvb_usb_dib0700_ir_proto parameter which is available with working kernel version (2.6.35.9.*)
Created attachment 471708 [details]
output of modinfo dvb_usb_dib0700 when IR works fine
Note dvb_usb_dib0700_ir_proto parameter with earlier kernel (2.6.35.9.*) when IR is working fine
Created attachment 471712 [details]
evtest output of device when remote controller does not work (2.6.35.10.* kernel)
Created attachment 471714 [details]
evtest output of device when remote controller works fine (2.6.35.9.* kernel)
If needed I can generate more debugging information of this. I'm not sure if there is something to do with this and bug #665870 Hm, your evtest output suggests you've got a remote that speaks NEC Extended protocol, and neither of the rc-dib0700-* keymaps in the current kernel source are NEC Extended. Mauro, any idea what's missing here? I don't know the dib0700 code at all myself. Bah. Not quite sure how I managed to change the component or cc dwmw2. Fixing. Could you please modprobe dib0700 driver with debug=9 parameter, and attach the output to the BZ? (In reply to comment #5) > If needed I can generate more debugging information of this. > I'm not sure if there is something to do with this and bug #665870 Just for the record, pretty sure its a completely unrelated issue over in that bug. Created attachment 472710 [details]
modprobe dvb_usb_dib0700 debug=9 output with 2.6.35.10 kernel
dmesg output after modprobe dvb_usb_dib0700 debug=9
This is under 2.6.35.10-74 kernel when remote controller does not work
Created attachment 472711 [details]
modprobe dvb_usb_dib0700 debug=9 output with 2.6.35.9 kernel
dmesg output after command: modprobe dvb_usb_dib0700 debug=9
This is under 2.6.35.9-64 kernel when remote controller works.
Tommi, I'm not seeing any IR keypress on your logs. Did you press any key? They were catched by evtest but they didn't produce any logs? with the debug enabled? That's weird... Yes, I double checked it now. There are no text generated by key presses. Both kernels are similar with it. I do not know if I do something wrong. Like debug=9 has no effect at all. I'm seeing same problem with a Nova T 500 on a Debian (testing/squeeze) system. Remote works with the Debian supplied 2.6.32 kernel, but not with 2.6.35.x and 2.6.36.x kernels (and I think I tried a 2.6.37-rc kernel too). Tommi R: To get debugging messages from the dvb_usb drivers the kernel must be compiled with the CONFIG_DVB_USB_DEBUG option. I haven't posted debug output as my card is currently recording and I don't want to break it to reload the module with debug option. Will attempt to get debug output in 12 hours or so time. Created attachment 472891 [details]
Dmesg with dvb_usb_dib0700 debug on IR remote keypress
OK, output of dmesg when dvb_usb loaded with debug=49 and dvb_usb_dib0700 with debug=9. Produced on a Debian system with self compiled 2.6.36.3 kernel, however since this appears to be a problem in the kernel it should give you useful evidence. Dmesg ends with a number of IR remote keypresses (the OK and surrounding arrow keys). Keypresses are not getting out to userspace.
I see a similar problem reported with the HVR1110 in bug report 665870. I also have a PVR350 lying about somewhere, which I could plug into a system and test as well if it thought helpful.
(In reply to comment #15) > Created attachment 472891 [details] > Dmesg with dvb_usb_dib0700 debug on IR remote keypress > > OK, output of dmesg when dvb_usb loaded with debug=49 and dvb_usb_dib0700 with > debug=9. Produced on a Debian system with self compiled 2.6.36.3 kernel, > however since this appears to be a problem in the kernel it should give you > useful evidence. Dmesg ends with a number of IR remote keypresses (the OK and > surrounding arrow keys). Keypresses are not getting out to userspace. OK, those are the messages I was expecting: [ 214.180808] dib0700_rc_urb_completion() [ 214.180819] IR ID = 01 state = 01 System = 00 1E Cmd = 25 DA (len 6) [ 214.180824] RC5 protocol This means that dib0700 got the right protocol and properly received the scancode. From your evdev test: Event: time 1293579362.215167, type 4 (Misc), code 4 (ScanCode), value 1e003b It is clear that the protocol is RC-5 but, instead of using 0x1e3b, the driver is passing it wrong to rc-core (as 0x1e003b). The problem is that the keycode for RC-5 is using: keycode = poll_reply->system16 << 8 | poll_reply->data; instead of: keycode = poll_reply->system << 8 | poll_reply->data; I'll do some tests here and post a patch for it. > > I see a similar problem reported with the HVR1110 in bug report 665870. I also > have a PVR350 lying about somewhere, which I could plug into a system and test > as well if it thought helpful. Not related. This patch should fix the issue:
https://patchwork.kernel.org/patch/474391/
Thanks, IR remote now working. But I have noticed one other issue. On a warm reboot the remote fails to work. The following is seen in the kernel log in such a situation: Registered IR keymap rc-dib0700-rc5 input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:08.0/0000:01:07.2/usb3/3-1/rc/rc0/input4 rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:08.0/0000:01:07.2/usb3/3-1/rc/rc0 dvb-usb: schedule remote query interval to 50 msecs. dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. dib0700: rc submit urb failed It seems to always work correctly on a cold start so not a major problem. Patch merged in 2.6.35.10-78.fc14. kernel-2.6.35.11-83.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.11-83.fc14 kernel-2.6.35.11-83.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |