On Sun, 13 Feb 2005 at 01:07 +0000, Lee Revell wrote:
> Are there any known incompatibilities with oprofile and the RT preempt patch?
>
> Lee
>
> Oops: 0000 [#1]
> PREEMPT
> alloc
> CPU: 0
> EIP: 0060:[oprofilefs_str_to_user+21/64] Not tainted VLI
> EFLAGS: 00010246 (2.6.11-rc2-RT-V0.7.37-01)
> EIP is at oprofilefs_str_to_user+0x15/0x40
> eax: 00000000 ebx: 00000000 ecx: ffffffff edx: 00000000
> esi: d593b6a0 edi: 00000000 ebp: cb966f6c esp: cb966f68
> ds: 007b es: 007b ss: 0068 preempt: 00000001
> Process cat (pid: 3290, threadinfo=cb966000 task=d083ce10)
> Stack: cb966fa8 cb966f90 c01529ec 00000000 0804d038 00001000 cb966fa8
> d593b6a0
> fffffff7 0804d038 cb966fbc c0152cc1 d593b6a0 0804d038 00001000
> cb966fa8
> 00000000 00000000 00000000 00000003 00001000 cb966000 c01026a4
> 00000003
oprofile_files.c:
oprofilefs_str_to_user(oprofile_ops.cpu_type, buf, count, offset);
oprofilefs.c:
ssize_t oprofilefs_str_to_user(char const * str, char __user * buf,
size_t count, loff_t * offset)
{
return simple_read_from_buffer(buf, count, offset, str, strlen(str));
}
oprofile_ops.cpu_type == NULL, this has been fixed 3 weeks ago,
can you retry with -rc4 ?
Philippe Elie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
