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] [FYI] FC6 kernel and latest xen

To: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, ia64 Fedora Core Development <fedora-ia64-list@xxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [FYI] FC6 kernel and latest xen
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Thu, 24 Aug 2006 13:16:27 +0200
Delivery-date: Thu, 24 Aug 2006 04:12:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4DC6C76C8EE4EEtakebe_akio@xxxxxxxxxxxxxx>
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: <4DC6C76C8EE4EEtakebe_akio@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Jeudi 24 Août 2006 13:00, Akio Takebe a écrit :
> Hi,
>
> I tried to boot dom0/domU with netfront/netback module.
> I can boot up dom0/domU with Kouya's patch.
>
> My environment is;
> - dom0/domU kernel
>    http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora cset #35247
> - xen & tools
>    http://xenbits.xensource.com/ext/xen-ia64-unstable.hg cset #11048
> - Machine
>    Tiger4
>
> But I have many error message.
>
> [root@guest ~]# kernel unaligned access to 0xe0000000187a4e1e, ip=
> 0xa0000001004fad50
> kernel unaligned access to 0xe0000000187a4e1e, ip=0xa0000001004fae21
>
> kernel unaligned access to 0xe0000000187a4e1e, ip=0xa0000001004faed0
> kernel unaligned access to 0xe0000000187a4e2e, ip=0xa0000001004fb130
> kernel unaligned access to 0xe0000000187a4e1e, ip=0xa0000001004fb2e0
> kernel unaligned access to 0xe00000001662921e, ip=0xa0000001004fad50
> kernel unaligned access to 0xe00000001662921e, ip=0xa0000001004fae21
> kernel unaligned access to 0xe00000001662921e, ip=0xa0000001004faed0
> kernel unaligned access to 0xe00000001662922e, ip=0xa0000001004fb130
> kernel unaligned access to 0xe00000001662921e, ip=0xa0000001004fb2e0
> kernel unaligned access to 0xe0000000187a5e1e, ip=0xa0000001004fad50
> kernel unaligned access to 0xe0000000187a5e1e, ip=0xa0000001004fae21
> kernel unaligned access to 0xe0000000187a5e1e, ip=0xa0000001004faed0
> kernel unaligned access to 0xe0000000187a5e2e, ip=0xa0000001004fb130
> kernel unaligned access to 0xe0000000187a5e1e, ip=0xa0000001004fb2e0
> kernel unaligned access to 0xe00000000df1a61e, ip=0xa0000001004fad50
> kernel unaligned access to 0xe00000000df1a61e, ip=0xa0000001004fae21
> kernel unaligned access to 0xe00000000df1a61e, ip=0xa0000001004faed0
> kernel unaligned access to 0xe00000000df1a62e, ip=0xa0000001004fb130
> kernel unaligned access to 0xe00000000df1a61e, ip=0xa0000001004fb2e0
> kernel unaligned access to 0xe0000000187a501e, ip=0xa0000001004fad50
> kernel unaligned access to 0xe0000000187a501e, ip=0xa0000001004fae21
> kernel unaligned access to 0xe0000000187a501e, ip=0xa0000001004faed0
> kernel unaligned access to 0xe0000000187a502e, ip=0xa0000001004fb130
> kernel unaligned access to 0xe0000000187a501e, ip=0xa0000001004fb2e0
I suppose these are the usual bridge unaligned access log.  You should check 
with IP.

Is anyone working on this ?

Tristan.

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

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