From: "zhenzhong.duan" <zhenzhong.duan@oracle.com>
To: Josh Stone <jistone@redhat.com>
Cc: systemtap@sourceware.org, k-yui@bs1.jp.nec.com
Subject: Re: Build-id mismatch: "kernel" vs. "vmlinux" byte 0 (0x82 vs 0x47)
Date: Tue, 24 Jul 2012 06:10:00 -0000 [thread overview]
Message-ID: <500E3C4B.1090204@oracle.com> (raw)
In-Reply-To: <500E2B60.5090403@redhat.com>
Hi Josh,
thanks for your comment.
>> I'm sure kernel and debuginfo match eath other.
>> Linux version 2.6.39-200.29.2.el6uek.x86_64
>> (mockbuild@ca-build44.us.oracle.com) (gcc version 4.4.6 20110731 (Red
>> Hat 4.4.6-3) (GCC) ) #1 SMP Sat Jul 14 10:50:56 EDT 2012
> Unfortunately, it is still possible for these to be mismatched, even if
> the version strings are identical. In order for the Build IDs to match,
> the packages must come from the exact same compilation run. One clue to
> check this is the "Build Date" information in the rpms, which you may
> find with this command:
>
> rpm -qif /boot/vmlinuz-2.6.39-200.29.2.el6uek.x86_64 \
> /usr/lib/debug/lib/modules/2.6.39-200.29.2.el6uek.x86_64/vmlinux
>
> It probably won't match the exact "10:50:56 EDT" time given in your
> kernel string, but rather some time after that when the rpms are
> actually written. The kernel and kernel-debuginfo rpms should be the
> same build date and time as each other though.
>
> Hope this helps, and let us know what that says.
>
> Josh
As you predict, kernel string/kernel-uek pkg/kernel-uek-debuginfo pkg's
time signature are all different.
In fact, 2.6.39-200.29.2.el6uek are a variant of upstream 3.2.5 or
later. So this maybe an upstream issue.
[root@zhenzhong1 ~]# rpm -qif /boot/vmlinuz-2.6.39-200.29.2.el6uek.x86_64 \
> /usr/lib/debug/lib/modules/2.6.39-200.29.2.el6uek.x86_64/vmlinux
Name : kernel-uek Relocations: (not relocatable)
Version : 2.6.39 Vendor: Oracle America
Release : 200.29.2.el6uek Build Date: Sat 14 Jul 2012
11:33:03 AM EDT
Install Date: Fri 20 Jul 2012 04:52:29 AM EDT Build Host:
ca-build44.us.oracle.com
Group : System Environment/Kernel Source RPM:
kernel-uek-2.6.39-200.29.2.el6uek.src.rpm
Size : 103285531 License: GPLv2
Signature : RSA/8, Sat 14 Jul 2012 11:50:15 AM EDT, Key ID
72f97b74ec551f03
URL : http://www.kernel.org/
Summary : The Linux kernel
...
Name : kernel-uek-debuginfo Relocations: (not relocatable)
Version : 2.6.39 Vendor: Oracle America
Release : 200.29.2.el6uek Build Date: Sat 14 Jul 2012
11:33:03 AM EDT
Install Date: Mon 23 Jul 2012 05:40:40 AM EDT Build Host:
ca-build44.us.oracle.com
Group : Development/Debug Source RPM:
kernel-uek-2.6.39-200.29.2.el6uek.src.rpm
Size : 1553026121 License: GPLv2
Signature : RSA/8, Sat 14 Jul 2012 11:50:02 AM EDT, Key ID
72f97b74ec551f03
URL : http://www.kernel.org/
Summary : Debug information for package kernel-uek
next prev parent reply other threads:[~2012-07-24 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 3:06 zhenzhong.duan
2012-07-24 4:58 ` Josh Stone
2012-07-24 6:10 ` zhenzhong.duan [this message]
2012-07-24 16:21 ` Josh Stone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=500E3C4B.1090204@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=jistone@redhat.com \
--cc=k-yui@bs1.jp.nec.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).