On Wed, 2009-09-30 at 12:57 +0200, Jean Delvare wrote: > Hi Pawel, > > I am removing the linux-i2c list from Cc, because it seems clear that > your problem is related to specific media drivers and not the i2c > subsystem. > > On Wed, 30 Sep 2009 10:16:15 +0200, Paweł Sikora wrote: > > 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. > > > i've attached asm dump of ir-common.ko > > i found the '41 c7 80 cc ...' code in dump at adress 0x83e. > > Not sure why you look at address 0x83e? The stack trace says +0x64. As > function ir_input_init() starts at 0x800, the oops address would be > 0x864, which is: > > 864: f0 0f ab 31 lock bts %esi,(%rcx) > > If my disassembler skills are still worth anything, this corresponds to > the set_bit instruction in: > > for (i = 0; i < IR_KEYTAB_SIZE; i++) > set_bit(ir->ir_codes[i], dev->keybit); > > in the source code. This suggests that ir->ir_codes is smaller than > expected (sounds unlikely as this array is included in struct > ir_input_state) or dev->keybit isn't large enough (sounds unlikely as > well, it should be large enough to contain 0x300 bits while ir keycodes > are all below 0x100.) So most probably something went wrong before and > we're only noticing now. Jean, You should be aware that the type of ir_codes changed recently from IR_KEYTAB_TYPE to struct ir_scancode_table * I'm not sure if it is the problem here, but it may be prudent to check that there's no mismatch between the module and the structure definitions being pulled in via "#include" (maybe by stopping gcc after the preprocessing with -E ). Regards, Andy > 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? > At this point, all I can offer is instrumenting ir_probe() and > ir_input_init() with log messages to see exactly what code paths are > taken and what parameters are passed around. > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
