[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Latest unstable detects cpu speed incorrectly
Hi,Forgot to mention that the domUs are Debian testing with XFS filesystem. You can find the bootlog from my previous postings. - Valtteri Kiviniemi Valtteri Kiviniemi kirjoitti: Hi,Compared to "nothing", just started to crash. Sometimes they boot and sometimes they dont. I did a full reboot for the server and now they are all working again without cpu spiking. The server was up only couple of days before this started, so I think that its going to start crashin in 48 hours or so.The problem is both tsc native and emulated. If the domUs wont crash, they just start to using 400-800% cpu when just idling.dmesg on Domain-0 is also flooding this: "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" - Valtteri Kiviniemi Jeremy Fitzhardinge kirjoitti:On 10/27/09 09:34, Valtteri Kiviniemi wrote:Hi, Now they are crashing on bootup:"Now" compared to what? Is this still related to tsc_native? Jgeneral protection fault: 0000 [#1] SMP last sysfs file: CPU 0 Pid: 1, comm: swapper Not tainted 2.6.31.4-domU-00396-g9cf89da #15 RIP: e030:[<ffffffff8119e25f>] [<ffffffff8119e25f>] strcmp+0x7/0x19 RSP: e02b:ffff88001f83be58 EFLAGS: 00010246 RAX: 0000000000000073 RBX: ffff88001fa1eb90 RCX: ffff88001fa1eb73 RDX: 0000000000000000 RSI: 0000b67d64d2a30e RDI: ffff88001f806900 RBP: 0000b67d64d2a30e R08: 0000000000000001 R09: ffffffff813c37c8 R10: ffffffff8100e072 R11: 0000000000000000 R12: 0000000000000000 R13: ffffffff81402030 R14: ffffffff8143f6a0 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000001001000 CR4: 0000000000002660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper (pid: 1, threadinfo ffff88001f83a000, task ffff88001f858000) Stack: ffffffff810c7e84 ffffffff8100e072 ffff88001fa1eb40 0000b67d64d2a30e <0> ffffffff810c6dc5 ffff88001fa1eb40 0000000000000000 0000000000000000 <0> 0000000000000000 0000b67d64d2a30e 00000000000274b2 0000000000000000 Call Trace: [<ffffffff810c7e84>] ? sysfs_find_dirent+0x1b/0x2f [<ffffffff8100e072>] ? check_events+0x12/0x20 [<ffffffff810c6dc5>] ? sysfs_hash_and_remove+0x29/0x59 [<ffffffff8107cecd>] ? sysfs_slab_alias+0x25/0x81 [<ffffffff81431a7d>] ? slab_sysfs_init+0xb6/0xe9 [<ffffffff814319c7>] ? slab_sysfs_init+0x0/0xe9 [<ffffffff8100a051>] ? do_one_initcall+0x50/0x151 [<ffffffff8141fb20>] ? kernel_init+0x14b/0x1a1 [<ffffffff810112aa>] ? child_rip+0xa/0x20 [<ffffffff810104ac>] ? int_ret_from_sys_call+0x7/0x1b [<ffffffff81010c5d>] ? retint_restore_args+0x5/0x6 [<ffffffff810112a0>] ? child_rip+0x0/0x20 Code: f8 eb 10 48 ff c1 49 ff c0 4c 39 c2 75 08 c6 01 00 eb 0d 45 31 c0 42 8a 04 06 88 01 84 c0 75 e3 48 89 f8 c3 31 d2 8a 0c 17 88 c8 <2a> 04 16 84 c0 75 07 48 ff c2 84 c9 75 ed 0f be c0 c3 31 c9 eb RIP [<ffffffff8119e25f>] strcmp+0x7/0x19 RSP <ffff88001f83be58> ---[ end trace a7919e7f17c0a725 ]--- Kernel panic - not syncing: Attempted to kill init!Pid: 1, comm: swapper Tainted: G D 2.6.31.4-domU-00396-g9cf89da #15Call Trace: [<ffffffff812b4993>] ? panic+0x86/0x12e [<ffffffff812b6919>] ? _spin_lock_irq+0x7/0x1c [<ffffffff811a5e20>] ? dummycon_dummy+0x0/0x3 [<ffffffff811a5e20>] ? dummycon_dummy+0x0/0x3 [<ffffffff8100d9bd>] ? xen_force_evtchn_callback+0x9/0xa [<ffffffff8100e072>] ? check_events+0x12/0x20 [<ffffffff811a5e20>] ? dummycon_dummy+0x0/0x3 [<ffffffff812b6995>] ? _write_lock_irq+0x7/0x16 [<ffffffff8103b2bd>] ? exit_ptrace+0xa7/0x126 [<ffffffff81036605>] ? do_exit+0x6a/0x5ce [<ffffffff8100e072>] ? check_events+0x12/0x20 [<ffffffff81013eb1>] ? oops_end+0x8e/0x93 [<ffffffff812b6d45>] ? general_protection+0x25/0x30 [<ffffffff8100e072>] ? check_events+0x12/0x20 [<ffffffff8119e25f>] ? strcmp+0x7/0x19 [<ffffffff810c7e84>] ? sysfs_find_dirent+0x1b/0x2f [<ffffffff8100e072>] ? check_events+0x12/0x20 [<ffffffff810c6dc5>] ? sysfs_hash_and_remove+0x29/0x59 [<ffffffff8107cecd>] ? sysfs_slab_alias+0x25/0x81 [<ffffffff81431a7d>] ? slab_sysfs_init+0xb6/0xe9 [<ffffffff814319c7>] ? slab_sysfs_init+0x0/0xe9 [<ffffffff8100a051>] ? do_one_initcall+0x50/0x151 [<ffffffff8141fb20>] ? kernel_init+0x14b/0x1a1 [<ffffffff810112aa>] ? child_rip+0xa/0x20 [<ffffffff810104ac>] ? int_ret_from_sys_call+0x7/0x1b [<ffffffff81010c5d>] ? retint_restore_args+0x5/0x6 [<ffffffff810112a0>] ? child_rip+0x0/0x20 - Valtteri Kiviniemi Valtteri Kiviniemi kirjoitti:Hi, It was downloaded and compiled on 2009-10-26 00:48 GMT+2. Kernel version is 2.6.31.4-dom0-00396-g9cf89da. - Valtteri Kiviniemi Keir Fraser kirjoitti:On 27/10/2009 16:14, "Valtteri Kiviniemi" <valtteri.kiviniemi@xxxxxxxxxxxx> wrote:I'll take that back, now its occuring in every virtual.Yes it didn't sound like it would really be TSC related. How 'latest' is your xen-unstable? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |