From: Robert V. <rob...@pr...> - 2003-08-08 15:07:15
|
I cannot load oprofile module. I think my kernel differs in those 32-bit suffixes, but I don't know how to list symbols in my current kernel, so I cannot verify it. My kernel sources match running kernel, but I doubt I've got the configuration exactly the same. What else should I look at besides SMP that I have already fixed? depmod: *** Unresolved symbols in /lib/modules/2.4.18-386/oprofile/oprofile.o depmod: unregister_sysctl_table_Rd14f2b30 depmod: fget_R26658d4d depmod: mem_map_R22d9a713 depmod: remove_wait_queue_Rb7355d75 depmod: init_mm_R33601568 depmod: fput_R607dfd1c depmod: proc_dointvec_R014986a0 depmod: __mntput_Rf10d2347 depmod: register_sysctl_table_R1da08d15 depmod: rwsem_wake depmod: add_wait_queue_R3ed1ea8a depmod: register_chrdev_Rc017d46d depmod: rwsem_down_read_failed depmod: dput_Rab917c47 |
From: John L. <le...@mo...> - 2003-08-08 15:25:31
|
On Fri, Aug 08, 2003 at 05:07:03PM +0200, Robert Vazan wrote: > I cannot load oprofile module. I think my kernel differs in those 32-bit > suffixes, but I don't know how to list symbols in my current kernel, so I > cannot verify it. My kernel sources match running kernel, but I doubt I've > got the configuration exactly the same. What else should I look at besides > SMP that I have already fixed? modversions. The best way to sort out your problem is to build a kernel, run that kernel, then point oprofile to those sources without changing anything. Then it's guaranteed to match john -- Khendon's Law: If the same point is made twice by the same person, the thread is over. |
From: Robert V. <rob...@pr...> - 2003-08-14 10:21:19
|
On Fri, 8 Aug 2003 16:21:25 +0100 John Levon <le...@mo...> wrote: > On Fri, Aug 08, 2003 at 05:07:03PM +0200, Robert Vazan wrote: > > > I cannot load oprofile module. I think my kernel differs in those > 32-bit > > suffixes, but I don't know how to list symbols in my current kernel, > so I > > cannot verify it. My kernel sources match running kernel, but I doubt > I've > > got the configuration exactly the same. What else should I look at > besides > > SMP that I have already fixed? > > modversions. The best way to sort out your problem is to build a kernel, > run that kernel, then point oprofile to those sources without changing > anything. Then it's guaranteed to match Well, it does work, but oprofile website claims that "No kernel patch is needed - just insert the module". I've even found original configuration in /boot and followed original packager's steps, but there is still some difference. |
From: John L. <le...@mo...> - 2003-08-14 12:37:24
|
On Thu, Aug 14, 2003 at 12:14:33PM +0200, Robert Vazan wrote: > Well, it does work, but oprofile website claims that "No kernel patch is > needed - just insert the module". I've even found original configuration No patch is needed. You passed kernel sources + config that do not match the running kernel, the problem was on your end somehow. regards john -- Khendon's Law: If the same point is made twice by the same person, the thread is over. |
From: Philippe E. <ph...@wa...> - 2003-08-14 14:36:29
|
Robert Vazan wrote: > On Fri, 8 Aug 2003 16:21:25 +0100 John Levon <le...@mo...> > wrote: > > >>On Fri, Aug 08, 2003 at 05:07:03PM +0200, Robert Vazan wrote: [module versioning problem] >> >>modversions. The best way to sort out your problem is to build a kernel, >>run that kernel, then point oprofile to those sources without changing >>anything. Then it's guaranteed to match > > > Well, it does work, but oprofile website claims that "No kernel patch is > needed - just insert the module". I've even found original configuration > in /boot and followed original packager's steps, but there is still some > difference. oprofile needs a kernel tree configured as was configured the running kernel, I suspect you had the right config in /boot but your kernel tree was no longer configured for this .config (we don't use .config file but we need a few .h generated in the kernel tree which must match the running kernel) Note also when we talk about kernel tree, we talk about vanilla kernel not kernel-2.4.20-xyz patched by distro foo-bar. Don't get it as a critics about distro foo-bar, we just can't track all change by various distro/ distro version. regards, Philippe Elie |