Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753922Ab1DNWDo (ORCPT ); Thu, 14 Apr 2011 18:03:44 -0400 Received: from mail-gy0-f174.google.com ([209.85.160.174]:49358 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752901Ab1DNWDk (ORCPT ); Thu, 14 Apr 2011 18:03:40 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=weFeozT0386LDUmKL80zri3lJuFXZaFvJEUOA1iyjSKBZovpDML4/dpSzkrAf/YOUR bXGJ0V6vzd5D2Yzh7aSJvZ2yR3xlDLuNELlnQ7SvdH7A8MS1d19Cg3+gb3Qe/aqWgicu SJwnlZbQ0vg3eUEhSUbJEC+NnSXpeAz2kcmhI= MIME-Version: 1.0 In-Reply-To: <4DA75EA9.4050602@ece.ntua.gr> References: <4DA75EA9.4050602@ece.ntua.gr> Date: Thu, 14 Apr 2011 19:03:39 -0300 X-Google-Sender-Auth: LnfcrMq12VBVAYYi3AQ0iDxXFzk Message-ID: Subject: Re: [REGRESSION] 2.6.32.36 - Linux Xen DomU doesn't boot anymore From: "guilherme m. schroeder" To: Stratos Psomadakis Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1041 Lines: 25 On Thu, Apr 14, 2011 at 5:52 PM, Stratos Psomadakis wrote: > Can you try 2.6.32.37-rc1? > The patch you're referring to was committed I think along with another > patch which caused some trouble in the -stable trees(I'm not surea bout > that though :/). > And in 2.6.32.37-rc1 it was reverted: > [59/74] [PATCH] Revert "x86: Cleanup highmap after brk is concluded" > Maybe it fixes your problem. > > -- > Stratos Psomadakis > No problem with 2.6.32.37-rc1. Do I need to bisect 2.6.32.37-rc1 against 2.6.32.36 to make sure it is the patch that you mentioned? And if we find it, there'll be a 2.6.32.36.1 release or we need to wait for 2.6.32.37? I'm asking this because some distros are already taking 2.6.32.36 (Debian 6.0 proposed kernel for example). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/