From mboxrd@z Thu Jan 1 00:00:00 1970 From: Valtteri Kiviniemi Subject: Re: Latest unstable detects cpu speed incorrectly Date: Tue, 27 Oct 2009 23:40:28 +0200 Message-ID: <4AE768CC.7080302@dataproof.fi> References: <4AE7208F.1090305@dataproof.fi> <4AE720FD.3020005@dataproof.fi> <4AE74E7E.4010301@goop.org> <4AE76886.1050309@dataproof.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AE76886.1050309@dataproof.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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? >> >> J >> >>> general 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:[] [] 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: >>> [] ? sysfs_find_dirent+0x1b/0x2f >>> [] ? check_events+0x12/0x20 >>> [] ? sysfs_hash_and_remove+0x29/0x59 >>> [] ? sysfs_slab_alias+0x25/0x81 >>> [] ? slab_sysfs_init+0xb6/0xe9 >>> [] ? slab_sysfs_init+0x0/0xe9 >>> [] ? do_one_initcall+0x50/0x151 >>> [] ? kernel_init+0x14b/0x1a1 >>> [] ? child_rip+0xa/0x20 >>> [] ? int_ret_from_sys_call+0x7/0x1b >>> [] ? retint_restore_args+0x5/0x6 >>> [] ? 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 [] strcmp+0x7/0x19 >>> RSP >>> ---[ 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 #15 >>> Call Trace: >>> [] ? panic+0x86/0x12e >>> [] ? _spin_lock_irq+0x7/0x1c >>> [] ? dummycon_dummy+0x0/0x3 >>> [] ? dummycon_dummy+0x0/0x3 >>> [] ? xen_force_evtchn_callback+0x9/0xa >>> [] ? check_events+0x12/0x20 >>> [] ? dummycon_dummy+0x0/0x3 >>> [] ? _write_lock_irq+0x7/0x16 >>> [] ? exit_ptrace+0xa7/0x126 >>> [] ? do_exit+0x6a/0x5ce >>> [] ? check_events+0x12/0x20 >>> [] ? oops_end+0x8e/0x93 >>> [] ? general_protection+0x25/0x30 >>> [] ? check_events+0x12/0x20 >>> [] ? strcmp+0x7/0x19 >>> [] ? sysfs_find_dirent+0x1b/0x2f >>> [] ? check_events+0x12/0x20 >>> [] ? sysfs_hash_and_remove+0x29/0x59 >>> [] ? sysfs_slab_alias+0x25/0x81 >>> [] ? slab_sysfs_init+0xb6/0xe9 >>> [] ? slab_sysfs_init+0x0/0xe9 >>> [] ? do_one_initcall+0x50/0x151 >>> [] ? kernel_init+0x14b/0x1a1 >>> [] ? child_rip+0xa/0x20 >>> [] ? int_ret_from_sys_call+0x7/0x1b >>> [] ? retint_restore_args+0x5/0x6 >>> [] ? 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" >>>>> >>>>> 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@lists.xensource.com >>>>> http://lists.xensource.com/xen-devel >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> http://lists.xensource.com/xen-devel >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >>> >> >