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: [Xen-devel] More driver domain issues - rebooting backend hangs

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] More driver domain issues - rebooting backend hangs
From: "B.G. Bruce" <bgb@xxxxxxxxx>
Date: Mon, 07 Feb 2005 18:16:19 -0400
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 07 Feb 2005 22:17:31 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D123740@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: Networking Technologies NV
References: <A95E2296287EAD4EB592B5DEEFCE0E9D123740@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: bgb@xxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Ian,

Here is what "o" gave (I hope it helps):


xen0 root # (XEN) *** Serial input -> Xen (type 'CTRL-a' three times to
switch input to DOM0).
(XEN) pt base=235b sh_info=1bc
(XEN) Audit 0: [2a21,2ec] Skip foreign page dom=fc5b5a00 pfn=1a1
c=00000001 t=f0000002 m2p=ffffffff
(XEN) Audit 0: [2a21,2ed] Skip foreign page dom=fc5b4d20 pfn=1a9
c=00000001 t=f0000002 m2p=ffffffff
(XEN) Audit 0: [2a21,34f] Skip foreign page dom=fc5b4040 pfn=1b2
c=00000001 t=f0000002 m2p=ffffffff
(XEN) Audit 0: Found 256 lowmem mappings and 33025 io mappings
(XEN) Audit 0: gen count!=1 (c=80000002) t=b0000001 ot=b0000001 pfn=1103
(XEN)      found dom=0 i=103 pfn=1346 t=36000000 c=80000001
(XEN) *pde = 00000000
(XEN)  -- POSSIBLY AN ACCESS TO FREED MEMORY? --
(XEN) CPU:    0
(XEN) EIP:    0808:[<fc520890>]
(XEN) EFLAGS: 00211206
(XEN) eax: f0300073   ebx: fea84800   ecx: fd400000   edx: 000f0300
(XEN) esi: 00000000   edi: ffa4a000   ebp: 002d0900   esp: fc503eec
(XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810
(XEN) Stack trace from ESP=fc503eec:
(XEN) 01041000 00000000 00000103 00001346 36000000 80000001 00000001
f0000002
(XEN)        ffffffff fc54f190 00000000 fc5b5a18 53458220 00000002
00001041 00006be1
(XEN)        00000000 0000006f fc503f80 00000001 00006be1 fd418618
00000100 00008101
(XEN)        fc503f6c 00003701 00000000 fc59e6c0 00000000 fc59e6c0
fc53a580 [fc5217d8]
(XEN)        fc59e6c0 00000000 00000008 [fc507ecd] 0000006f 00000000
fc53a580 [fc510cd2]
(XEN)        00000000 fc59e6c0 fc53a580 00000000 00040000 00000000
00000000 [fc519421]
(XEN)        00000000 fc59e6c0 00000198 00000001 53913e80 50964e00
00000001 c0306200
(XEN)        00000000 00000006 00070000 c0106c05 00000061 00201246
c02e1fe4 00000069
(XEN)        0000007b 0000007b 00000000 00000000 fc53a580
(XEN) Call Trace from ESP=fc503eec: [<fc5217d8>] [<fc507ecd>]
[<fc510cd2>] [<fc519421>]
                                                                                
                                                                                
                                     
****************************************
CPU0 FATAL PAGE FAULT
[error_code=0000]
Faulting linear address might be fea8480c
Aieee! CPU0 is toast...
****************************************
                                                                                
                                                                                
                                     
Reboot in five seconds...




On Sun, 2005-02-06 at 21:51, Ian Pratt wrote:
> > When rebooting the backend driver domain, if it has been utilized by a
> > normal domU, it will close down properly and then hang (not 
> > reboot). I'm
> > left rebooting the whole box.  Is this to be expected?  This even
> > happens if the normal domU has been powered off.
> 
> It certainly never used to be a problem with the old xend, but running
> separate driver domains has not been widely tested with the current one.
> 
> If you're using a debug build of Xen with a serial console, it might be
> worth hitting 'o' to find out what resources the domain is still
> holding.
> 
> Ian
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel