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-ia64-devel

Re: [Xen-ia64-devel] Weekly Xen-IA64/VTI status report.

To: "You, Yongkang" <yongkang.you@xxxxxxxxx>, "xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Weekly Xen-IA64/VTI status report.
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Fri, 31 Mar 2006 13:16:52 +0100
Delivery-date: Fri, 31 Mar 2006 12:14:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <16A54BF5D6E14E4D916CE26C9AD30575044A20CA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <16A54BF5D6E14E4D916CE26C9AD30575044A20CA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Vendredi 31 Mars 2006 12:34, You, Yongkang a écrit :
[...]
More comments.
> I also rerun some failed LTP cases in Xen0. The results are:.
>
> proc01 couldn't finish and return for more than 1 hour. I have to break it.
> proc01        0       INFO: /proc/sa1/cpe/data: open: Cannot allocate memory
> proc01        1       BROK : Unexpected signal 2 received.
This test reads all files in /proc.  I will try to fix the issue.

> fork12 will hang xen0 after run in 30 mins. Serial port kept report soft
> lockup detected on CPU#0 and call trace.
Look also very bad with bare iron linux.

> And another 2 system call cases madvise02 and setrlimit03 also failed. The
> following is the output.
>
> #./setrlimit03
> setrlimit03    1  FAIL  :  call succeeded unexpectedly
Uhh, success here.
To be investigated.
(Note that I use ltp-full-20060306)

> #./madvise02
> madvise02    1  PASS  :  expected failure - errno = 22 : Invalid argument
> madvise02    2  PASS  :  expected failure - errno = 22 : Invalid argument
> madvise02    3  PASS  :  expected failure - errno = 22 : Invalid argument
> madvise02    4  PASS  :  expected failure - errno = 12 : Cannot allocate
> memory madvise02    5  FAIL  :  madvise failed, expected return value = -1,
> got 0
Same results on bare iron linux.

Thank you for the tests,
Tristan.


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