From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: strange guest slowness after some time Date: Wed, 18 Mar 2009 00:02:19 +0100 Message-ID: <49C02BFB.3050902@wpkg.org> References: <49B29705.6000904@wpkg.org> <49B4E7A6.3090601@redhat.com> <49B4EDC9.9020504@wpkg.org> <49B4EE8F.7050001@redhat.com> <49BD007C.9030809@wpkg.org> <49BF7FB6.9080503@wpkg.org> <49BF8686.5050707@redhat.com> <49BF88BE.7040805@wpkg.org> <49BFC276.1080600@gmx.net> <49BFC743.20000@redhat.com> <49BFCC04.9080402@wpkg.org> <49BFD84F.8050509@gmx.net> <49BFD999.503@redhat.com> <49BFE146.2090308@wpkg.org> <49BFF20D.6010303@wpkg.org> <49BFF45A.5070307@gmx.net> <49BFF8D2.5080000@wpkg.org> <49C00495.3060105@wpkg.org> <49C02563.8020702@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org To: Felix Leimbach Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:54812 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751970AbZCQXCZ (ORCPT ); Tue, 17 Mar 2009 19:02:25 -0400 In-Reply-To: <49C02563.8020702@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski schrieb: > Tomasz Chmielewski schrieb: > >> Sorry, both machines run Debian Lenny and 2.6.26 kernel. >> The only difference is that machine which crashes (with MTU=100) or >> locks up (with MTU=1500) runs a "2.6.26-1-686" kernel and the one >> which doesn't lock up runs "2.6.26-1-486" kernel (both are Debian's >> kernels). > > Some more tries and I got this one. Serial console died, but SSH is > still working. > > Note the "S" tainted flag. > According to Documentation/oops-tracing.txt, it means: > > 3: 'S' if the oops occurred on an SMP kernel running on hardware that > hasn't been certified as safe to run multiprocessor. > Currently this occurs only on various Athlons that are not > SMP capable. > > > And this is a difference between "2.6.26-1-686" and "2.6.26-1-486" kernels. > > # grep -i smp /boot/config-2.6.26-1-686 > CONFIG_X86_SMP=y > CONFIG_X86_32_SMP=y > CONFIG_SMP=y > > > # grep -i smp /boot/config-2.6.26-1-486 > CONFIG_BROKEN_ON_SMP=y > # CONFIG_SMP is not set BTW, it was the machine with /boot/config-2.6.26-1-486 kernel (non-SMP) which got slow for me today. -- Tomasz Chmielewski http://wpkg.org