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] save/restore clean up and related bugs

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] save/restore clean up and related bugs
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Mon, 07 May 2007 18:09:04 -0600
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 07 May 2007 17:07:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070507062308.GH6474%yamahata@xxxxxxxxxxxxx>
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>
Organization: HP OSLO R&D
References: <20070507062308.GH6474%yamahata@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2007-05-07 at 15:23 +0900, Isaku Yamahata wrote:
> Hi.
> I debugged domU save/restore and sent out the patches.
> There were some bugs which seemed to occur very rarely.
> Please test.
> 
> - bug 943
>   http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=943
>   To be honest I saw a similar issue before and I didn't track it down
>   at that time.
>   But I'm not able to reproduce it at this time.
>   What activity causes it? Does this still happen?

   I still see these pretty regularly after a save/restore (running ia64
cset 15029).  I'm testing with a 16G 2-way dom0 and a 4-way 4G domU
using an lvm disk.  I boot up the domU, save, restore, then an 'ls' in
the domU usually triggers a few of them.  They tend to work themselves
out after a while, so subsequent 'ls' operations usually work fine.
Here are the kernel addresses that I've seen trigger these messages on
my current test system:


0xa00000010012d000 <kmem_cache_alloc+608>:      [MII]       break.m 0x7
0xa000000100152190 <count+144>: [MII]       ld8 r9=[r32]
0xa0000001004c71d0 <get_request+912>:   [MII]       break.m 0x7
0xa0000001004cb960 <__make_request+2432>:       [MII]       break.m 0x7
0xe000000000000810 I believe this is where we branch into PAL_HALT_LIGHT

> - NULL pointer dereference
>   I also observed the following kernel panic when a domain is restored.
>   It occured very rarely and I wasn't able to reproduce it reliably.
> 
> Unable to handle kernel NULL pointer dereference (address 0000000000000000)
> swapper[0]: Oops 11012296146944 [1]
> Modules linked in:

   I don't think I've seen one of these recently.  Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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

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