Boris Derzhavets
2010-Nov-06 10:59 UTC
[Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
Dmesg log is attached :-
[ 42.140012] WARNING: at lib/debugobjects.c:259 debug_print_object+0x5b/0x63()
[ 42.140012] Hardware name: System Product Name
[ 42.140012] ODEBUG: free active (active state 0) object type: percpu_counter
[ 42.140012] Modules linked in: ip6table_filter ip6_tables ebtable_nat
ebtables ipt_MASQUERADE iptable_nat nf_nat deflate zlib_deflate ctr camellia
cast5 rmd160 crypto_null ccm serpent blowfish twofish_generic twofish_x86_64
twofish_common ecb xcbc cbc sha256_generic sha512_generic des_generic cryptd
aes_x86_64 aes_generic ah6 ah4 esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4
xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro
xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp xfrm6_tunnel
tunnel6 af_key sunrpc bridge stp llc ipv6 evtchn xenfs uinput snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_intel r8169 mii snd_hda_codec snd_hwdep shpchp
snd_seq snd_seq_device snd_pcm microcode snd_timer iTCO_wdt i2c_i801
asus_atk0110 snd iTCO_vendor_support soundcore snd_page_alloc pata_acpi
firewire_ohci firewire_core ata_generic crc_itu_t pata_jmicron radeon ttm
drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded:
scsi_wait_scan]
[ 42.140012] Pid: 53, comm: kworker/u:6 Not tainted
2.6.37-0.1.rc1.git0.xendom0.fc14.x86_64 #1
[ 42.140012] Call Trace:
[ 42.140012] [<ffffffff81051d68>] warn_slowpath_common+0x85/0x9d
[ 42.140012] [<ffffffff81051e23>] warn_slowpath_fmt+0x46/0x48
[ 42.140012] [<ffffffff812573e9>] debug_print_object+0x5b/0x63
[ 42.140012] [<ffffffff81257c1f>] debug_check_no_obj_freed+0x99/0x18a
[ 42.140012] [<ffffffff8107d997>] ? arch_local_save_flags+0xb/0xd
[ 42.140012] [<ffffffff810822b4>] ?
debug_check_no_locks_freed+0x11c/0x138
[ 42.140012] [<ffffffff813f76b8>] ? net_free+0x2c/0x31
[ 42.140012] [<ffffffff81123804>] kmem_cache_free+0x6f/0x10b
[ 42.140012] [<ffffffff813f76b8>] net_free+0x2c/0x31
[ 42.140012] [<ffffffff813f7835>] cleanup_net+0x178/0x197
[ 42.140012] [<ffffffff81068d8f>] process_one_work+0x1f4/0x361
[ 42.140012] [<ffffffff81068cfb>] ? process_one_work+0x160/0x361
[ 42.140012] [<ffffffff813f76bd>] ? cleanup_net+0x0/0x197
[ 42.140012] [<ffffffff8106a1a8>] worker_thread+0x104/0x1a4
[ 42.140012] [<ffffffff8106a0a4>] ? worker_thread+0x0/0x1a4
[ 42.140012] [<ffffffff8106dbee>] kthread+0xa0/0xa8
[ 42.140012] [<ffffffff81082165>] ?
trace_hardirqs_on_caller+0x10b/0x12f
[ 42.140012] [<ffffffff8100ab64>] kernel_thread_helper+0x4/0x10
[ 42.140012] [<ffffffff814b23d0>] ? restore_args+0x0/0x30
[ 42.140012] [<ffffffff8100ab60>] ? kernel_thread_helper+0x0/0x10
[ 42.140012] ---[ end trace c2d2451e1a620a4f ]---
[ 42.140012] BUG: sleeping function called from invalid context at
kernel/mutex.c:278
[ 42.140012] in_atomic(): 0, irqs_disabled(): 1, pid: 53, name: kworker/u:6
[ 42.140012] 2 locks held by kworker/u:6/53:
[ 42.140012] #0: (netns){+.+.+.}, at: [<ffffffff81068cfb>]
process_one_work+0x160/0x361
[ 42.140012] #1: (net_cleanup_work){+.+.+.}, at: [<ffffffff81068cfb>]
process_one_work+0x160/0x361
[ 42.140012] irq event stamp: 7666
[ 42.140012] hardirqs last enabled at (7665): [<ffffffff81123756>]
kfree+0x11f/0x136
[ 42.140012] hardirqs last disabled at (7666): [<ffffffff811237cd>]
kmem_cache_free+0x38/0x10b
[ 42.140012] softirqs last enabled at (7620): [<ffffffff8141ea6c>]
netlink_release+0x1f3/0x208
[ 42.140012] softirqs last disabled at (7618): [<ffffffff8141ea54>]
netlink_release+0x1db/0x208
[ 42.140012] Pid: 53, comm: kworker/u:6 Tainted: G W
2.6.37-0.1.rc1.git0.xendom0.fc14.x86_64 #1
[ 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
[ 42.140012] [<ffffffff810822b4>] ?
debug_check_no_locks_freed+0x11c/0x138
[ 42.140012] [<ffffffff813f76b8>] ? net_free+0x2c/0x31
[ 42.140012] [<ffffffff81123804>] kmem_cache_free+0x6f/0x10b
[ 42.140012] [<ffffffff813f76b8>] net_free+0x2c/0x31
[ 42.140012] [<ffffffff813f7835>] cleanup_net+0x178/0x197
[ 42.140012] [<ffffffff81068d8f>] process_one_work+0x1f4/0x361
[ 42.140012] [<ffffffff81068cfb>] ? process_one_work+0x160/0x361
[ 42.140012] [<ffffffff813f76bd>] ? cleanup_net+0x0/0x197
[ 42.140012] [<ffffffff8106a1a8>] worker_thread+0x104/0x1a4
[ 42.140012] [<ffffffff8106a0a4>] ? worker_thread+0x0/0x1a4
[ 42.140012] [<ffffffff8106dbee>] kthread+0xa0/0xa8
[ 42.140012] [<ffffffff81082165>] ?
trace_hardirqs_on_caller+0x10b/0x12f
[ 42.140012] [<ffffffff8100ab64>] kernel_thread_helper+0x4/0x10
[ 42.140012] [<ffffffff814b23d0>] ? restore_args+0x0/0x30
[ 42.140012] [<ffffffff8100ab60>] ? kernel_thread_helper+0x0/0x10
Boris
--- On Fri, 11/5/10, M A Young <m.a.young@durham.ac.uk> wrote:
From: M A Young <m.a.young@durham.ac.uk>
Subject: [Fedora-xen] 2.6.37-rc1 dom0 kernel
To: xen@lists.fedoraproject.org
Date: Friday, November 5, 2010, 7:32 PM
I have built another test kernel (2.6.37-0.1.rc1.git0.xendom0.fc15) to
play with at http://koji.fedoraproject.org/koji/taskinfo?taskID=2581020 .
As with the previous kernel this is entirely based on the upstream kernel
and Fedora kernel patches, and is probably close to what the Fedora 15
kernel will look like soon. I haven''t tested it yet.
Michael Young
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Nov-07 13:43 UTC
[Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
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@durham.ac.uk> wrote: From: M A Young <m.a.young@durham.ac.uk> Subject: Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen@lists.fedoraproject.org, "xen-users" <xen-users@lists.xensource.com> 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Nov-07 14:28 UTC
Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
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@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: "M A Young" <m.a.young@durham.ac.uk> Cc: xen@lists.fedoraproject.org, "xen-users" <xen-users@lists.xensource.com> 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@durham.ac.uk> wrote: From: M A Young <m.a.young@durham.ac.uk> Subject: Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen@lists.fedoraproject.org, "xen-users" <xen-users@lists.xensource.com> 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Nov-07 16:25 UTC
Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
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@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: "M A Young" <m.a.young@durham.ac.uk> Cc: xen@lists.fedoraproject.org, "xen-users" <xen-users@lists.xensource.com> 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@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: "M A Young" <m.a.young@durham.ac.uk> Cc: xen@lists.fedoraproject.org, "xen-users" <xen-users@lists.xensource.com> 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@durham.ac.uk> wrote: From: M A Young <m.a.young@durham.ac.uk> Subject: Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen@lists.fedoraproject.org, "xen-users" <xen-users@lists.xensource.com> Date: Saturday, November 6, 2010, 9:29 AM On Sat, 6 Nov 2010, Boris Derzhavets wrote:> ... > [ 42.140012] CallTrace:>[ 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@lists.xensource.com http://lists.xensource.com/xen-users -----Inline Attachment Follows----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users