From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Campbell Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39 Date: Tue, 31 May 2011 17:26:10 +0800 Message-ID: <4DE4B432.1090203@fnarfbargle.com> References: <4DE44333.9000903@fnarfbargle.com> <20110531054729.GA16852@liondog.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: Borislav Petkov , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-mm Return-path: In-Reply-To: <20110531054729.GA16852@liondog.tnic> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 31/05/11 13:47, Borislav Petkov wrote: > Looks like a KSM issue. Disabling CONFIG_KSM should at least stop your > machine from oopsing. > > Adding linux-mm. > I initially thought that, so the second panic was produced with KSM disabled from boot. echo 0 > /sys/kernel/mm/ksm/run If you still think that compiling ksm out of the kernel will prevent it then I'm willing to give it a go. It's a production server, so I can only really bounce it around after about 9PM - GMT+8. Regards, Brad