[opensuse-kernel] Debuginfo for x86_64 kernels (systemtap complaints about arch mismatch)
I'm trying to make systemtap work on 12.3 x86_64. Attempt to compile latencytap.stp from included examples gives bor@opensuse:/tmp> sudo stap latencytap.stp semantic error: ELF machine i?86| (code 3) mismatch with target x86_64 in '/usr/lib/debug/boot/vmlinux-3.7.10-1.11-desktop.debug' semantic error: while resolving probe point: identifier 'kernel' at latencytap.stp:51:7 source: kernel.function("deactivate_task") { ^ semantic error: no match semantic error: while resolving probe point: identifier 'kernel' at :62:7 source: kernel.function("activate_task") { ^ semantic error: while resolving probe point: identifier 'scheduler' at :81:7 source: probe scheduler.cpu_on { ^ Pass 2: analysis failed. Try again with another '--vp 01' option. Well, there is no debuginfo for x86_64, only for i586. Is it missing indeed or is it systemtap issue? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Andrey Borzenkov wrote:
I'm trying to make systemtap work on 12.3 x86_64. Attempt to compile latencytap.stp from included examples gives
I had the same problem in factory... Found a script that was developed to fix these problems, since apparently the interface is fairly fragile... Now where did that script go...(and come from)... I found the script but not sure where I D/led it from... might have been https://github.com/gormanm/mmtests/commits/master Maybe it would work for your case? Thought about submitting it back to this list for inclusion in the product. I dunno about the debug packages though -- as I built my own kernel w/debug turned on, and it just worked...
On Thu, Jun 13, 2013 at 11:12:07PM -0700, Linda Walsh wrote:
Andrey Borzenkov wrote:
I'm trying to make systemtap work on 12.3 x86_64. Attempt to compile latencytap.stp from included examples gives
I had the same problem in factory... Found a script that was developed to fix these problems, since apparently the interface is fairly fragile...
Now where did that script go...(and come from)...
I found the script but not sure where I D/led it from... might have been https://github.com/gormanm/mmtests/commits/master
That stap-fix.sh script in there is meant to handle internal differences in the kernel API when building custom kernels. It should never be necessary when working with distribution kernels. Looking at the error message it's far more likely the problem is that 64-bit kernel debug information is installed when the running kernel is 32-bit. -- Mel Gorman SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Fri, Jun 14, 2013 at 12:58 PM, Mel Gorman <mgorman@suse.de> wrote:
That stap-fix.sh script in there is meant to handle internal differences in the kernel API when building custom kernels. It should never be necessary when working with distribution kernels. Looking at the error message it's far more likely the problem is that 64-bit kernel debug information is installed when the running kernel is 32-bit.
Other way round :) I have 64 bit system but -debuginfo packages are available only for 32 bit. So runnig "zypper in kernel...-debuginfo" picked and installed 32 bit versions. I checked 12.2 and there -debuginfo packages are present for for both 32 and 64 bit. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 06/14/2013 04:16 AM, Andrey Borzenkov wrote:
On Fri, Jun 14, 2013 at 12:58 PM, Mel Gorman <mgorman@suse.de> wrote:
That stap-fix.sh script in there is meant to handle internal differences in the kernel API when building custom kernels. It should never be necessary when working with distribution kernels. Looking at the error message it's far more likely the problem is that 64-bit kernel debug information is installed when the running kernel is 32-bit.
Other way round :) I have 64 bit system but -debuginfo packages are available only for 32 bit. So runnig "zypper in kernel...-debuginfo" picked and installed 32 bit versions. I checked 12.2 and there -debuginfo packages are present for for both 32 and 64 bit.
My recollection was that it was a space issue. I think it should be fixed now/soon (for Factory) as there was a recent discussion on BS constraints that I think was the core issue. It's annoying that zypper will silently install the 32bit debuginfo (installed 64bit kernel) when 64bit debuginfo is missing. Anyhow, the core stap error is indeed because of the 32/64 mismatch. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 07/10/2013 10:30 PM, Tony Jones wrote:
On 06/14/2013 04:16 AM, Andrey Borzenkov wrote:
On Fri, Jun 14, 2013 at 12:58 PM, Mel Gorman <mgorman@suse.de> wrote:
That stap-fix.sh script in there is meant to handle internal differences in the kernel API when building custom kernels. It should never be necessary when working with distribution kernels. Looking at the error message it's far more likely the problem is that 64-bit kernel debug information is installed when the running kernel is 32-bit.
Other way round :) I have 64 bit system but -debuginfo packages are available only for 32 bit. So runnig "zypper in kernel...-debuginfo" picked and installed 32 bit versions. I checked 12.2 and there -debuginfo packages are present for for both 32 and 64 bit.
Please see https://bugzilla.novell.com/show_bug.cgi?id=824971 ... -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Mel Gorman wrote:
That stap-fix.sh script in there is meant to handle internal differences in the kernel API when building custom kernels. It should never be necessary when working with distribution kernels. Looking at the error message it's far more likely the problem is that 64-bit kernel debug information is installed when the running kernel is 32-bit.
So if he just built his own from the sources, it would solve the problem? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Fri, Jun 14, 2013 at 04:26:43PM -0700, Linda Walsh wrote:
Mel Gorman wrote:
That stap-fix.sh script in there is meant to handle internal differences in the kernel API when building custom kernels. It should never be necessary when working with distribution kernels. Looking at the error message it's far more likely the problem is that 64-bit kernel debug information is installed when the running kernel is 32-bit.
So if he just built his own from the sources, it would solve the problem?
Yes I would expect so, assuming he has CONFIG_DEBUG_INFO set and then either does a manual install (non-packaged build) or installs the resulting debuginfo package (packaged build with obs). I would hope/expect though that just downloading the correct debuginfo package is an easier option. -- Mel Gorman SUSE Labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (5)
-
Andrey Borzenkov -
Jiri Slaby -
Linda Walsh -
Mel Gorman -
Tony Jones