WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel

To: M A Young <m.a.young@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Sun, 7 Nov 2010 08:25:44 -0800 (PST)
Cc: xen@xxxxxxxxxxxxxxxxxxxxxxx, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 07 Nov 2010 08:27:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1289147144; bh=BXFbxb+QsyVAJccxhkG4Z0EQhP6SX18PAIQ627jZFQI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=5r8t/WVjzdJYfZPO+OUBL5k13/xWFyq/hS606Fg18FmcRGoY48JtgEfm9CBpm0Le6t6Cp2QmvC16bMHXfDOrkltZutd+FHPW37J9oMJKy9iupBviC1dpt2yQQ0rEuoX8DTxVrw7adZa7zB4oDMaFOiBHoJ0IbXONlTj3mu+fmCI=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=jokkcrcOTeihuBN9Nj8pvpnI71e6YxSLXpVXXjx8zuaZnRNmBEbfRfM4N8dNz1Z3IDL5BHkxek1fnXdrUux500nfHccbXgwMoKgbpu3xHB9bGMm0OVfDMlidm7KbPnidrD9faqL13Tvsxag1rCKp+C6Z72WJWhkB70P8+FrcqOs=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <978418.93469.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Done
. . . . . . .
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-headers-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-debuginfo-common-x86_64-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/perf-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-devel-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/kernel-debuginfo-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.vzYwPP
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd kernel-2.6.36.fc14
+ rm -rf /root/rpmbuild/BUILDROOT/kernel-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64
+ exit 0

--- On Sun, 11/7/10, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
To: "M A Young" <m.a.young@xxxxxxxxxxxx>
Cc: xen@xxxxxxxxxxxxxxxxxxxxxxx, "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, November 7, 2010, 9:28 AM

I've again tried to adjust kernel.spec from
kernel-2.6.37-0.1.rc1.git0.xendom0.fc15.src.rpm

to rcrev=1 ; gitrev=5

and build started OK.

Boris.

--- On Sun, 11/7/10, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
To: "M A Young" <m.a.young@xxxxxxxxxxxx>
Cc: xen@xxxxxxxxxxxxxxxxxxxxxxx, "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, November 7, 2010, 8:43 AM

I've tried to adjust kernel.spec from kernel-2.6.37-0.1.rc0.git13.xendom0.fc15.src.rpm
to rcrevision  = 1,  gitrevision =5
.....
# The rc snapshot level
%define rcrev 1
# The git snapshot level
%define gitrev 5
.....

Files patch-2.6.37-rc1.bz2,  patch-2.6.37-rc1-git5.bz2 have been copied to SOURCES
I get an error when attempt to build :-

# rpmbuild -bb ./kernel.spec

.......

Patch161: linux-2.6-i386-nx-emulation.patch
+ case "$patch" in
+ patch -p1 -F1 -s
+ ApplyPatch linux-2.6-32bit-mmap-exec-randomization.patch
+ local patch=linux-2.6-32bit-mmap-exec-randomization.patch
+ shift
+ '[' '!' -f /root/rpmbuild/SOURCES/linux-2.6-32bit-mmap-exec-randomization.patch ']'
Patch160: linux-2.6-32bit-mmap-exec-randomization.patch
+ case "$patch" in
+ patch -p1 -F1 -s
1 out of 5 hunks FAILED -- saving rejects to file mm/mmap.c.rej
error: Bad exit status from /var/tmp/rpm-tmp.FmT4Fy (%prep)


Boris.
P.S. I've also tried to adjust kernel.spec from
kernel-2.6.37-0.1.rc1.git0.xendom0.fc15.src.rpm
with results even worse then above:-
Patch32: linux-2.6-utrace-ptrace.patch failed to apply.

--- On Sat, 11/6/10, M A Young <m.a.young@xxxxxxxxxxxx> wrote:

From: M A Young <m.a.young@xxxxxxxxxxxx>
Subject: Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: xen@xxxxxxxxxxxxxxxxxxxxxxx, "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, November 6, 2010, 9:29 AM

On Sat, 6 Nov 2010, Boris Derzhavets wrote:

> ...
> [   42.140012] Call Trace:
> [   42.140012]  [<ffffffff810807a8>] ? print_irqtrace_events+0xa0/0xa4
> [   42.140012]  [<ffffffff81043256>] __might_sleep+0x103/0x108
> [   42.140012]  [<ffffffff814b0512>] mutex_lock_nested+0x25/0x43
> [   42.140012]  [<ffffffff8125ae02>] percpu_counter_destroy+0x3c/0x66
> [   42.140012]  [<ffffffff8125ae42>] percpu_counter_fixup_free+0x16/0x32
> [   42.140012]  [<ffffffff8125723b>] debug_object_fixup+0x1e/0x2b
> [   42.140012]  [<ffffffff81257c54>] debug_check_no_obj_freed+0xce/0x18a
> ...

This is probably a result of a percpu_counter bug in an IPv6 patch. As a temporary measure you can disable IPv6 (if you don't need it), eg. as suggested at http://fedorasolved.org/network-solutions/disable-ipv6

It was patched after rc1 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=41bb78b4b9adb21cf2c395b6b880aaae99c788b7
so should be fixed when I next do a build of 2.6.37 .

    Michael Young


-----Inline Attachment Follows-----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


-----Inline Attachment Follows-----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>