From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Marc - A. Dahlhaus" <mad@wol.de>
Subject: Re: Fw: Re: Problems with load the most recent 2.6.29-rc6
	&	Xen unstable on ASUS P5K Premium
Date: Tue, 03 Mar 2009 20:13:45 +0100
Message-ID: <49AD8169.5080301@wol.de>
References: <407160.22456.qm@web56101.mail.re3.yahoo.com>
	<49AD7DB3.3040207@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <49AD7DB3.3040207@goop.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: bderzhavets@yahoo.com, Xen-devel <xen-devel@lists.xensource.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

Jeremy Fitzhardinge schrieb:
> Boris Derzhavets wrote:
>> >I probably shouldn't have been operating machinery yesterday.
>> >The crash is probably because I committed the e820 memory 
>> rearranging >stuff into the wrong branch, but something may have 
>> broken us from >tip/master as well.
>> >   J
>>
>> Kernel was already broken at *2/28/09
>> *
>>
> Thanks, that's a useful reference.  I'm in the middle of a bisect at 
> the moment, so I should nail down what went wrong fairly soon.
>
>    J
The second test i did with console=ttyS0,9600n8 kernel param didn't show 
output from the kernel.

Marc