From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751174Ab0CXERb (ORCPT ); Wed, 24 Mar 2010 00:17:31 -0400 Received: from mail-gx0-f217.google.com ([209.85.217.217]:38725 "EHLO mail-gx0-f217.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750888Ab0CXERa convert rfc822-to-8bit (ORCPT ); Wed, 24 Mar 2010 00:17:30 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ftTv9qlO2htnFjtsTXaekbqdr1JcEiv+WGuVnxzXG//8zTcBuI7TQwcLW+9TdkvoR0 Neq6hmmF05EArde/NoQxrpMjZ+MMZLDCmp8Sm5qk+4gtTagA7OqAk5SJaXILfXp4nCOe bGiX0HL5OYIWgVmAzC3NdYUbNzqz54+vIPutk= MIME-Version: 1.0 In-Reply-To: <5712ce4f1003231735w33fb60a0h651c731fdbed747e@mail.gmail.com> References: <5712ce4f1003211947i1a2ac84ch269885f7c2888c4f@mail.gmail.com> <201003222224.47780.rjw@sisk.pl> <20100322212919.GB8941@lenovo> <5712ce4f1003231735w33fb60a0h651c731fdbed747e@mail.gmail.com> Date: Wed, 24 Mar 2010 07:17:28 +0300 Message-ID: Subject: Re: [Bug #15392] The kernel does not start up. From: Cyrill Gorcunov To: =?ISO-8859-1?Q?RALOVICH=2C_Krist=F3f?= Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Maciej Rutecki Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/24/10, RALOVICH, Kristóf wrote: > On Mon, Mar 22, 2010 at 17:29, Cyrill Gorcunov wrote: >> On Mon, Mar 22, 2010 at 10:24:47PM +0100, Rafael J. Wysocki wrote: >>> On Monday 22 March 2010, RALOVICH, Kristóf wrote: >>> > The issue is still there with 2.6.33-rc1, 2.6.33 and 2.6.33.1 too. >>> >>> Thanks for the update. >>> >>> Rafael >>> >>> >> [...] >> >> (Out of thread) >> >> Hi Kristóf, >> >> I don't have time to take a closer look on this bug >> but curious -- what will happen if you change compressing >> method to say bz2, instead of LZMA being used now? >> >> -- Cyrill >> > > I took a look: I tested 2.6.33.1 with bz2 instead of LZMA, the same > issue is still there. > > Kristof > Thanks, good to know