WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: Fw: Re: [Xen-devel] Problems with load the most recent 2.6.29-rc6 &

To: bderzhavets@xxxxxxxxx
Subject: Re: Fw: Re: [Xen-devel] Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium
From: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@xxxxxx>
Date: Wed, 04 Mar 2009 13:51:23 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, M A Young <m.a.young@xxxxxxxxxxxx>
Delivery-date: Wed, 04 Mar 2009 04:51:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <937768.2814.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <937768.2814.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello Boris,


i use a simple serial null modem cable to connect two serial ports on my
test machines with each other and did a simple "cat /dev/ttyS0 | tee
file.log" on the listening box to generate the logs.

Marc

Am Mittwoch, den 04.03.2009, 03:37 -0800 schrieb Boris Derzhavets:
> x86_64 build works for me on E8400 box and fails to load on Q9550
> box :-
> Black screen after Xen scrubbing for free RAM.
> I guess a kind of RS232 terminal is required to be connected to COM1
> to setup
> serial console. I am not sure may any converting cable to be used for
> connection
> to  Samsung 721N.
> Please, suggest any appropriate technical specifications or point to
> my misunderstanding of this procedure.
> 
> --- On Tue, 3/3/09, Marc - A. Dahlhaus <mad@xxxxxx> wrote:
>         From: Marc - A. Dahlhaus <mad@xxxxxx>
>         Subject: Re: Fw: Re: [Xen-devel] Problems with load the most
>         recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium
>         To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
>         Cc: bderzhavets@xxxxxxxxx, "Xen-devel"
>         <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ian Campbell"
>         <Ian.Campbell@xxxxxxxxxx>, "M A Young"
>         <m.a.young@xxxxxxxxxxxx>
>         Date: Tuesday, March 3, 2009, 7:11 PM
>         
>         Jeremy Fitzhardinge schrieb:
>         > M A Young wrote:
>         >> On Tue, 3 Mar 2009, M A Young wrote:
>         >> 
>         >>> If you need another reference point a kernel I build from
>         xen/dom0/hackery as of 25th Feb works.
>         >> 
>         >> Or more precisely up to and including changeset
>         55d8085671863fe4ee6a17b7814bd38180a44e1d
>         >>
>         
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=55d8085671863fe4ee6a17b7814bd38180a44e1d
>         
>         > 
>         > Thanks.  I make the breakage a bit more recent than that.  The 
> current
>         pushed xen/dom0/hackery boots for me now.
>         > 
>         >    J
>         Crashes for me on x86_32 with the same symptoms as in my last tests. 
> even the
>         backtraces are quite the same as the ones posted before.
>         I'll try
>          an x86_64 build tomorrow...
>         
>         Marc
>         
>         
>         _______________________________________________
>         Xen-devel mailing list
>         Xen-devel@xxxxxxxxxxxxxxxxxxx
>         http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>