Re: [2.6.31] ir-kbd-i2c oops.
On Sunday 04 October 2009 00:52:18 Hermann Pitton wrote: Hi, Am Samstag, den 03.10.2009, 21:09 +0200 schrieb Paweł Sikora: On Saturday 03 October 2009 20:15:27 Jean Delvare wrote: moreover, with this patch i'm observing a flood in dmesg: [ 938.313245] i2c IR (Pinnacle PCTV): unknown key: key=0x12 raw=0x12 down=1 [ 938.419914] i2c IR (Pinnacle PCTV): unknown key: key=0x12 raw=0x12 down=0 [ 939.273249] i2c IR (Pinnacle PCTV): unknown key: key=0x24 raw=0x24 down=1 [ 939.379955] i2c IR (Pinnacle PCTV): unknown key: key=0x24 raw=0x24 down=0 Different issue, and I don't know much about IR support, but these keys aren't listed in ir_codes_pinnacle_color. Maybe you have a different variant of this remote control with more keys and we need to add their definitions. i have such one: http://imgbin.org/index.php?page=imageid=812 hm, maybe it is some fake Pinnacle stuff, at least that remote is very different from the supported ones with gray only or colored keys and looks very poor. i have pinnacle pctv analog pci 110i: http://imgbin.org/index.php?page=imageid=813 05:00.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) Subsystem: Pinnacle Systems Inc. PCTV 110i (saa7133) Flags: bus master, medium devsel, latency 64, IRQ 16 Memory at febff800 (32-bit, non-prefetchable) [size=2K] Capabilities: [40] Power Management version 2 Kernel driver in use: saa7134 Kernel modules: saa7134 05:00.0 0480: 1131:7133 (rev d1) -- 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: [2.6.31] ir-kbd-i2c oops.
On Saturday 03 October 2009 20:15:27 Jean Delvare wrote: moreover, with this patch i'm observing a flood in dmesg: [ 938.313245] i2c IR (Pinnacle PCTV): unknown key: key=0x12 raw=0x12 down=1 [ 938.419914] i2c IR (Pinnacle PCTV): unknown key: key=0x12 raw=0x12 down=0 [ 939.273249] i2c IR (Pinnacle PCTV): unknown key: key=0x24 raw=0x24 down=1 [ 939.379955] i2c IR (Pinnacle PCTV): unknown key: key=0x24 raw=0x24 down=0 Different issue, and I don't know much about IR support, but these keys aren't listed in ir_codes_pinnacle_color. Maybe you have a different variant of this remote control with more keys and we need to add their definitions. i have such one: http://imgbin.org/index.php?page=imageid=812 Which keys are triggering these messages? this is the funny thing because i'm not pressing any keys at all. the remote control is unused currently becasue i'm using only pinnacle svideo input for watching sat-tv with tvtime. -- 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: [2.6.31] ir-kbd-i2c oops.
On Tuesday 29 September 2009 16:16:29 Jean Delvare wrote:
On Wed, 16 Sep 2009 10:03:32 +0200, Paweł Sikora wrote:
On Wednesday 16 September 2009 08:57:01 Jean Delvare wrote:
Hi Pawel,
I think this would be fixed by the following patch:
http://patchwork.kernel.org/patch/45707/
still oopses. this time i've attached full dmesg.
Any news on this? Do you have a refined list of kernels which have the
bug and kernels which do not?
afaics in the 2.6.2{7,8}, the remote sends some noises to pc.
effect: random characters on terminal and unusable login prompt.
now in the 2.6.31, the kernel module oopses during udev loading.
so i've renamed the .ko to prevent loading.
Tried 2.6.32-rc1? Tried the v4l-dvb repository?
no.
I am also skeptical about the +0x64/0x1a52, ir_input_init() is a rather
small function and I fail to see how it could be 6738 bytes in binary size.
i've attached asm dump of ir-common.ko
i found the '41 c7 80 cc ...' code in dump at adress 0x83e.
ir-common.ko: file format elf64-x86-64
Disassembly of section .text:
ir_extract_bits:
0: 31 c0 xor%eax,%eax
2: ba 01 00 00 00 mov$0x1,%edx
7: eb 09 jmp12 ir_extract_bits+0x12
9: 0f 1f 80 00 00 00 00nopl 0x0(%rax)
10: d1 ef shr%edi
12: 40 f6 c6 01 test $0x1,%sil
16: 74 0d je 25 ir_extract_bits+0x25
18: 89 c1 mov%eax,%ecx
1a: 09 d1 or %edx,%ecx
1c: 40 f6 c7 01 test $0x1,%dil
20: 0f 45 c1cmovne %ecx,%eax
23: 01 d2 add%edx,%edx
25: d1 ee shr%esi
27: 75 e7 jne10 ir_extract_bits+0x10
29: f3 c3 repz retq
2b: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
0030 ir_decode_pulsedistance:
30: 41 55 push %r13
32: c1 e6 05shl$0x5,%esi
35: 85 f6 test %esi,%esi
37: 41 54 push %r12
39: 55 push %rbp
3a: 53 push %rbx
3b: 89 cb mov%ecx,%ebx
3d: 7e 58 jle97 ir_decode_pulsedistance+0x67
3f: 31 c0 xor%eax,%eax
41: 45 31 c0xor%r8d,%r8d
44: 41 bb 1f 00 00 00 mov$0x1f,%r11d
4a: 41 ba 01 00 00 00 mov$0x1,%r10d
50: eb 12 jmp64 ir_decode_pulsedistance+0x34
52: 66 0f 1f 44 00 00 nopw 0x0(%rax,%rax,1)
58: 41 83 c0 01 add$0x1,%r8d
5c: 83 c0 01add$0x1,%eax
5f: 41 39 f0cmp%esi,%r8d
62: 7d 33 jge97 ir_decode_pulsedistance+0x67
64: 44 89 c1mov%r8d,%ecx
67: 45 89 c1mov%r8d,%r9d
6a: 44 89 ddmov%r11d,%ebp
6d: 83 e1 1fand$0x1f,%ecx
70: 41 c1 f9 05 sar$0x5,%r9d
74: 45 89 d5mov%r10d,%r13d
77: 29 cd sub%ecx,%ebp
79: 4d 63 c9movslq %r9d,%r9
7c: 89 e9 mov%ebp,%ecx
7e: 41 d3 e5shl%cl,%r13d
81: 46 85 2c 8f test %r13d,(%rdi,%r9,4)
85: 75 d1 jne58 ir_decode_pulsedistance+0x28
87: 83 f8 1ccmp$0x1c,%eax
8a: 7f 1c jg a8 ir_decode_pulsedistance+0x78
8c: 41 83 c0 01 add$0x1,%r8d
90: 31 c0 xor%eax,%eax
92: 41 39 f0cmp%esi,%r8d
95: 7c cd jl 64 ir_decode_pulsedistance+0x34
97: b8 ff ff ff ff mov$0x,%eax
9c: 5b pop%rbx
9d: 5d pop%rbp
9e: 41 5c pop%r12
a0: 41 5d pop%r13
a2: c3 retq
a3: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
a8: 41 39 f0cmp%esi,%r8d
ab: 7d ea jge97 ir_decode_pulsedistance+0x67
ad: 31 c0 xor%eax,%eax
af: 41 bb 1f 00 00 00 mov$0x1f,%r11d
b5: 41 ba 01 00 00 00 mov$0x1,%r10d
bb: eb 26 jmpe3 ir_decode_pulsedistance+0xb3
bd: 0f 1f 00nopl (%rax)
c0: 44 89 c1mov%r8d,%ecx
c3: 45 89 c1mov%r8d,%r9d
c6: 44 89 ddmov%r11d,%ebp
c9: 83 e1 1fand$0x1f,%ecx
cc: 41 c1 f9 05 sar$0x5,%r9d
d0: 45 89 d5mov%r10d,%r13d
d3: 29 cd sub%ecx,%ebp
d5: 4d 63 c9movslq %r9d,%r9
d8: 89 e9
Re: [2.6.31] ir-kbd-i2c oops.
On Wednesday 30 September 2009 12:57:37 Jean Delvare wrote: Are you running distribution kernels or self-compiled ones? Any local patches applied? Would you be able to apply debug patches and rebuild your kernel? yes, i'm using patched (vserver,grsec) modular kernel from pld-linux but i'm able to boot custom git build and do the bisect if necessary. -- 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: [2.6.31] ir-kbd-i2c oops.
On Wednesday 16 September 2009 08:57:01 Jean Delvare wrote: Hi Pawel, I think this would be fixed by the following patch: http://patchwork.kernel.org/patch/45707/ still oopses. this time i've attached full dmesg. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.31-0.4 (pl...@pldmachine) (gcc version 4.4.1 20090724 (release) (PLD-Linux) ) #1 SMP Wed Sep 16 09:45:40 CEST 2009 [0.00] Command line: root=/dev/md0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009cc00 (usable) [0.00] BIOS-e820: 0009cc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - cff7 (usable) [0.00] BIOS-e820: cff7 - cff7e000 (ACPI data) [0.00] BIOS-e820: cff7e000 - cffd (ACPI NVS) [0.00] BIOS-e820: cffd - d000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00023000 (usable) [0.00] DMI present. [0.00] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] last_pfn = 0x23 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-D write-protect [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask E write-back [0.00] 1 base 2 mask FE000 write-back [0.00] 2 base 22000 mask FF000 write-back [0.00] 3 base 0D000 mask FF000 uncachable [0.00] 4 base 0E000 mask FE000 uncachable [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820 update range: d000 - 0001 (usable) == (reserved) [0.00] last_pfn = 0xcff70 max_arch_pfn = 0x4 [0.00] Scanning 0 areas for low memory corruption [0.00] modified physical RAM map: [0.00] modified: - 0001 (reserved) [0.00] modified: 0001 - 0009cc00 (usable) [0.00] modified: 0009cc00 - 000a (reserved) [0.00] modified: 000e4000 - 0010 (reserved) [0.00] modified: 0010 - cff7 (usable) [0.00] modified: cff7 - cff7e000 (ACPI data) [0.00] modified: cff7e000 - cffd (ACPI NVS) [0.00] modified: cffd - d000 (reserved) [0.00] modified: fee0 - fee01000 (reserved) [0.00] modified: fff0 - 0001 (reserved) [0.00] modified: 0001 - 00023000 (usable) [0.00] initial memory mapped : 0 - 2000 [0.00] init_memory_mapping: -cff7 [0.00] NX (Execute Disable) protection: active [0.00] 00 - 00cfe0 page 2M [0.00] 00cfe0 - 00cff7 page 4k [0.00] kernel direct mapping tables up to cff7 @ 1-16000 [0.00] init_memory_mapping: 0001-00023000 [0.00] NX (Execute Disable) protection: active [0.00] 01 - 023000 page 2M [0.00] kernel direct mapping tables up to 23000 @ 11000-1b000 [0.00] RAMDISK: 37f5 - 37fefb03 [0.00] ACPI: RSDP 000fb460 00024 (v02 ACPIAM) [0.00] ACPI: XSDT cff70100 0005C (v01 A_M_I_ OEMXSDT 08000820 MSFT 0097) [0.00] ACPI: FACP cff70290 000F4 (v03 A_M_I_ OEMFACP 08000820 MSFT 0097) [0.00] ACPI: DSDT cff70440 0964B (v01 A1012 A1012001 0001 INTL 20060113) [0.00] ACPI: FACS cff7e000 00040 [0.00] ACPI: APIC cff70390 0006C (v01 A_M_I_ OEMAPIC 08000820 MSFT 0097) [0.00] ACPI: MCFG cff70400 0003C (v01 A_M_I_ OEMMCFG 08000820 MSFT 0097) [0.00] ACPI: OEMB cff7e040 00081 (v01 A_M_I_ AMI_OEM 08000820 MSFT 0097) [0.00] ACPI: HPET cff79a90 00038 (v01 A_M_I_ OEMHPET 08000820 MSFT 0097) [0.00] ACPI: OSFR
